> >

> >

> W

No big deal - I looked at the code and you did a much more thorough job than I
would have done. Appreciate all of the hard work -- this product is masterful!

> Sorry for that. The idea is that the -4 is the minor number between releases
> (mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
> -4 version several times when testing a new RPM building scheme, but I promise
> to take more care in the future (:-)))
> 
> Having the CVS revision in the executable is however a good idea and I will
> put it in.
> 
> > Stefan, would it be ok to add the "minor" revision level to the VERSION
> > constant?  I've been doing this after I download source just so I can keep
> > things straight, you keep cranking out versions ;->
> > 
> > EX: 
> > #define VERSION "2.5.4-4"
> > BECOMES
> > #define VERSION "2.5.4-4-1.483" or something like that?
> > 
> > Just a thought.
> > 
> > Thanks

That problem has been fixed in 2.5.4-5

I am getting the following error message with version 2.5.4-4 when I try to
add a new entry to a log book.

Attachment file "" empty or not found

If I add the following line to me elogd.cfg I do not get the error, but will
not be able to use attachments.

Enable attachments = 0

I recently upgraded from version 2.2.5 which did not have the problem.  I
did not see anything in the changelog referencing this type of change to how
attachments are handled.

I there something I need to set in the config so that an attachment is not
expected every time a new entry is made?

Sorry for that. The idea is that the -4 is the minor number between releases
(mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
-4 version several times when testing a new RPM building scheme, but I promise
to take more care in the future (:-)))

Having the CVS revision in the executable is however a good idea and I will
put it in.

> Stefan, would it be ok to add the "minor" revision level to the VERSION
> constant?  I've been doing this after I download source just so I can keep
> things straight, you keep cranking out versions ;->
> 
> EX: 
> #define VERSION "2.5.4-4"
> BECOMES
> #define VERSION "2.5.4-4-1.483" or something like that?
> 
> Just a thought.
> 
> Thanks

Stefan, would it be ok to add the "minor" revision level to the VERSION
constant?  I've been doing this after I download source just so I can keep
things straight, you keep cranking out versions ;->

EX: 
#define VERSION "2.5.4-4"
BECOMES
#define VERSION "2.5.4-4-1.483" or something like that?

Just a thought.

Thanks