• LORD/minesweeper errors

    From Dumas Walker@VERT/CAPCITY2 to All on Saturday, November 23, 2019 17:25:26
    I pulled a cvs update for the xtrn directory about an hour ago. After adding LORD, LORD2, and Minesweeper to my doors menus, I am getting the following errors:

    LORD:
    !JavaScript /sbbs/xtrn/lord/lord.js line 2979: TypeError: statefile.new is not a function

    LORD2:
    !JavaScript /sbbs/exec/load/recordfile.js line 26: TypeError: RecordDef[i].type.match is not a function

    Minesweeper:
    !JavaScript /sbbs/xtrn/minesweeper/minesweeper.js line 39: ReferenceError: BG_HIGH is not defined

    This is on a linux machine in an SSH session.

    ---
    þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Digital Man@VERT to Dumas Walker on Monday, November 25, 2019 12:18:15
    Re: LORD/minesweeper errors
    By: Dumas Walker to All on Sat Nov 23 2019 05:25 pm

    I pulled a cvs update for the xtrn directory about an hour ago. After adding LORD, LORD2, and Minesweeper to my doors menus, I am getting the following errors:

    LORD:
    !JavaScript /sbbs/xtrn/lord/lord.js line 2979: TypeError: statefile.new is not a function

    LORD2:
    !JavaScript /sbbs/exec/load/recordfile.js line 26: TypeError: RecordDef[i].type.match is not a function

    Minesweeper:
    !JavaScript /sbbs/xtrn/minesweeper/minesweeper.js line 39: ReferenceError: BG_HIGH is not defined

    This is on a linux machine in an SSH session.

    Sounds like you need to cvs-update your exec and exec/load directories.

    digital man

    This Is Spinal Tap quote #19:
    Oh then, maybe it's not green. Anyway this is what I sleep in sometimes.
    Norco, CA WX: 66.5øF, 32.0% humidity, 1 mph ESE wind, 0.00 inches rain/24hrs

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Tuesday, November 26, 2019 19:44:00
    Sounds like you need to cvs-update your exec and exec/load directories.

    cd ~
    export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs
    cvs update -d src 3rdp
    cd /sbbs/src/sbbs3; make RELEASE=1 USE_DOSEMU=1 symlinks
    cd /sbbs/src/sbbs3/scfg; make RELEASE=1 symlinks
    cd ~
    ## do this again because sometimes the machine seems to forget it was done export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs
    cvs update -d exec
    cd /sbbs/ctrl
    rm -v text.dat.1
    wget 'http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/text.dat'
    cvs update -d text
    cd exec
    ./jsexec update

    That is what my compsync.sh currently looks like, minus the exports that
    set the SBBS variables, a backup of exec, and the bash header info.

    Besides src, 3rdp, exec, and text (and apparently exec/load) are there any other directories that need regular cvs update pulls? Is there anything
    you see that is not in the correct order?

    Thanks!


    * SLMR 2.1a * This tagline is umop apisdn

    ---
    þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Digital Man@VERT to Dumas Walker on Wednesday, November 27, 2019 08:54:55
    Re: LORD/minesweeper errors
    By: Dumas Walker to DIGITAL MAN on Tue Nov 26 2019 07:44 pm

    Sounds like you need to cvs-update your exec and exec/load directories.

    cd ~
    export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs
    cvs update -d src 3rdp
    cd /sbbs/src/sbbs3; make RELEASE=1 USE_DOSEMU=1 symlinks
    cd /sbbs/src/sbbs3/scfg; make RELEASE=1 symlinks
    cd ~
    ## do this again because sometimes the machine seems to forget it was done export CVSROOT=:pserver:anonymous@cvs.synchro.net:/cvsroot/sbbs
    cvs update -d exec
    cd /sbbs/ctrl
    rm -v text.dat.1
    wget 'http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/ctrl/text.dat' cvs update -d text

    The current working directory at this point ^ is /sbbs/ctrl, so a "cvs update -d text" would fail.

    cd exec

    Also this "cd" command would fail. Try using full paths for your "cd" commands instead (e.g. cd /sbbs/exec).

    ./jsexec update

    That is what my compsync.sh currently looks like, minus the exports that
    set the SBBS variables, a backup of exec, and the bash header info.

    It appears to have issues with current directory and "cd"ing with relative paths and missing a "cd" or two. If you specified pull paths on all your command-lines, you shouldn't need *any* cd commands.

    Besides src, 3rdp, exec, and text (and apparently exec/load) are there any other directories that need regular cvs update pulls? Is there anything
    you see that is not in the correct order?

    That looks like it might almost be right if your home diretory (~) is in fact /sbbs. Is it?

    digital man

    Synchronet "Real Fact" #52:
    Answers to Frequently Asked Questions: http://wiki.synchro.net/faq:index
    Norco, CA WX: 53.5øF, 66.0% humidity, 0 mph W wind, 0.00 inches rain/24hrs

    ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Dumas Walker@VERT/CAPCITY2 to Digital Man on Saturday, November 30, 2019 14:26:15
    Sounds like you need to cvs-update your exec and exec/load directories.


    I did that just a bit ago. updating exec seems to pull in exec/load, btw, but I did them both anyway.

    Now lord starts but gets an error that I was not able to capture when trying to create a new player. It does not do it again when the player returns. Something about not being able to find an fmutex around line 42 maybe?

    It seems to work now. Lord 2 and Minesweeper also seem to work so I am looking forward to opening up to the users. Thanks!

    ---
    þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP