Re: real LSB compliance
On Sat, Jun 30, 2001 at 11:51:46PM -0400, Joey Hess wrote:
> So, if we can stop talking about the tired RPM issue for a minute, I was
> wonering: How close is stable and/or testing to compliance with the LSB?
> Has anyone got a handle on that yet?
>
> I downloaded lsbdev from their web site. This is mostly used to build
> .lsb packages (someone should probably package it), but it has a
> lsblibchk program that does a check of the system's libs. It doesn't
> much like unstable[1]. It's also not a thorough check, I'm sure, just
> libs.
>
> It'd be rather nice if we could get unstable and/or an apt repository
> set up to easily make debian fully LSB compliant, soonish. Realistic?
Bear in mind most of the complaints you see there are bogus.
Completely.
> [1] joey@silk:~/tmp>./usr/bin/lsblibchk
> ./usr/bin/lsblibchk 1.0.0
> Unable to find library ld-lsb.so.1
Some LSB thing I assume :) Everyone in the real world calls it either
ld.so.1 or ld-linux.so.2 depending on their platform (roughly, maybe a
few other names).
> Checking symbols in /usr/lib/libGL.so.1
> Checking symbols in /usr/X11R6/lib/libICE.so.6
> Checking symbols in /usr/X11R6/lib/libSM.so.6
> Checking symbols in /usr/X11R6/lib/libX11.so.6
> Checking symbols in /usr/X11R6/lib/libXext.so.6
> Checking symbols in /usr/X11R6/lib/libXt.so.6
> Checking symbols in /lib/libc.so.6
> fgetpos64 has version GLIBC_2.2, expecting GLIBC_2.1
> fgetwc has version GLIBC_2.2, expecting
> fgetwc_unlocked has version GLIBC_2.2, expecting
> getrlimit64 has version GLIBC_2.2, expecting GLIBC_2.1
> getwc has version GLIBC_2.2, expecting
> msgctl has version GLIBC_2.2, expecting GLIBC_2.0
> posix_memalign has version GLIBC_2.2, expecting
> shmctl has version GLIBC_2.2, expecting GLIBC_2.0
> vfwscanf has version GLIBC_2.2, expecting
> Checking symbols in /lib/libcrypt.so.1
> Checking symbols in /lib/libdl.so.2
> Checking symbols in /lib/libm.so.6
> feclearexcept has version GLIBC_2.2, expecting GLIBC_2.1
> fesetenv has version GLIBC_2.2, expecting GLIBC_2.1
> fesetexceptflag has version GLIBC_2.2, expecting GLIBC_2.1
> Checking symbols in /lib/libncurses.so.5
> Checking symbols in /lib/libpthread.so.0
> Checking symbols in /lib/librt.so.1
> Checking symbols in /lib/libutil.so.1
> forkpty has version GLIBC_2.0, expecting
> login has version GLIBC_2.0, expecting
> login_tty has version GLIBC_2.0, expecting
> logout has version GLIBC_2.0, expecting
> logwtmp has version GLIBC_2.0, expecting
> openpty has version GLIBC_2.0, expecting
> Checking symbols in /usr/lib/libz.so.1
Welcome to current version of glibc. It's the LSB that needs to
change, not us.
--
Daniel Jacobowitz Debian GNU/Linux Developer
Monta Vista Software Debian Security Team
Reply to: