On 04/14/2012 06:55 PM, Benj. Mako Hill wrote: > Thanks for the detailed feedback on the package! Apologies that I > forgot the build dep. > > <quote who="Julian Taylor" date="Sat, Apr 14, 2012 at 06:17:30PM +0200"> >> changing from non-setuptools to setuptools based builds withing a debian >> revision should not be done. > > What? Where is this documented?
to my knowledge its not documented properly. The issue comes from dh_python2's symlinking between modules and dpkg's special rules for directories and symlinks. The actual upgrade failure is dependent on a bunch of factors (like the file system of the build machine) so it might not be easily reproducible. Fixing it in dh_python2 is on POX's todo list but I don't think its done yet. It probably also disappears when python2.6 is removed. now that -2 is using dh_python2 you have following options: - using a temporary preinst like foolscap (definitely works) - reverting back to pysupport (maybe works) - Temporarily conflicting with -2 (maybe works, Breaks is not enough) or not care about the people who already updated in unstable upgrades from -1 to -3 will work as the issue does not occur on pysupport -> dh_python2 upgrades. > >> Also the dh_python2 conversion (which was not even mentioned in the >> changelog!) was done wrongly. > > I did not attempt to do a dh_python2 conversion so I did not mention > it in the changelog and I'm sorry it happened and happened wrongly. > >> Please follow http://wiki.debian.org/Python/TransitionToDHPython2 and >> take note of jakubs comments in this bug. > > Sure. I'll do this. also note this warning dh_python2 outputs: W: dh_python2:90: Python 2.7 should install files in /usr/lib/python2.7/dist-packages/. Did you forget "--install-layout=deb"?
signature.asc
Description: OpenPGP digital signature
