tag 380855 - patch
severity 380855 important
thanks
On Fri, 13 Aug 2010, Jakub Wilk wrote:
> * [email protected], 2006-08-01, 12:32:
> > Hi, your package has been detected as generating a (for most of that
> >mass bug fill: private) python module/extension that may need an upgrade
> >to the new Python Policy[1].
> [...]
> > [1] http://lists.debian.org/debian-devel-announce/2006/06/msg00009.html
>
> lilypond builds a private Python extension. Such extensions are
> normally not binary compatible across different Python versions, so
> the package must declare tight dependency on the version for which
> the extension was built. The attached patch fixes this bug.
The package which could possibly need a tight dependency isn't
lilypond, but lilypond-data; secondly, lilypond-data depends on
python-support, and it properly calls dh_pysupport in its build-indep
rule, and the appropriate calls to it are made in the postinst rule.
Now, while I'm not an expert in python packaging, it seems clear that
by registering with python-support, on an upgrade to the python
interpreter, the rtupdate scripts should result in the private modules
being recompiled. If it's not, then there's a bug somewhere.
Finally, XS-Python-Version and the ${python:Depends} probably should
be added, but certainly aren't a requirement, as it shouldn't matter
for the first,[1] and should be python for the second.
Don Armstrong
1: After all, your change just indicates that it supports all version
of python which we currently distribute, which is what the absence of
that field means in the first place.
--
There are two types of people in this world, good and bad. The good
sleep better, but the bad seem to enjoy the waking hours much more.
-- Woody Allen
http://www.donarmstrong.com http://rzlab.ucr.edu
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
