[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#241395: 241395: More than just a preinst bug



I just hit the same bug on a locally compiled kernel ('uname -r' ==
2.4.20evms3) and this is a bigger problem than just the preinst error.

I realize that libc needs to adjust its behaviour depending on the
kernel release, but it needs to detect available features, rather
than just relying on uname(2). There is no requirement that locally
built kernels have a particular format for the release field. There
is no mention of requiring a leading '-' in the make-kpkg manpage
for '--append-to-version' or '--flavour'; if anything, hyphens are
discouraged. Regardless, use of make-kpkg is not required.

If libc is going to continue to depend on a particular structure for the
kernel version number, then all the build tools involved (make-kpkg,
kernel make files, etc.) need to scream loud and clear when that
structure is violated. 

The various Debian and upstream maintainers of the packages involved
need to determine the appropriate solution and implement it. A warning
in the libc preinst (which amounts to "uh, you're screwed") is *way* too
late.

Steve

-- 
Steve Greenland
    The irony is that Bill Gates claims to be making a stable operating
    system and Linus Torvalds claims to be trying to take over the
    world.       -- seen on the net



Reply to: