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

Bug#507849: lintian.d.o run finished, source/binary mismatch not quite fixed



Russ Allbery <rra@debian.org> writes:
> Russ Allbery <rra@debian.org> writes:

>> I'm going to try regenerating the package list by hand and see if I come
>> up with any different results.

> Running list-binpkg by hand returns the correct listing and source
> value.  I wonder if I didn't clean the laboratory as thoroughly as I
> thought I had.  After I upload the next release, I'll do another full
> archive run to test both this and the memory leak fix.

I unfortunately can now confirm that this is still broken.  I checked the
binary-packages listing and it had the right value for the source version,
but after a full run (with harness -f), the value in the binary-packages
list is wrong again.

gluck:/org/lintian.debian.org/laboratory/info> grep aufs-modules-2.6.26-1-486 binary-packages 
aufs-modules-2.6.26-1-486;2.6.26+0+20080719-6;linux-modules-extra-2.6;2.6.26+0+20080719-6;pool/main/l/linux-modules-extra-2.6/aufs-modules-2.6.26-1-486_2.6.26+0+20080719-6_i386.deb;1229775426

This claims the binary package with version 2.6.26+0+20080719-6 was built
from a source package with the same version.  However, this is clearly
wrong:

gluck:/org/lintian.debian.org/laboratory/binary/aufs-modules-2.6.26-1-486> dpkg -I deb | grep Source
 Source: linux-modules-extra-2.6 (2.6.26-6)

I don't understand what's failing in the code and I've looked at it a
couple of times now.  I think it needs more eyeballs.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>



Reply to: