Re: dpkg-repack warnings: what effect?
Le lundi 24 juillet 2006 à 23:18 -0500, Joe Wreschnig a écrit : > (Or, finally announce that Python 2.4 is plain too late for etch. Then > people can have as long as they want to debate over this crap, and > Python developers can just give up hope.) Well, isn't the whole purpose of that new policy stuff to delay python 2.4? -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: Ceci est une partie de message numériquement signée
Re: dpkg-repack warnings: what effect?
On Tue, 2006-07-25 at 14:27 +0200, Josselin Mouette wrote: > Le lundi 24 juillet 2006 à 23:18 -0500, Joe Wreschnig a écrit : > > (Or, finally announce that Python 2.4 is plain too late for etch. Then > > people can have as long as they want to debate over this crap, and > > Python developers can just give up hope.) > > Well, isn't the whole purpose of that new policy stuff to delay python > 2.4? Oh, so it's not possible for someone to be an irresponsible maintainer without being an Ubuntu shill as well? When did they hire you, then? (Yes, this message isn't constructive, but I'm beyond caring.) -- Joe Wreschnig <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Generation of "python" dependencies for public extensions versus python2.3
Hi, While trying to install the packages from experimental where python is python2.4, I was surprized by the non-upgradability of the python-gmenus package (from gnome-menus): it is built with XS-Python-Version set to current, and ends up with: Depends: libc6 (>= 2.3.6-6), libglib2.0-0 (>= 2.10.0), libgnome-menu2 (>= 2.14.0), python-central (>= 0.5), python (>= 2.3), python (<< 2.4) Python-Version: 2.3 Since "current" was 2.3 when it was built, it ships files below /usr/lib/python2.3, so why doesn't it end with a python2.3 dependency instead of pure python dependencies? And why does it "conflict" with a "python" 2.4? The extension would certainly still work when used from python2.3 after the switch, and this seems to make upgrades harder. Bye, -- Loïc Minier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Move to python 2.4 / Changing the packaging style for python packages
Matthias, On Tue, Jun 13, 2006, Matthias Klose wrote: > We will prepare the transition in experimental by an upload of the > python, python-dev packages I tried testing my rtupdates scripts by installing "python" version 2.4.3-5 from experimental, but they didn't seem to run, and I couldn't find anywhere in the maintainer scripts of the python package a place where they would be run. Is this feature already included in the python packages? In experimental? Or do I need to depend on something? I checked the python package from http://people.debian.org/~doko/pythontst/, and its maintainer scripts didn't seem to have the feature either. Bye, -- Loïc Minier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Generation of "python" dependencies for public extensions versus python2.3
On Tue, 2006-07-25 at 22:07 +0200, Loïc Minier wrote: > Hi, > > While trying to install the packages from experimental where python > is python2.4, I was surprized by the non-upgradability of the > python-gmenus package (from gnome-menus): it is built with > XS-Python-Version set to current, and ends up with: > Depends: libc6 (>= 2.3.6-6), libglib2.0-0 (>= 2.10.0), > libgnome-menu2 (>= 2.14.0), python-central (>= 0.5), python (>= > 2.3), python (<< 2.4) > Python-Version: 2.3 > > Since "current" was 2.3 when it was built, it ships files below > /usr/lib/python2.3, so why doesn't it end with a python2.3 dependency > instead of pure python dependencies? And why does it "conflict" with a > "python" 2.4? The scripts in /usr/lib/python2.3/site-packages/GMenuSimpleEditor call plain "python". That's probably causing the dependency. There's another bug in the gnome-menus package too: $ dpkg -s gnome-menus | grep Depends Depends: libc6 (>= 2.3.6-6), libglib2.0-0 (>= 2.10.0), libgnome-menu2, python (>= 2.3), python (<< 3), python-gmenu (= 2.14.0-3), python-glade2 So gnome-menus claims to work with 2.4. But in the package /usr/bin/gmenu-simple-editor has: #!/usr/bin/env python ... if not "/usr/lib/python2.3/site-packages" in sys.path: sys.path.insert (0, "/usr/lib/python2.3/site-packages") In other words, it will load the 2.3 extension even when it's running on Python 2.4. That's bad. Why hasn't this been updated to support multiple versions of Python? That's what public extensions should do now. -- Joe Wreschnig <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Re: Generation of "python" dependencies for public extensions versus python2.3
On Tue, Jul 25, 2006, Joe Wreschnig wrote: > The scripts in /usr/lib/python2.3/site-packages/GMenuSimpleEditor call > plain "python". That's probably causing the dependency. Ok, I suspected this, but since there was no other python2.3 depends, I thought there was something wrong in the first place. > There's another bug in the gnome-menus package too: Ouch, thanks for spotting this. > Why hasn't this been updated to support multiple versions of Python? > That's what public extensions should do now. Because it has a single rdep within the same source package, gnome-menus. I'll try to strip the shebangs of the private module and see whether it helps, if not I will resort to building for all available python versions, even if only one will actually be used. :-/ Thanks, -- Loïc Minier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
