On Sun, Feb 24, 2013 at 4:12 AM, Julien Cristau <jcris...@debian.org> wrote: > On Sun, Feb 24, 2013 at 03:42:06 -0800, Vincent Cheng wrote: > >> Andreas, if I understood your analysis of #700782 correctly, the >> hypothetical situation that an user unpacks any of the affected >> packages (or an older version prior to being rebuilt against >> python3.2-dev (>= 3.2.3-7)) before python3.2-dev to trigger this bug >> still exists, right? In that case, python3.2-dev should probably still >> add a Conflicts: relationship with all of the affected packages; I >> wonder if Matthias might have anything to say about this? >> > Very much NAK to adding conflicts against packages at this stage, > especially for issues that don't affect the upgrade path from squeeze > (where there's no python3.2). >
Fair enough, I'll leave it to your discretion whether to tag #701071 and #701045 as wheezy-ignore, or just close them altogether. The rest of the bugs need at least a binNMU (rebuild against the fixed python3.2-dev package) before they can be closed. Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
