Bug#748266: wheezy-pu: package python2.7/2.7.3-6+deb7u2

[Ian Jackson <ijackson@chiark.greenend.org.uk>]

Luis Alejandro Martínez Faneyth writes ("Bug#748266: wheezy-pu: package python2.7/2.7.3-6+deb7u2"):
> On 18/05/14 16:31, Jonathan Wiltshire wrote:
> > This is not quite correct. I could not reproduce the problem
> > upgrading a fresh 7.4 system to 7.5, nor have I seen it in the
> > wild.
> > 
> 
> Perhaps i should have been more clear on how to reproduce the bug,
> sorry. On the test case you are presenting, the bug will only happen
> if you do an aptitude safe-upgrade on a i386 machine.
> 
> > The file lists for 2.7.3-6 and 2.7.3-6+deb7u2 are identical:
> > 
> > $ debdiff python2.7_2.7.3-6_amd64.deb
> > python2.7_2.7.3-6+deb7u2_amd64.deb File lists identical (after any
> > substitutions)
> 
> Not for the i386 build, as bug #702005 says.
> 
> $ debdiff python2.7_2.7.3-6_i386.deb python2.7_2.7.3-6+deb7u2_i386.deb
> [The following lists of changes regard files as different if they have
> different names, permissions or owners.]

Do you know why these files are in the i386 but not the amd64 .deb ?

> > Only the intermediate package 2.7.3-6+deb7u1, which originated in 
> > stable-security, contains two files that do not belong to it:
...
> > According to the changelog [1] the problem was detected and fixed
> > in March, so users upgrading from 2.7.3-6 straight to
> > 2.7.3-6+deb7u2 will not see a problem. 2.7.3-6+deb7u1 was never
> > released in a DSA or through stable, so I don't believe that any
> > real users will have it installed.

Luis's comments about i386 seem to suggest that i386 users will see
the bug, in which case providing a fix in stable-updates would be the
correct approach.  Have I misunderstood ?

Thanks,
Ian.