On Monday, May 04, 2015 05:30:04 PM VS wrote:
> 04.05.2015 16:37, Robert James Clay пишет:
> >>
> >> CrashMail II doesn't work on debian jessie.
> >> Error: Failed to read message #1 in JAM messagebase
> >> "/home/fido/areas/3bfe0095"
> >>
> > So, this was with version 1.5? And was this the 64 bit version? I ask
> > because I have seen or have heard of issues with the 64 bit version that
> > do not seem to be in the 32 bit version.
>
> Yes, that is 64 bit Debian Jessie.
>
> $ crashmail version
> This is CrashMail II version 1.5
Note that there is already a bug open in Debian [1] and upstream [2] about
issues with operations on a 64 bit system.
I you have not already done so, I would appreciate it you check it's
operation on an 32 bit system. I'm also setting up both 32 and 64 bit systems
(hardware as all as LXCs.) but I would appreciate knowing how others are
seeing it as as well.
> >> Also I can't switch on debug mode for logging.
> >>
> > You mean, by setting the LogLevel to "6"?
>
> Yes
>
> > If so; what are you expecting that you are not seeing?
>
> I haven't noticed big difference between LogLevel 3 and LogLevel 6. That
> is why I've decided LogLevel 6 didn't work.
Looking at the code again that LogLevel doesn't actually seem to be used
much... (Only found one instance.) If you have suggestions about where such
should be, please let me know. Or add a ticket about it at the upstream
project.
Note also that with 1.5-1 version of the package, there is also a package
available with the debugging symbols for it, crashmail-dbg.
> By the way - I have my old JAM message base from 2002 year. It was made
> by crashecho (not crashmail). There weren't any errors when I worked
> with it in 2002.
Was that on a 32 bit system?
> But now, when I scan it by crashmail II and have this
> error for the each echo-conference in my JAM Base - Failed to read
> message #2 (#3,#4,#5...#11) in JAM messagebase
> "/home/fido/areas/3bfe0095". Messages from #2 to #5 have this error but
> messages #1 and #11 ... #20 are OK.
>
> I've thought - my jam messagebase is broken. And simply have made one
> message by GoldedPlus and MSGED TE in a new JAM base. I got the same
> error - Failed to read message #1 in JAM messagebase
> "/home/fido/areas/3bfe0095"
>
> That is why I think - that is problem of crashmail II.
Rather than it being related to the Debian packaging?
RJ Clay ('Jame')
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742723
[2] https://sourceforge.net/p/ftnapps/crashmail/tickets/4/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
