Joey Hess wrote:
> 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..
I've fixed cherrypy3 in the modules team'
Joey Hess wrote:
> 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..
yeah, fully understandable and a bit unfo
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 repla
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 \
>
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/sb
5 matches
Mail list logo
