Bug#700782: Bug#700997: Bug#700995: Solving directory vs. symlink conflict: /usr/include/python3.2
[Adding python3.2's maintainer, as well as #701071 and #701045, to cc:] On Sat, Feb 23, 2013 at 3:55 AM, Julien Cristau jcris...@debian.org wrote: On Fri, Feb 22, 2013 at 09:32:45 +0100, Andreas Beckmann wrote: On 2013-02-22 08:51, Vincent Cheng closed #700997: * [...] distutils in Debian now takes care of installing headers into the right location as of python3.2 (= 3.2.3-7), so add a build-dep on that [...] Maybe a solution for the other packages, too. Sounds like all of these bugs should be reassigned to python3.2-dev then, and closed? Someone first has to manually check that these packages use distutils (look for something along the lines of python setup.py install --install-layout=deb in debian/rules) and doesn't move around stuff manually in debian/rules or elsewhere; binNMUs should then be safe (although I still think source uploads to get python3.2-dev (= 3.2.3-7) added to build-depends of each of these packages should be done). I'll get around to looking at the rest of these bugs (eventually), as they should be easy to fix in the above holds true. 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? Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700782: Bug#700997: Bug#700995: Solving directory vs. symlink conflict: /usr/include/python3.2
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). Cheers, Julien signature.asc Description: Digital signature
Bug#700782: Bug#700997: Bug#700995: Solving directory vs. symlink conflict: /usr/include/python3.2
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
