• AlphaTest upgrade

    From bcw142@21:1/145 to g00r00 on Saturday, December 30, 2017 10:24:43
    When trying to upgrade my AlphaTest system I ran in to an issue: bcw@lenotv2:/mystic$ ./mystic -ver
    ERROR: Data files are not current and must be upgraded
    bcw@lenotv2:/mystic$ ./upgrade

    Mystic BBS Data File Updater v1.12 A37
    Copyright (C) 1997-2017 By James Coyle

    Current data file version.....: v1.12 A37
    Latest data file revision is..: v1.12 A37

    No actions to take, your data files are up to date

    Now what's wrong is something to do with the way I upgrade and not a problem with Mystic itself in any way, except that ./mystic -ver doesn't work. That makes it very had to find the problem which is /mystic/mystic is v1.12 A36 in
    a directory with A37 data files. I had to search with a hexeditor to figure that out because the version command doesn't work when there's a data file mismatch. Version should be able to work even if the data files don't match
    up so these problems can be seen without hacking it with a hexeditor.
    Another fix might be to output the mismatch when it occurs. If you try to run such a mismatch, it could just show the versions of mystic vs data files as
    the error message. I guess this second version might be a better choice.
    ERROR: Data files are not current and must be upgraded
    doesn't really help tell you which is the issue, mystic or it's data files.
    In my case the data files are current, I have an old mystic for some reason.

    --- Mystic BBS v1.12 A35 (Raspberry Pi/32)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From g00r00@21:1/108 to bcw142 on Saturday, December 30, 2017 16:21:02
    problem with Mystic itself in any way, except that ./mystic -ver doesn't work. That makes it very had to find the problem which is /mystic/mystic is v1.12 A36 in a directory with A37 data files. I had to search with a hexeditor to figure that out because the version command doesn't work
    when there's a data file mismatch. Version should be able to work even

    If upgrade says your data files are A37 but mystic says it doesn't match the version, then that means that Mystic can not be A37. I agree the message isn't clear in this situation, so I've changed the error message text in this situation to make it more obvious:

    ERROR: Data files do not match the version of Mystic

    Mystic Version: 1.12 A36
    Data Version: 1.12 A37

    --- Mystic BBS v1.12 A37 2017/12/30 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)