1. Forum
  2. FSXNet
  3. FSX BBS

  • Magicka 0.10?

    From Dumas Walker@21:1/175 to apam on Sunday, May 20, 2018 10:37:04
    Good morning,
    This morning, I tried to upgrade from 0.09 to 0.10 patch. I ran 'git pull' first which, since I was pointed to 09 and it no longer exists, gave me an error. So I ran 'git checkout v0.10-patch'. That appeared to reset me to the correct version.

    However, when I run 'git pull' again, while I get some message about being pointed to 0.10, I also get one telling me that I am already up to date.
    I went ahead and ran 'make clean' and am running 'make www' now, but shouldn't 'git pull' have actually pulled something?

    Thanks!
    --- SBBSecho 3.04-Linux
    * Origin: CCO BBS - capcity2.synchro.net - 1-502-875-8938 (21:1/175)
  • From apam@21:1/125 to Dumas Walker on Monday, May 21, 2018 07:52:50
    Good morning, This morning, I tried to upgrade from 0.09 to 0.10
    patch. I ran 'git pull' first which, since I was pointed to 09 and
    it no longer exists, gave me an error. So I ran 'git checkout v0.10-patch'. That appeared to reset me to the correct version.

    However, when I run 'git pull' again, while I get some message about
    being pointed to 0.10, I also get one telling me that I am already up
    to date. I went ahead and ran 'make clean' and am running 'make www'
    now, but shouldn't 'git pull' have actually pulled something?

    I think the first git pull would have pulled the changes into your copy
    of the repository and when you run checkout it pulls them out of your
    copy of the repository.

    So the second git pull wouldn't have pulled any changes as the first one already pulled them even though v0.10-patch wasn't checked out at the
    time.

    Andrew

    --- MagickaBBS v0.11alpha (Linux/x86_64)
    * Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)
  • From Dumas Walker@21:1/175 to APAM on Sunday, May 20, 2018 19:11:00
    So the second git pull wouldn't have pulled any changes as the first one already pulled them even though v0.10-patch wasn't checked out at the
    time.

    I compiled it and it thinks it is 0.10-patch, so I am good I guess. :)

    ---
    � SLMR 2.1a � "Mmmmmmmm.....doughnuts."
    * Origin: CCO BBS - capitolcityonline.net:26 (21:1/175)
  • From Dumas Walker@21:1/175 to apam on Monday, May 21, 2018 19:26:42
    Re: RE: Magicka 0.10?
    By: apam to Dumas Walker on Mon May 21 2018 07:52:50

    Is there any way to set the git and/or compile so that it does NOT erase the magimail config file EVERY time one upgrades to the next patch version? I had copied it to another directory (but not one that was nut under MagickaBBS) so it got both copies this time.

    Here on my pi, magimail won't find it unless it is in the magimail bin directory. It would be nice if it was in the directory with all of the other INI files as that one (apparently) does not get erased every time.

    Thanks!
    --- SBBSecho 3.04-Linux
    * Origin: CCO BBS - capitolcityonline.net:26 (21:1/175)
  • From apam@21:1/125 to Dumas Walker on Tuesday, May 22, 2018 13:15:06
    Re: RE: Magicka 0.10?
    By: apam to Dumas Walker on Mon May 21 2018 07:52:50

    Is there any way to set the git and/or compile so that it does NOT
    erase the magimail config file EVERY time one upgrades to the next
    patch version? I had copied it to another directory (but not one
    that was nut under MagickaBBS) so it got both copies this time.
    Here on my pi, magimail won't find it unless it is in the magimail
    bin directory. It would be nice if it was in the directory with all
    of the other INI files as that one (apparently) does not get erased
    every time.

    What I do is have it in an ftn folder under the MagickaBBS. Magimail only
    looks in the current working directory for the magimail.prefs, so what I
    do is invoke magimail like this

    cd MagickaBBS/ftn

    ../utils/magimail/bin/magimail scan

    I could tweak the makefile to not erase the bin folder but the individual binaries instead when clean is run, but for the short term try the above
    method :)

    Andrew

    --- MagickaBBS v0.11alpha (Linux/x86_64)
    * Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)
  • From Havok@21:4/119 to apam on Tuesday, May 22, 2018 16:44:44
    Hello apam

    So tell me what is added new to 0.11 ?

    I just updated today and missed what you added....


    Havok

    --- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)
    * Origin: After Hours|The Villages,FL|afterhours-bbs.com (21:4/119)
  • From apam@21:1/125 to Havok on Wednesday, May 23, 2018 07:32:56
    Hi

    So tell me what is added new to 0.11 ?

    0.11 is the new "work in progress" branch, all I've added so far is the
    message flagging function :)

    Andrew

    --- MagickaBBS v0.11alpha (Linux/x86_64)
    * Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)
  • From Blue White@21:1/175.8 to apam on Tuesday, May 22, 2018 18:11:04
    What I do is have it in an ftn folder under the MagickaBBS. Magimail
    only looks in the current working directory for the magimail.prefs, so what I do is invoke magimail like this

    That suggestion should fix it. thanks!


    ... 2 + 2 = 5 for extremely large values of 2.
    --- MultiMail
    * Origin: Possum Lodge South * capitolcityonline.net:7636 (21:1/175.8)