I was able to find the new A47. I have never upgraded Mystic before and am confused by a few things.

In the upgrade.txt file, it says:

2. There is no automatic upgrade process. The process is to install the full
installation to a temporary directory, so that you have access to the
latest version of the files. Then follow the upgrade instructions
provided
below for your specific version. Usually this just means replacing new
binary files contained in the new alpha. DO NOT ATTEMPT TO INSTALL OVER
YOUR EXISTING SETUP

I am running Linux and upgrading from A46. In the instructions on how to do this, there's no indication I can see of what binary files to copy over in
that list. Everything in the main mystic dir?

There is also an upgrade executable which seems to update DAT files. There's no reference to this one in the upgrade instructions either.

I have unrar'd the A47 into a temporary diectory. My understanding is I
should do a fresh install of this to a temporary directory, then copy some files over, and then do the checklist of other upgrades. My question is
which files should I copy over? Is there some kind of glob I should use to know which ones, or is it basically everyting in the /mystic directory?

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

In the upgrade.txt file, it says:

2. There is no automatic upgrade process. The process is to install
the full installation to a temporary directory, so that you have access to the latest version of the files. Then follow the upgrade instructions provided
below for your specific version. Usually this just means replacing new binary files contained in the new alpha. DO NOT ATTEMPT TO INSTALL OVER YOUR EXISTING SETUP

I am running Linux and upgrading from A46. In the instructions on how
to do this, there's no indication I can see of what binary files to copy over in that list. Everything in the main mystic dir?

I hate to write ANY wrong info, but I'll try to help you... yer coming from a46 all the way to the newest a47, which will be a great update but there is some extra steps to be done.

Once yer on a47, and a newer a47 alpha comes out its pretty easy; USUALLY its simply two commands:
./install replace ~/mystic [This replaces the executables in /mystic to new
ones]
./mplc -T [This recompiles all the scripts to the new version.]

However, coming from a46 is a bigger update. BACKUP YOUR BBS FULLY - DATA LOSS COULD HAPPEN! Heres the commands I'd enter to upgrade from a46 stable to the newest 06/21 a47:

./install replace ~/mystic
[This WILL overwrite your /mystic binaries to new a47 versions!]
./install extract prompts.dat ~/mystic/data
./install extract msg_editor.c132* ~/mystic/themes/default/text
./install extract msg_editor.ini ~/mystic/themes/default/text
[IF you use a custom msg_editor.ini you might want to EDIT yours as opposed to overwriting with new. If yours is stock, this is fine.]
./install extract taglines.ans ~/mystic/themes/default/text
./install extract taglines.ini ~/mystic/themes/default/text
./install extract taglines.dat ~/mystic/data
[You can find my LARGE 400,000line taglines file @ 20ForBeers.com:1337, file area #22 'Other BBS', taglines.zip.]
./mystic -cfg
[Goto new user settings #2 and set Taglines to "ON"; or whatever setting you prefer.]
[If you have a custom #132 prompt in any of your themes, reset to default or update to include new format; add "YNC" to the beginning.]
[If you have a custom #522 prompt in any of your themes, reset to default or update to include new format; add "YN" to the beginning.]
./mplc -T
[From the /mystic directory; this recompiles all your MPL scripts to the new format.]
rm fidopoll
[fidopoll has been officially replaced by the POLL command in MIS. You must address any events you're using, and fix any calls to "fidopoll" that you may use... additionally, some of us have created the following fidopoll.sh script, AND chmod +x'd it, so that anything we missed will still function and not create an issue:]

fidopoll.sh:
-----
#!/bin/sh
./mis poll $@
-----

I believe this covers everything; however YOU need to read upgrade.txt and whatsnew.txt to make sure I didn't miss any steps. MY system is highly customized and I can't just overwrite those msg_editor.ini and other files... but any stock system will be fine. Again, backup FIRST... shutdown MIS before trying any update [BBS fully offline and shutdown.] and doublecheck my work. I'm not a professional sysOp, I just pretend to be one on Tuesdays.

... A REAL test for that pink bunny : installing Windows95 on an XT



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

I hate to write ANY wrong info, but I'll try to help you... yer coming from a46 all the way to the newest a47, which will be a great update but there is some extra steps to be done.

Thanks. I will check your steps against the checklist. Stopping everything and backing up goes without saying. I appreciate the time you took to write all of that out.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

I think I'm just about good to go.

The one thing I noticed is my single Python (mpy) script, having worked fine before the upgrade from A46 to A47, is now returning:

Cannot initialize Python, press a key

Nothing else has changed other than this upgrade. Anyone have any ideas?

Note: I got this working in Ubuntu by following the instructions on the Wiki (this involved re-compling Python with some options). I am unsure whether repeating that process would have any effect. On Python 2.7.x currently.

--- Mystic BBS v1.12 A47 2021/06/28 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

Fixed the Python issue after a search through this echo.

From an exchange about a month ago:

The Godfather reported that he was having Python problems as well, and Warpslide responded that the Python paths in Configuration -> General Settings were set to Windows paths. At some point in the upgrade process, this happened to me as well.

This turned out to be my problem as well. I don't recall just glossing over those settings or if they are new, but as I am running Linux, blanking out that setting worked for me as it now access from the default location on my Linux system.

Curiously, pointing the directory to my actual libpython2.7.so.1.0 file, or to do the directory it is in, did not work for some reason.

Blank works.

But these do not, for some reason. As I run Ubuntu, I had to do the compile-with-swtiches procedure from the Wiki.

/usr/local/bin/python
/usr/local/bin/python/libpython2.7.so.1.0

Just including it here in case anyone else has this issue.

--- Mystic BBS v1.12 A47 2021/06/28 (Linux/64)
* Origin: Shipwrecks & Shibboleths [San Francisco, CA - USA] (21:1/227)

I hate to write ANY wrong info, but I'll try to help you... yer comin from a46 all the way to the newest a47, which will be a great update there is some extra steps to be done.

Thanks. I will check your steps against the checklist. Stopping everything and backing up goes without saying. I appreciate the time
you took to write all of that out.

Oh, no worries at all my friend - I love this stupid BBS habit. I think you'll like the a47 - especially for taglines, the new 160c ansi viewer, scrolling menu text and a lot more. Its a damn good upgrade.

Let me know how the upgrade goes when you get moving on it. :P Cheers, DC!!

... A program is never complete; you just release an update now and then.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Fixed the Python issue after a search through this echo.

Good job documenting that for the next guy - you were really good at posting info someone else might need. Glad that update went super smoothly, cause it was a big one and I thought for your sure yer computer was gonna catch on fire, blow up and take out your eyeball in the process... whew. We dodged a bullet, rockstar - yer here for the long-haul!!!

OMG - we made it... last time we went thru this was when we lost 'diskmaster42'... RIP, we'll never forget you DM.

... I don't know, ask Jim Harrer at Mustang Software.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2021/06/21 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

On 02 Jul 2021, paulie420 said the following...

In the upgrade.txt file, it says:

2. There is no automatic upgrade process. The process is to install the full installation to a temporary directory, so that you have access to the latest version of the files. Then follow the upgra instructions provided

Nope doesn't work. After 6/28/21 update I noticed .ANS file viewing didn't work. I saw the new 7/2/21 update, has more instructions, but still doesn't work, The upgrade.txt does have more instructions, but it still doesn't
work for archives of .ANS files. Basically view doesn't work anymore.
I'll have to do much more digging through upgrade.txt and whatsnew.txt

... Everyone has a photographic memory. Some don't have film.

--- Mystic BBS v1.12 A47 2021/06/28 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

On 02 Jul 2021, DustCouncil said the following...

Fixed the Python issue after a search through this echo.

It's things like this that are the reason why I'm glad that I keep all the messages my BBS received.

I did figure _someone_ had an answer for this:

The Godfather reported that he was having Python problems as well, and Warpslide responded that the Python paths in Configuration -> General Settings were set to Windows paths. At some point in the upgrade process, this happened
to me as well.

And, yeah, that was DustCouncil finding the answer, and referencing an even older message where it was also answered.

Upshot is that I _finally_ have Storm BBS on A47. Now to see what else I need to change and/or have been missing.

Curiously, pointing the directory to my actual libpython2.7.so.1.0 file, or to the directory it is in, did not work for some reason.

Blank works.

...I'm still at a loss on this one, too, but it actually working is limiting my desire to actually figure it out.

Not sure if I'll have to figure out something for Python3, regardless. I didn't leave that one blank, but I'm not sure where I'm using Python3 at the moment.

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Storm BBS (21:2/108)

Fixed the Python issue after a search through this echo.

Good job documenting that for the next guy - you were really good at posting info someone else might need.

Hah!

And it _did_ help. Especially since searching with a search engine did not.

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Storm BBS (21:2/108)