Joey Hess wrote:
> My test build of all packages that use dh or dh_auto_*
> will be running for the next several days.
>
> Preliminary testing to see what this change breaks suggests
> it's not all smooth sailing:
>
> mv debian/python-cherrypy3/usr/lib/python*/*/cherrypy/cherryd \
> debian/python-cherrypy3/usr/sbin/
> mv: will not overwrite just-created
> `debian/python-cherrypy3/usr/sbin/cherryd' with
> `debian/python-cherrypy3/usr/lib/python2.5/site-packages/cherrypy/cherryd'
>
> Presumably this is now building multiple versions of
> the file for different python versions which breaks
> the assumption in this code.
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.
--
Bernd Zeimetz Debian GNU/Linux Developer
GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
