Bug#507849: lintian.d.o run finished, source/binary mismatch not quite fixed
Russ Allbery <rra@debian.org> writes:
> I'm not sure that we fixed the problem with binary versus source package
> versioning. Look at:
>
> http://lintian.debian.org/maintainer/debian-kernel@lists.debian.org.html
>
> specifically the the linux-latest package. binary-info has:
>
> linux-modules-xen-686;2.6.26+17;linux-latest-2.6;2.6.26+17;pool/main/l/linux-latest-2.6/linux-modules-xen-686_2.6.26+17_i386.deb;1228953725
>
> which shows a source package version of 2.6.26+17. But the
> corresponding source package version is 17, as one can see from (for
> example) the Source field in the linux-modules-xen-686/control/control
> file in the lab.
I'm at a loss. Retracing all that list-binpkg does, I can't see where it
would have gotten that incorrect value for $source_version. The command
that reproduces what's happening is:
ar p /org/ftp.debian.org/ftp/pool/main/l/linux-latest-2.6/linux-modules-xen-686_2.6.26+17_i386.deb control.tar.gz | tar --wildcards -xzO -f - '*control' | env LINTIAN_ROOT=/org/lintian.debian.org/root perl -MUtil -e 'my ($data) = parse_dpkg_control(\*STDIN); print $data->{source}, "\n"; print join(" ", $data->{source} =~ /^([-+\.\w]+)\s+\((.+)\)$/), "\n"'
and it produces the right output:
linux-latest-2.6 (17)
linux-latest-2.6 17
the second being the parsed version using the regex in list-binpkg. Yet
for some reason this didn't work.
I'm going to try regenerating the package list by hand and see if I come
up with any different results.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: