Bug#624321: libconfig-model-perl: Doesn't know about control fields for Python packages

[Stefano Rivera]

Hi Dominique (2011.04.27_23:12:09_+0200)
> > I suppose, if you do support this, it would be nice to migrate
> > XS-Python-Version / debian/pyversions to X-Python-Version.
> 
> No problem. I guess that copying the content of XS-Python-Version or 
> debian/pyversions into X-Python-Version is enough. Is this right?

Yes and no. X-Python-Version is stricter than XS.
It can't mention 3.x (which never made any sense in XS), only 2.x.
It can't be "current".
It can't contain a list of versions, only ">= 2.X" and/or "<< 2.Y"

debian/pyversions contains ranges like "2.X" or "2.X-" or "2.X-2.Y"
rather than dpkg-like comparisons.

Yeah, it's complex. Maybe ignore it :)

> > X-Python-Version requires a BD on python{,-all}{,-dev,-dbg} (>= 2.6.5-13~)
> 
> I don't understand this one. Do you have some examples ?

X-Python-Version can only be understood by the pyversions script
included in the python package (which is commonly depended on via
python-dev, python-all, python-dbg, or python-all-dbg) since 2.6.5-13.

So whenever X-Python-Version is used, there should be a versioned
build-dependency on one of those packages. That is something lintian
should enforce, not you, but if you are doing automated migrations, you
need to be aware of it.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  H: +27 21 465 6908 C: +27 72 419 8559  UCT: x3127