Bernd Zeimetz wrote: > Right, but imho that problem here is a bug in the package, not in the way dh > works now. The right way to fix it would be to patch setup.py to install the > file at the right place in /usr/sbin. That's not a problem for distutils. > > It is also easy to work around by replacing python* by something like > `pyversions -d`. Python modules and extensions should always be built with all > Python versions, or the versions to build with should be limited via > pyversions. > > In theory it would be enough to build modules with the default python version > only - but there is no sane way to distinguish between modules and extensions, > so building with all Python versions is the only sane way I can think of. > > Are there more Python related FTBFS popping up? I'd be happy to file bugs and > patch them, as long as no major regression pops up.
It'll be a while before my build gets to the main cluster of python packages, and there arn't too many that could be affected, but we will need to get bugs filed at least. I don't normally let debhelper releases break back-compat.. -- see shy jo
signature.asc
Description: Digital signature
