On Thu, 2006-06-15 at 13:44 +0200, Pierre Habouzit wrote: > Le jeu 15 juin 2006 13:36, Piotr Ozarowski a écrit : > > Pierre Habouzit (madcoder@debian.org): > > > > well the thing is there is no way to track all the packages that > > > *have* to follow the python subpolicy, and that makes the work of > > > tracking them for transition harder. > > > > > > I think/thought it makes sense that a source package lists all the > > > subpolicies it's supposed to follow, because it makes our lifes > > > easier. > > > > You can't bump Standards-Version number if your package is not > > following *all* standards (i.e subpolicies). > > > > The fact is that python policy is not official yet (at least document > > on d.o is not updated) and > > /usr/share/doc/debian-policy/upgrading-checklist.txt.gz > > doesn't mention about new python policy at all. > > we are not talking about the same target. My goal is to be able to spot > every package that has to conform to the python subpolicy by just > listing those fields. Obviously the Standards-Version is bumped also, > but it's not distinctive of python and not python related packages. This isn't really helpful now. Many packages have been uploaded already, without this field. Anything conforming to the new policy has XS-Python-Version. That seems to be enough to detect that it's been migrated. -- Joe Wreschnig <piman@sacredchao.net>
Attachment:
signature.asc
Description: This is a digitally signed message part