On Tue, Sep 17, 2013 at 6:20 PM, Stuart Prescott <stu...@debian.org> wrote: > The introduction of the dependency "python3:any (>= 3.2.3-3~)" in a number of > python3 packages should require that python3 be upgraded to at least version > 3.3.0-2 since that is the first version that is marked as Multi-Arch: allowed. […] > However, wheezy's apt appears to think that the non-multi-arch'd python3 > package in wheezy satisfies this dependency (the version is sufficient but the > :any requires a Multi-Arch: allowed package).
Can you confirm that this only happens on single-arch systems? The attached patch seems to fix that (but I only tested with the included testcase). As its trivial it should be possible to get it into a point-release. I would say its a good idea to raise the versionnumber non-the-less for all the people who are naughty and don't follow point-releases. And its more correct / less confusing, as its not an completely bogus idea to strip :any in single architecture environments. It has no meaning there anyway, right? ;) Best regards David Kalnischkies
0001-don-t-strip-any-from-dependencies-in-single-arch.patch
Description: Binary data
