> Le lundi 05 novembre 2007 à 15:40 +0100, Piotr Ożarowski a écrit : > > Hi Fabrizio > > > > > I am looking for sponsorship for my new python module: python-avc, > > > ITP http://bugs.debian.org/448646, > > > mentors http://mentors.debian.net/debian/pool/main/p/python-avc. > > > > * remove "Provides: ${python:Provides}" - architecture independent ^^^^^^^^^^^^^^^^^^^^^^^^ > > packages don't need it > > Of course they do. What if a package Depends: python2.5, python2.5-avc? Depends: python2.5, python-avc (>=new_policy_version) Joss, python2.5-avc is not in new policy spirit. Think about this situation: Fabrizio is uploading this package now, it provides python2.4-avc and python2.5-avc. Some packages are depending on python2.4-avc and then 2.4 is removed from supported Python versions. Should Fabrizio upload new version just because 2.4 is no longer supported? Should he upload new version when 2.6 will be added? What with package that still depends on python2.4-avc? Why do we have python-central and python-support then? Please note that I'm talking about architecture *independent* packages. Architecture dependent package *have to* provide pythonX.Y-module. Fabrizio: you're added, welcome in the team :-) -- -=[ Piotr Ozarowski ]=- -=[ http://www.ozarowski.pl ]=-
Attachment:
pgplZuOaa1cxW.pgp
Description: PGP signature