Comment 6 for bug 633015

RE: SRU

I can confirm the -proposed packages resolves this issue in Lucid.

It might be a good idea for someone else to separately verify this -proposed package before changing the tag. The process to test is to grab a package that has a binary file (foo) in the orig tarball... dpkg-source -x it, overwrite the upstream binary in the extracted location; and echo "foo" > debian/source/include-binaries.

I have a sample package this can be proved against if needed.

The LP generated diff concerns me somewhat, but seems to be a LP bug.... see below:

<Daviey> lifeless / maxb: https://launchpad.net/ubuntu/lucid/+source/dpkg/1.15.5.6ubuntu4.4
<Daviey> The diff LP has generated is: http://launchpadlibrarian.net/57004735/dpkg_1.15.5.6ubuntu4.2_1.15.5.6ubuntu4.4.diff.gz
<Daviey> which is against *4.2
<Daviey> https://launchpad.net/ubuntu/+source/dpkg/1.15.5.6ubuntu4.2/+publishinghistory <--- is odd
<Daviey> *.1 is marked Superseded by 4.3 !
<Daviey> *.2 isn't marked superseeded, just deleted with the comment "moved to -updates"
<Daviey> The debian/changelog for 4.3 doesn't mention 4.1 (oddly)
<Daviey> In any case, LP is giving an incorrect diff to me.... :/
<Daviey> (if you debdiff 4.3 and 4.4, you get the diff i expected.
<Daviey> ^^ Downloading the .dsc's from launchpad.
<maxb> Daviey: 4.3 was a security update
<maxb> Therefore, at the time 4.4 was uploaded to proposed, it's possibly that 4.2 was still the latest in the updates pocket?
* maxb curses at the difficulty of finding a link to https://launchpad.net/ubuntu/+source/dpkg/+publishinghistory, and manually composes the URL

<maxb> hmm, apparently not, 4.3 was copied to updates long before 4.4 hit proposed
<maxb> oh, gah, I bet LP saw that there was an earlier dpkg in lucid-proposed, and didn't check other pockets