Bug#373853: dh_python generated wrong substvars
On Sat, 17 Jun 2006, Matthias Klose wrote: it's correct that we do have the information of = 2.4 in the dependency, _iff_ we have a dependency on python (= 2.4), but this dependency isn't generated if the module just included .py files which do _not_ have a hashbang line (but maybe that's another bug). Yes that's another bug. The python dependency is generated only if python programs or if python modules are found. But dh_python only looks in standard paths and it won't look in /usr/share/pycentral or /usr/share/python-support... I'll fix this. A = 2.4 in the version fields doesn't hurt and we can get this information from exactly one place. OK. I'll provide an updated dh_python soon. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
Bug#373853: dh_python generated wrong substvars
it's correct that we do have the information of = 2.4 in the dependency, _iff_ we have a dependency on python (= 2.4), but this dependency isn't generated if the module just included .py files which do _not_ have a hashbang line (but maybe that's another bug). A = 2.4 in the version fields doesn't hurt and we can get this information from exactly one place. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#373853: dh_python generated wrong substvars
On Fri, 16 Jun 2006, Piotr Ozarowski wrote: I have following line in debian/control (source section) XS-Python-Version: = 2.4 and in generated *.substvars file: python:Versions=all Is your package arch: all? If that's the case, then it's normal. The Python-Version: field in the *binary* package is there to document if the package needs update to work with a new python version. That's the only reason why it has been introduced. Basically, you have 3 cases: - the package is arch: all and uses python-support/python-central to make it available to all the versions known to work with it = we get all = no update is needed for a new python version - the package has private modules, and those are byte-compiled for the current python version = we get current = no update is needed as the modules are byte-compiled again for the new version - the package contains extensions (and/or public modules not shared, ie installed in /usr/lib/python2.X/site-modules) and you get the explicit list of versions supported = in general we get 2.3, 2.4 but you might as well get 2.3 or 2.4 = update is needed if the new version is not listed in the field You could replace all by all, = 2.4 but it doesn't bring anything. This information is already in the Depends field and in the Python-Version of the source package. If you agree with this reasoning, feel free to close the bug. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
Bug#373853: dh_python generated wrong substvars
severity 373853 wishlist
thanks
Raphael Hertzog ([EMAIL PROTECTED]):
On Fri, 16 Jun 2006, Piotr Ozarowski wrote:
I have following line in debian/control (source section)
XS-Python-Version: = 2.4
and in generated *.substvars file:
python:Versions=all
Is your package arch: all?
yes, it is
If that's the case, then it's normal. The Python-Version: field in the
*binary* package is there to document if the package needs update to work
with a new python version. That's the only reason why it has been
introduced.
(New) Debian Python Policy, section 2.3:
| Your control file should also have a line:
|
| XB-Python-Version: ${python:Versions}
|
|The python:Versions is substituted by the supported Python versions of the
|binary package, based on XS-Python-Version. (If you are not using dh_python you
|will need to handle this substitution yourself.) The format of the field
|XB-Python-Version is the same as the XS-Python-Version field for packages not
|containing extensions. Packages with extensions must list the versions
|explicitely.
my package doesn't support python 2.3, that's why I have reported bug (other
packages
could have similar problem, thats why I used important severity)
If it's expected behaviour, please clarify the policy - I asked about that on
#debian-python before reporting bug and nobody told me what you just did
If you agree with this reasoning, feel free to close the bug.
I have changed severity level, please close bug after policy will be updated
(or is it only me who get it wrong?)
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpmaICfcEKcp.pgp
Description: PGP signature
Bug#373853: dh_python generated wrong substvars
Package: debhelper Version: 5.0.37.1 Severity: important I have following line in debian/control (source section) XS-Python-Version: = 2.4 and in generated *.substvars file: python:Versions=all since python2.3 is still supported, I think it shouldn't be all note that `pyversions -r '=2.4'` is generating python2.4 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.12-grsec Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) Versions of packages debhelper depends on: ii binutils 2.16.1cvs20060413-1 The GNU assembler, linker and bina ii coreutils5.96-3 The GNU core utilities ii dpkg-dev 1.13.21 package building tools for Debian ii file 4.17-2 Determines file type using magic ii html2text1.3.2a-3An advanced HTML to text converter ii perl 5.8.8-6 Larry Wall's Practical Extraction ii po-debconf 1.0.2 manage translated Debconf template debhelper recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
