* Maximiliano Curia <m...@debian.org>, 2010-07-31, 19:17:
The problem is that the packages compiles twice, once for every supported python version. But things like plugins have a static destination (not dependant of the python version), so its overwritten.
This is not bad per se, as long it's not the default version which is overwritten.
The simplest solution would be to support only one python version at any given time.
That would be an unfounded regression. We do want public Python extensions to be compiled with multiple Python versions.
Other options would need to create one package per python version supported, or make the plugins package dependant of all the available python versions at any given time.
Uhh, that would mean that the package needs a sourceful upload by every Python transition. No, that's exactly kind of thing turns transitions into hell.
I would prefer the first option, but its clearly an argumentable decision, so I'll wait a few days before nmuing this trivial fix. --- jppy-0.0.56/debian/control 2010-07-31 18:05:03.000000000 -0400 +++ jppy-0.0.56.new/debian/control 2010-07-31 17:12:53.000000000 -0400 @@ -8,7 +8,7 @@ Vcs-Git: git://git.debian.org/git/jppy/jppy.git Vcs-Browser: http://git.debian.org/?p=jppy/jppy.git Homepage: http://jppy.alioth.debian.org/ -XS-Python-Version: >= 2.5 +XS-Python-Version: = 2.6 Package: python-jppy Section: python
Please don't. "XS-Python-Version: = 2.6" is not even valid syntax, according to Python Policy.
-- Jakub Wilk
signature.asc
Description: Digital signature
