Bug#505001: soya: Include debian/pyversions file, remove debian/pycompat
OoO En ce début d'après-midi nuageux du samedi 08 novembre 2008, vers 14:31, Iain Lane [EMAIL PROTECTED] disait : I've just merged your package with our Ubuntu-local changes and thought to forward the delta back to you for your consideration. We add a debian/pyversions file to comply with the python policy at [0] From my reading, debian/pyversions seems optional if soya does not require a particular Python version. I cannot guarantee that soya would work with all existing Python versions but it works with the current Python version of stable and all currently supported version in Lenny and unstable, therefore I think that debian/pyversions is not useful (based on the fact that we drop too old dependency information). Tell me if you agree. We can also seek advice on debian-python@ if needed. and remove debian/pycompat. I note that you said you'd removed this in the latest upload to experimental but I still see this in the package. You are right. It seems that I did not compile soya in a clean environment because I don't see debian/pycompat in the SVN repository. Therefore, it will be dropped with next upload. -- SHERRI DOES NOT GOT BACK SHERRI DOES NOT GOT BACK SHERRI DOES NOT GOT BACK -+- Bart Simpson on chalkboard in episode AABF07 pgphG6u3fWt3w.pgp Description: PGP signature
Bug#505001: soya: Include debian/pyversions file, remove debian/pycompat
Vincent Bernat wrote: OoO En ce début d'après-midi nuageux du samedi 08 novembre 2008, vers 14:31, Iain Lane [EMAIL PROTECTED] disait : I've just merged your package with our Ubuntu-local changes and thought to forward the delta back to you for your consideration. We add a debian/pyversions file to comply with the python policy at [0] From my reading, debian/pyversions seems optional if soya does not require a particular Python version. I cannot guarantee that soya would work with all existing Python versions but it works with the current Python version of stable and all currently supported version in Lenny and unstable, therefore I think that debian/pyversions is not useful (based on the fact that we drop too old dependency information). Hi, Sure, I think that's a fair viewpoint. I just added it for some value of semantic correctness, based on the compatibility that upstream list on their website. I don't think it particularly makes any technical difference. btw, I just noticed that pycompat wasn't removed from my debdiff either. Further investigation reveals that the cdbs python-distutils class insists on creating it. I've deleted it in the clean:: target in the rules file for now. Iain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#505001: soya: Include debian/pyversions file, remove debian/pycompat
Package: soya Version: 0.14-1 Severity: minor Tags: patch User: [EMAIL PROTECTED] Usertags: origin-ubuntu jaunty ubuntu-patch Hi, I've just merged your package with our Ubuntu-local changes and thought to forward the delta back to you for your consideration. We add a debian/pyversions file to comply with the python policy at [0], and remove debian/pycompat. I note that you said you'd removed this in the latest upload to experimental but I still see this in the package. In Ubuntu, we've applied the attached patch to achieve the following: * Merge from Debian experimental (LP: #295540), remaining changes: - Add debian/pyversions file * Remove debian/pycompat Thanks, Iain [0] http://wiki.debian.org/DebianPython/NewPolicy -- System Information: Debian Release: lenny/sid APT prefers intrepid-updates APT policy: (500, 'intrepid-updates'), (500, 'intrepid-security'), (500, 'intrepid-proposed'), (500, 'intrepid-backports'), (500, 'intrepid') Architecture: amd64 (x86_64) Kernel: Linux 2.6.27-7-generic (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- soya-0.14.orig/debian/pyversions +++ soya-0.14/debian/pyversions @@ -0,0 +1 @@ +2.2-
