Package: libroot-python-dev Version: 5.18.00-2.3 Hi,
currently, the libroot-python-dev package contains a symbolic link from /usr/lib/python-support/pythonX.Y to a private directory of root-system. With the upcoming version of python-support (currently in experimental), the files installed in /usr/lib/python-support are ignored and the built package is, as such, broken. (Note that the packages already built will not break upon upgrade, only those built against the newer python-support version will fail.) You should probably do this linkage before dh_pysupport and dh_link for it to work, but in all cases it looks a bit hackish to me. The usual solution in this situation is to link the files the other way round: ship only public modules, and for several Python versions, then make the private stuff use the public one way or another. In all cases, this doesn’t look like an easy thing to do with such a complex package. If it turns out to be too complex, we can simply synchronize at the moment of the upload of the newer python-support to unstable. Thanks, -- .''`. Debian 5.0 "Lenny" has been released! : :' : `. `' Last night, Darth Vader came down from planet Vulcan and told `- me that if you don't install Lenny, he'd melt your brain.
signature.asc
Description: Ceci est une partie de message numériquement signée
