Hello Rick,

On 31 Oct 16 19:45, Rick Christian wrote to Nicholas Boel:

 RC>>> 0.71 has 5-6 files in the directory some too small to be source,
 RC>>> no clear directions on what to use, so moved on to 0.75 instead.

 RC> As per above, which of these:
 RC> crashmail_0.71-4.diff.gz        2010-08-12      14.3 kB         0
 RC> i crashmail_0.71-4.dsc    2010-08-12      1.1 kB  0
 RC> i crashmail_0.71-3.diff.gz        2009-07-11      14.0 kB         0
 RC> i crashmail_0.71-3.dsc    2009-07-11      1.1 kB  0
 RC> i cm071linux.zip  2009-02-17      361.6 kB        0
 RC> i crashmail_0.71-2.diff.gz        2007-09-02      4.0 kB  0
 RC> i crashmail_0.71-2.dsc    2007-09-02      567 Bytes       0
 RC> i crashmail_0.71-1.diff.gz        2004-07-28      3.8 kB  0
 RC> i crashmail_0.71-1.dsc    2004-07-28      567 Bytes       0
 RC> i crashmail_0.71.orig.tar.gz      2004-07-28      169.9 kB

 RC> Only the .orig.tar.gz and the cm071linux.zip seem to big enough to be
 RC> source

cm071linux.zip is the original source archive (as confirmed by Paul).

 RC> lets see this cm071linux.zip is big enough to have source

See? A little trial and error goes a long way!

 RC> Lets throw the library of PKTs at it!

 RC> Area NETMAIL -- 10 messages
 RC> Area PERSONAL_MESSAGES -- 77 messages
 RC> Area BINKD -- 151 messages
 RC> Area NET135 -- 3 messages
 RC> Area NET135FILE -- 104 messages
 RC> Area NET135HUB -- 122 messages
 RC> Area FIDONEWS -- 224 messages
 RC> Area RBERRYPI -- 110 messages
 RC> Area JAMNNTPD -- 150 messages

 RC>    Total ->     Read messages:    881     Written messages:      7
 RC> Imported -> Imported messages:    874      Routed netmails:      7
 RC>      Bad ->      Bad messages:      0   Duplicate messages:      0

 RC> Scanning for orphan files
 RC> Scanning for old packets
 RC> Scanning for new files to pack
 RC> Sending unpacked netmail to 1:135/300.0 (Normal)
 RC> Linking JAM area BINKD
 RC> Linking JAM area NET135
 RC> Linking JAM area NET135FILE
 RC> Linking JAM area NET135HUB
 RC> Linking JAM area FIDONEWS
 RC> Linking JAM area RBERRYPI
 RC> Linking JAM area JAMNNTPD
 RC> Scanning all areas for messages to export
 RC> Scanning area NETMAIL
 RC> Scanning area TESTECHO
 RC> Scanning area TEST
 RC> Scanning area BINKD
 RC> Scanning area NET135
 RC> Scanning area NET135FILE
 RC> Scanning area NET135HUB
 RC> Scanning area FIDONEWS
 RC> Scanning area RBERRYPI
 RC> Scanning area JAMNNTPD

 RC> No messages exported
 RC> Scanning for orphan files
 RC> Scanning for old packets
 RC> Scanning for new files to pack
 RC> CrashMail end
 RC> rec9140@fidodev:~/cmzip/crashmail-0.71/bin$

 RC> So... hmmm.. THIS file seems to work... as no error can't read
 RC> messages...

CONTRATS!

 RC> I've spent the better part of 20+ hours on this over the past 2
 RC> days...

 RC> Thats TOO MUCH! I've moved servers with less headaches in less time
 RC> than that.

Had you listened to some of us (especially Paul) in the first place, you would
not have spent so much time with headaches.

 RC> It should be far simpler.. sudo apt-get install .... edit configs move
 RC> on.

This is Fidonet and FTN software. Most of it does NOT make it into specific
Linux distribution repositories and/or package managers. And obviously as you
can see, when they do make it there, they are left alone untested and quite
possibly broken (as in this case you've just witnessed).

 RC> Now it appears that possibly I've found a version that is the
 RC> "original" version.

 RC> Which you could have posted:

 RC> "Hey grab this file... cm071linux.zip at..http://......." and then run
 RC> this.

I didn't realize you being a linux guy for so many years still needed your hand
held?

 RC> EXPUNGE the DEB's in the repos. and all the other files on the source
 RC> thingy and elsewhere... and see what kind of DEB's I can create that
 RC> will install a WORKING version of this....

You're probably better off using the binaries included with the original
release, rather than trying to go through hoops to get it put into the Debian
repositories. Since the better part of 5 people total seem to actually be using
that tosser.

 RC> I am not sure yet how to test this on the working setup.. I guess I
 RC> can run a parallel setup with the MSG format till it works and toss in
 RC> things to a test JAM setup.... don't know.

 RC> I need booze right now... and lots of it....

SAME! :)

 RC> I've got to get my notes into some sort of readable fashion and then
 RC> work on testing it, and then getting this online so NOBODY ever goes
 RC> through this crap again!

Going through that crap was completely unnecessary. You were told from the
beginning that 0.71 was the original release, and that you should use that. It
was you who decided to try two other versions prior to that one, because you
found some broken (and obviously untested) packages in the Debian repositories.

If you want to go about getting those packages removed from the repos, you may
want to talk to RJ Clay (1:120/544), as I believe he's the guy that attempts to
make deb packages out of FTN software. If it truly is broken, maybe he can fix
it?

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827