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