Hi, On Thu, Nov 09, 2006, Alexandre Fayolle wrote: > I'm trying to build and upload a new release of python-psyco, and the > built package is wrong because `pyversions -r debian/control` returns > python2.4 even though debian/control says that XS-Python-Version is > >=2.2, << 2.6. > > I have python-all installed, so I would expect the call to pyversions to > return python2.3 python2.4 python2.5
I think what you describe is correct behavior. pyversions was changed so that we can get rid of python2.3, and this means we should not build any new packages against python2.3, and rebuilds will hence lose their "python2.3-" virtual provide. Concerning python2.5, it's not enabled yet because it's not expected to be the default version in etch, but I suppose it could be now that it is officially released and in sync in etch. > Any package building C extension modules rebuilt with the current setup > will only compile the C extension for python2.4, which is not what we > want. I think it is. :) My bug report is about packages which were built with a pyversions returning python2.3 and based on python-support, but not usable anymore now that pyversions does not return 2.3. Bye, -- Loïc Minier <[EMAIL PROTECTED]>
