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

Re: LSB 3.1 status for etch

On Tue, 2006-08-01 at 11:21 +0200, Petter Reinholdtsen wrote:
> [Jeff Licquia]
> > Most of the current tests pass.  Of those that don't, most are
> > recognized deficiencies.  In sum, there are two potential issues
> > with Debian and the LSB: a possible bug in cpio, and an issue with
> > the libX11 ABI that is common to X.org distributions.
> If I got this right, we could fix one issue with cpio and claim Debian
> is compliant with LSB 3.1?

Sort of.  We have to release etch first.  I doubt people want to support
July's etch for all time. :-)

But assuming the cpio problem gets fixed, it would seem that we will be
able to certify etch once it's released.

> I guess now is the time to fix cpio and update policy, then. :)
> Is there a BTS report describing the problem with cpio?  I am not sure
> what to look for in
> <URL:http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=cpio>.

To my knowledge, there is no Debian bug yet.

Some of the other LSB people have started working on the cpio bug since
I posted my report.  It's a problem in Fedora Core 5 as well.  Our
current theory is that something changed between cpio 2.5 and 2.6,
although we've noted some cpio 2.6 distributions that don't have the

I am currently preparing to analyze the changes between 2.5 and 2.6, to
see if I can isolate the exact change which introduced the problem.

Reply to: