A few weeks back, you had mentioned that the upgrade scripts no longer work. I was reading the install instructions on github. Those do not appear to like an existing installation.

How does one upgrade to the latest version again?

Thanks!
--- SBBSecho 3.01-Linux
* Origin: CCO BBS - capcity2.synchro.net - 1-502-875-8938 (21:1/175)

Hmm, should just be a matter of git pull and make www or just make if you're not using the webserver.

Then run any of the sql update scripts on the relevant databases. There is
one for the users.sq3 and another for any filebases you have set up.

Andrew
--- MagickaBBS v0.7alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

Hmm, should just be a matter of git pull and make www or just make if you're not using the webserver.

"Please commit your changes or stash them before your merge. Aborting."

So, how do I convince git that I have already made backups? :)
--- SBBSecho 3.01-Linux
* Origin: CCO BBS - capcity2.synchro.net - 1-502-875-8938 (21:1/175)

Dumas Walker said....

Hmm, should just be a matter of git pull and make www or just make if

you'r

e

not using the webserver.

"Please commit your changes or stash them before your merge. Aborting."

If I recall correctly, it's probably complaining about a binary file I accidentally committed and removed, just delete the files it complains about and try again..

Andrew
--- MagickaBBS v0.7alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

If I recall correctly, it's probably complaining about a binary file I >accidentally committed and removed, just delete the files it complains about >and try again..

Thanks! Next time I have a few minutes, I will do that and we will see
what happens.

---
þ SLMR 2.1a þ "­Beavis! ¨Donde esta su hall pass?"
* Origin: CCO BBS - capcity2.synchro.net - 1-502-875-8938 (21:1/175)

³ > > Hmm, should just be a matter of git pull and make www or just make if
³ you'r
³ > e
³ > > not using the webserver.
³ >
³ > "Please commit your changes or stash them before your merge. Aborting."
³
³ If I recall correctly, it's probably complaining about a binary file I
³ accidentally committed and removed, just delete the files it complains about ³ and try again..
ÀÄ[=>DW]

It is actually complaining about 2-3 screens full of files... at least 60
of them. I am concerned that deleting them all will cause some sort of
issue.

I checked man git but there does not appear (to me) to be a
command to tell it to ignore all those and just go ahead and repull it all.

##Mmr 2.61á. !link 12-05-17 14:41


--- GTMail 1.26
* Origin: moe's tavern * 1-502-875-8938 * moetiki.ddns.net (21:1/175.3)

It is actually complaining about 2-3 screens full of files... at least 60 of them. I am concerned that deleting them all will cause some sort of issue.

Hmm, that's odd. Might be best just to nuke it and start over.

Andrew


--- MagickaBBS v0.7alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

Quoting apam to Dumas Walker <=-

It is actually complaining about 2-3 screens full of files... at least 60

Hmm, that's odd. Might be best just to nuke it and start over.

Possibly from when you changed the directory structure a while back? I
know one install I just saved my language file, ansi and menu directory
and scrapped everything else. Was way easier. :)

Shawn

... If you can't control yourselves, we will do it FOR you.
--- Blue Wave/386
* Origin: A Tiny slice o pi (21:1/130.4)

Tiny said....

Quoting apam to Dumas Walker <=-

It is actually complaining about 2-3 screens full of files... at least

60

Hmm, that's odd. Might be best just to nuke it and start over.

Possibly from when you changed the directory structure a while back? I
know one install I just saved my language file, ansi and menu directory
and scrapped everything else. Was way easier. :)

Possible I suppose, but git should have coped with that. The only thing I can think of that might cause so many files is possibly some time/date issues.

Andrew
--- MagickaBBS v0.7alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

Possibly from when you changed the directory structure a while back? I

Speaking of changing the directory structure.. I've been thinking of
moving all the examples into a dist/ folder, and removing the "_default"
etc from the folder names.. That way when you do an initial setup you can
just recursivley copy the dist folder rather than each folder to a
different name.

Also thinking about making a script to do initial setup a bit like the raspberry pi script, but just for configuring.

I just saw the issues you've been creating.. thanks a lot :) you're
awesome :)

Andrew


--- MagickaBBS v0.7alpha (Linux/x86_64)
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

etc from the folder names.. That way when you do an initial setup you can just recursivley copy the dist folder rather than each folder to a different name.

Sure that would work. I'm used to things the way they are now, but
it's not that difficult to change muscle memory. ;)

Also thinking about making a script to do initial setup a bit like the raspberry pi script, but just for configuring.

That would be handy for the new users. One thing especially is the magicka.strings file. I just manually look for additions (new lines) and
if there are any I copy / paste them from the
/src/MagickaBBS/magicka.strings to the running version that I have
modified. You do normally also make a note in git if you change any
major wording or key strokes in the rest of the file I need to deal with.

I just saw the issues you've been creating.. thanks a lot :) you're awesome :)

No problem. :) As they are not really "issues" I just hope any one
else developing at least realizes I'm not being a fidonet "I DEMAND THIS
WORK PERFECTLY NOW!!!!" kinda person. ;)

Shawn


--- MagickaBBS v0.7alpha (Linux/armv7l)
* Origin: A Tiny slice o pi (21:1/130.4)

Tiny wrote to apam <=-

etc from the folder names.. That way when you do an initial setup you can just recursivley copy the dist folder rather than each folder to a different name.

Sure that would work. I'm used to things the way they are now, but
it's not that difficult to change muscle memory. ;)

As you're already set up, in theory it shouldn't be that noticable. Except
for the strings you already mentioned.

That would be handy for the new users. One thing especially is the magicka.strings file. I just manually look for additions (new lines)
and if there are any I copy / paste them from the /src/MagickaBBS/magicka.strings to the running version that I have modified. You do normally also make a note in git if you change any
major wording or key strokes in the rest of the file I need to deal
with.

Yes, I'm not really sure what the best way of managing the strings file is. Usually I just add them to the end. But that means there could be obsolete strings throughout the file.

No problem. :) As they are not really "issues" I just hope any one
else developing at least realizes I'm not being a fidonet "I DEMAND
THIS WORK PERFECTLY NOW!!!!" kinda person. ;)

It's all good, None of the current developers think that anyway ;P. Just testing the Full Name for "Personal Messages" in bluewave to make sure I haven't destroyed it.. Will add the email area tomorrow perhaps, I really should be in bed :)

Andrew


... MultiMail, the new multi-platform, multi-format offline reader!
--- MultiMail/Linux
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)

Hello apam!

07 Jan 18 15:36, you wrote to Dumas Walker:

It is actually complaining about 2-3 screens full of files... at
least 60 of them. I am concerned that deleting them all will
cause some sort of issue.

Hmm, that's odd. Might be best just to nuke it and start over.

Or at least pull a copy in a different directory, so you can compare the two.

BitByter

--- GoldED+/LNX 1.1.5-b20170303
* Origin: Phoenix BBS * phoenix.bnbbbs.net (21:4/105)

On Saturday, January 6th Dumas Walker muttered...

again.. └─[=>DW] It is actually complaining about 2-3 screens full of files... at least 60 of them. I am concerned that deleting them all will cause some sort of issue. I checked man git but there does not appear (to me) to be a command to tell it to ignore all those and just go ahead and

I'm jumping in here without context, but are you sure text files aren't being modified between Unix and DOS line endings? In a lot of default configs, if you
check out e.g. Unix/Linux style text file (e.g. source) to a Windows box or vice versa, it will automatically be modified. You'd need to turn this off, or selectively turn it off in the repo by file extention then re-checkout said files.



--- ENiGMA 1/2 v0.0.8-alpha (linux; x64; 6.11.3)
* Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)

Quoting apam to Tiny <=-

Yes, I'm not really sure what the best way of managing the strings
file is. Usually I just add them to the end. But that means there could
be obsolete strings throughout the file.

That can be delt with. ie: if you replace an obsolete string with a new
one can you not just say in a "readme.now" file "line 23 is new" or
something so we know to change it?

It's all good, None of the current developers think that anyway ;P.

Good enough. :)

Just testing the Full Name for "Personal Messages" in bluewave to make sure I haven't destroyed it.. Will add the email area tomorrow perhaps,
I really should be in bed :)

By the time you read this I've updated it here and uploaded this packet
to the system ready for testing. :)

Shawn

... Never invest your money in anything that eats or needs painting.
--- Blue Wave/386
* Origin: A Tiny slice o pi (21:1/130.4)

Quoting NuSkooler to Dumas Walker <=-

I'm jumping in here without context, but are you sure text files
aren't being modified between Unix and DOS line endings? In a lot of

I have some files with both line endings here, and it doesn't seem to
affect anything. Not sure if maybe my editors change it or if apam
takes that into consideration. (ansi files are all done on windows xp)

Shawn

... I'm on the computer and I'm not wearing pants!
--- Blue Wave/386
* Origin: A Tiny slice o pi (21:1/130.4)

Hmm, that's odd. Might be best just to nuke it and start over.

Too much like work. :) Git and compile your own is really only good for people who have the time to keep up and git everytime something changes, or
who just want to stay on the bleeding edge. If you don't keep up you are
going to wind up out of sync, and starting over a lot.

I am no doubt in that latter group!

I think it is neat project and will keep tabs on it. If it ever gets to the point where there are some stable release binaries I may try it again.

Thanks!

---
þ SLMR 2.1a þ Keep your stick on the ice
* Origin: CCO BBS - capcity2.synchro.net - 1-502-875-8938 (21:1/175)

Dumas Walker wrote to APAM <=-

Hmm, that's odd. Might be best just to nuke it and start over.

Too much like work. :) Git and compile your own is really only good
for people who have the time to keep up and git everytime something changes, or who just want to stay on the bleeding edge. If you don't
keep up you are going to wind up out of sync, and starting over a lot.

It really shouldn't be that hard, yours seems to be a special case where
there has been some corruption locally. It should just be a matter of git
pull, make and running any update scripts, regardless of how out of date it
is.

I think it is neat project and will keep tabs on it. If it ever gets
to the point where there are some stable release binaries I may try it again.

Thanks for trying it out.

Andrew


... What is mind? No matter! What is matter? Never mind! - Homer S.
--- MultiMail/Linux
* Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)