using 3.x instead of 3.x.0 (when minor-minor version is 0) is done by
kernel.org, so I suppose it makes sense for Debian to follow this scheme.
it may be a good idea to run a test that logs all components calling uname,
so they can be checked for version scheme bugs.
On Sun, Sep 8, 2013 at 5:46
On Mon, 2013-09-09 at 14:12 +0200, Yoram Bar Haim wrote:
using 3.x instead of 3.x.0 (when minor-minor version is 0) is done by
kernel.org, so I suppose it makes sense for Debian to follow this
scheme.
Actually, the '.0' is still included if you build a kernel without any
stable updates and
this work-around will make program think they run on top of 2.6.x kernel,
which might be a bug if the program does have special behavior for 3.x.y
On Mon, Sep 9, 2013 at 3:49 PM, Ben Hutchings b...@decadent.org.uk wrote:
On Mon, 2013-09-09 at 14:12 +0200, Yoram Bar Haim wrote:
using 3.x
On 09/09/13 14:07, Yoram Bar Haim wrote:
this work-around will make program think they run on top of 2.6.x
kernel, which might be a bug if the program does have special behavior
for 3.x.y
With all due respect, it's a bug in a program if it crashes with a 3.x
uname string. If it then also
Of course, this is a bug in the user-space compnent (libamu in this case),
and sure, a code that crashes because it does not like the release string
is a bad code, no argument about that.
the idea of running a test to locate problematic component was not ment to
be a responsibility of
Hi,
Just FYI, as you might be interested in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722145
Kaplan
6 matches
Mail list logo
