Bug#509697: Python 2.5, ctypes, and binutils
* Sandro Tosi [Wed, 31 Dec 2008 14:58:43 +0100]: Hi all, reporting here what discussed with Adeodato on irc: On Fri, Dec 26, 2008 at 17:04, Adeodato Simó d...@net.com.org.es wrote: Regarding #509697 (python 2.5 providing ctypes, and ctypes using objdump), I don't think it's reasonable to make python2.5 depend on binutils, just for the purpose of one of the modules in the standard library. One option would be to add binutils to Recommends or Suggest, but that does not ensure packages that Depend: python-ctypes will work. Maybe python should stop Providing: python-ctypes, and python-ctypes should depend on python (= 2.5) | python2.4 instead of just python2.4 (plus the recently added a dependency on binutils). This way binutils will get pulled only when a package that depends on python-ctypes is installed. (This does not solve, however, packages that are being smart and are depending on python (= 2.5) | python-ctypes. But maybe those packages should stop doing that.) If this is the way to go, then for squeeze it means that, if the ctypes source package is to disappear, it should be created as a dummy package (from python-defaults instead?), if only to contain the binutils depends/recommends. Of course, upload again ctypes to update the depends it's pretty easy; what it's a little bit more critical are the smarts rdepends that currently Deps on python (= 2.5) | python-ctypes; those are: $ grep-available -FDepends,Recommends,Suggests python-ctypes | python (= 2.5) -o -FDepends,Recommends,Suggests python (= 2.5) | python-ctypes -sPackage Package: python-musicbrainz2 Package: telepathy-butterfly Package: python-elisa Package: python-utidylib Package: python-msn Package: python-opengl Package: python-pyglet Now, even since they're not that many, and nmus (if the maints won't react in a timely fashion) could be done, my fear (partially shared with dato) if this is the right time for this mini-migration, due to the hard freeze is coming ReallySoonNow. I'd like to hear from you what's you're thinking. The Python maintainer introduced in python2.5 2.5.2-15 a patch to implement find_library() using ldconfig first, which should be available everywhere; and only if that fails, use objdump. The theory is that packages that know/discover ldconfig won't be enough, should gain a dependency on binutils. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org Listening to: Presuntos Implicados - La alegría -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509697: Python 2.5, ctypes, and binutils
On Wed, Dec 31, 2008 at 14:58, Sandro Tosi mo...@debian.org wrote: $ grep-available -FDepends,Recommends,Suggests python-ctypes | python (= 2.5) -o -FDepends,Recommends,Suggests python (= 2.5) | python-ctypes -sPackage Package: python-musicbrainz2 Package: telepathy-butterfly Package: python-elisa Package: python-utidylib Package: python-msn Package: python-opengl Package: python-pyglet better command, to catch even uber-smart depends: $ grep-available -FDepends,Recommends,Suggests python-ctypes | python (= 2.5) -o -FDepends,Recommends,Suggests python (= 2.5) | python-ctypes -o -FDepends,Recommends,Suggests python2.5 | python-ctypes -o -FDepends,Recommends,Suggests python-ctypes | python2.5 -sPackage Package: python-coherence Package: python-musicbrainz2 Package: telepathy-butterfly Package: python-elisa Package: python-utidylib Package: python-msn Package: python-opengl Package: python-pyglet Now, since unstable ctypes upload was caught by libffi soname bump, and probably needs a tpu upload (please RT confirm this or if libffi5 will be migrated in lenny) it's an additional reason to decide about the situation explained above. Cheers, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509697: Python 2.5, ctypes, and binutils
Hi all, reporting here what discussed with Adeodato on irc: On Fri, Dec 26, 2008 at 17:04, Adeodato Simó d...@net.com.org.es wrote: Regarding #509697 (python 2.5 providing ctypes, and ctypes using objdump), I don't think it's reasonable to make python2.5 depend on binutils, just for the purpose of one of the modules in the standard library. One option would be to add binutils to Recommends or Suggest, but that does not ensure packages that Depend: python-ctypes will work. Maybe python should stop Providing: python-ctypes, and python-ctypes should depend on python (= 2.5) | python2.4 instead of just python2.4 (plus the recently added a dependency on binutils). This way binutils will get pulled only when a package that depends on python-ctypes is installed. (This does not solve, however, packages that are being smart and are depending on python (= 2.5) | python-ctypes. But maybe those packages should stop doing that.) If this is the way to go, then for squeeze it means that, if the ctypes source package is to disappear, it should be created as a dummy package (from python-defaults instead?), if only to contain the binutils depends/recommends. Of course, upload again ctypes to update the depends it's pretty easy; what it's a little bit more critical are the smarts rdepends that currently Deps on python (= 2.5) | python-ctypes; those are: $ grep-available -FDepends,Recommends,Suggests python-ctypes | python (= 2.5) -o -FDepends,Recommends,Suggests python (= 2.5) | python-ctypes -sPackage Package: python-musicbrainz2 Package: telepathy-butterfly Package: python-elisa Package: python-utidylib Package: python-msn Package: python-opengl Package: python-pyglet Now, even since they're not that many, and nmus (if the maints won't react in a timely fashion) could be done, my fear (partially shared with dato) if this is the right time for this mini-migration, due to the hard freeze is coming ReallySoonNow. I'd like to hear from you what's you're thinking. With the occasion, I'd like to wish a Happy New Year to all of you, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509697: Python 2.5, ctypes, and binutils
Regarding #509697 (python 2.5 providing ctypes, and ctypes using objdump), I don't think it's reasonable to make python2.5 depend on binutils, just for the purpose of one of the modules in the standard library. One option would be to add binutils to Recommends or Suggest, but that does not ensure packages that Depend: python-ctypes will work. Maybe python should stop Providing: python-ctypes, and python-ctypes should depend on python (= 2.5) | python2.4 instead of just python2.4 (plus the recently added a dependency on binutils). This way binutils will get pulled only when a package that depends on python-ctypes is installed. (This does not solve, however, packages that are being smart and are depending on python (= 2.5) | python-ctypes. But maybe those packages should stop doing that.) If this is the way to go, then for squeeze it means that, if the ctypes source package is to disappear, it should be created as a dummy package (from python-defaults instead?), if only to contain the binutils depends/recommends. Comments welcome. -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org When all is summed up, a man never speaks of himself without loss; his accusations of himself are always believed; his praises never. -- Michel de Montaigne -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
