Hi!
Could someone look at "nevow" in the repository. I have upgraded it to
use dh_python2 (from python-central). However, the "Python-Version"
field in the binary package did disappear, ${python:Breaks} is expanded
to nothing and I have a new lintian warning.
debian/control (partial):
Source: nevow
Build-Depends: debhelper (>= 5.0.38), cdbs (>= 0.4.90~),
python (>= 2.6.6-3), python-setuptools (>= 0.6b3)
Build-Depends-Indep: python-twisted-core (>= 10.1.0-1~),
python-twisted-web (>= 10.1.0-1~),
python-twisted-lore
X-Python-Version: >= 2.4
Package: python-nevow
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, dpkg (>= 1.14.17~),
python-twisted-core (>= 10.1.0-1~), python-twisted-web (>= 10.1.0-1~)
Provides: ${python:Provides}
Replaces: python2.3-nevow (<< 0.7.0-1.1), python2.4-nevow (<< 0.7.0-1.1)
Breaks: python2.3-nevow (<< 0.7.0-1.1), python2.4-nevow (<< 0.7.0-1.1),
${python:Breaks}
The lintian warning:
W: python-nevow: old-versioned-python-dependency depends: python (<< 2.7)
N:
N: This package appears to be an architecture-independent Python module but
N: has a dependency on a version of python less than a particular version,
N: doesn't use python-support and no Python-Version control field. This
N: normally means that the package isn't using the current Python policy;
N: most architecture-independent Python packages will work with any future
N: version of Python if they follow the new policy.
N:
N: If this package really does require only a particular range of Python
N: versions and uses python-central, add a Python-Version control field (as
N: described in 2.3 of the Python policy) to resolve this warning.
N:
N: Severity: normal, Certainty: certain
Shouldn't dh_python2 add the Python-Version field?
Thanks!
--
BOFH excuse #412:
Radial Telemetry Infiltration
pgpuoFLZ8tl6q.pgp
Description: PGP signature
