Debian has switched to python2.5
Hi, for those like myself who didn't even notice, Debian has switched to python2.5 by the release team NMUing Python. So currently, some packages needs to be fixed, for example on my system, these packages now want to be removed: gimp-python hpijs hpijs-ppds hplip hplip-gui libapache2-mod-python openoffice.org openoffice.org-writer pida python-ctypes python-opengl python-subversion python-uno trac The problem is probably mainly with python-ctypes and maybe a few others. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian has switched to python2.5
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 14 Apr 2008 at 09:39:05 +0200, Ondrej Certik wrote: > So currently, some packages needs to be fixed, for example on my > system, these packages now want to be removed: > > gimp-python hpijs hpijs-ppds hplip hplip-gui libapache2-mod-python > openoffice.org openoffice.org-writer pida python-ctypes python-opengl > python-subversion python-uno trac > > The problem is probably mainly with python-ctypes and maybe a few others. To which we can add the packages that conflict with python > 2.4: lsb-core (fixed) ppmtofb and at least the following packages that depend on python << 2.5: decompyle deskbar-applet duplicity eikazo hplip libapache2-mod-python libgv-python libhdate-python libhocr-python omniidl4 pyqonsole pyslide python-aubio python-audit python-awn python-beagle python-bongoproject python-brlapi python-buffy python-celementtree python-clutter python-csound python-csoundac python-cwiid python-dballe python-dcop python-empathy python-fontforge python-galago python-galago-gtk python-gdal python-ggz python-gnuradio python-gtk-vnc python-hid python-hippocanvas python-insighttoolkit python-ipod python-jppy python-lash python-ldb python-libbtctl python-libpcap python-libvirt python-mmkeys python-ocempgui python-opencv python-pgm python-phidgets python-playerc python-pydds python-pygoocanvas python-pythonmagick python-pyxine python-setools python-sqlrelay python-subversion python-tdb python-twisted-calendarserver python-uno python-vipscc python-visual python-vtk python-wsgiref python-xpcom quantlib-python rdiff-backup xmldiff (This list is incomplete. It was obtained by attempting to upgrade my sid system and install the entire "python" section in aptitude, and inspecting the broken packages - so the only packages it includes outside the python section are those that I happened to have already. It'll probably do for a first pass, though, since it should include all the "library-ish" modules). python-ctypes, python-celementtree, python-elementtree, python-wsgiref have been subsumed by Python 2.5, so they just need to build modules for Python < 2.5 only and stop conflicting with Python 2.5 (I suspect). Hopefully there can be some sort of common strategy for these modules. Many packages (those that only build modules for the currently-default Python version, e.g. most packages that use Automake) can probably be fixed by a binNMU on all architectures: cwiid and deskbar-applet seem to do the right thing with no source changes, although I haven't tested the resulting packages. However, there's going to be some sort of horrifically huge transition to testing where everything must move simultaneously, unless we fix at least some of them to build modules for all supported Python versions (python-gobject is probably a good template for how to make Automake do this; I used it as a template when updating the python-dbus packaging). If we can do that, the Automake-using packages can trickle in to testing ahead of ython-defaults, since they'll have modules for both Python 2.4 and Python 2.5. Simon -BEGIN PGP SIGNATURE- iD8DBQFIAzINWSc8zVUw7HYRAm4lAJsGhqgOYFdxNtFbK2lSaH01bPHyEgCeP/J1 katDhVHaz+/dazqkRig2Xa0= =udX/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian has switched to python2.5
python2.5 is default since less than 24h, binNMUs were requested, please give our build daemons some time. In the mean time you can take a look at [1] and try to fix some old DPMT bugs :-) [1] http://qa.debian.org/[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bytecompiling python modules of a multipel binary source package
On lun, 2008-04-14 at 00:52 +0100, Serafeim Zanikolas wrote: > I'm packaging a set of pure python modules (ITP #473039), which are part of a > single module and share a few common files. So in /usr/share/python-support/ > we have: > > python-nodebox-web/nodebox_web/web/ (files required by all other modules) > python-nodebox-web/nodebox_web/web/wikipedia > python-nodebox-web/nodebox_web/web/yahoo > [..] > > where the non -common ones are independent of each other. > > These are packaged as > > python-nodebox-web-common > python-nodebox-web-wikipedia > python-nodebox-web-yahoo > [..] (where the latter depend on -common) This is where things are wrong. There should be one directory in /usr/share/python-support for each package, and not a single directory for the three packages. > The way I deal with this is having a .prerm script for every non -common > binary that wipes the whole directory (update-python-modules -c), and then > recreates the dir in a .postrm script (update-python-modules). This works but > requires a .prerm and .postrm scripts for every binary. (I can't use a single > pair of scripts for all, because -common must only call update-python-modules > -c. (Or I could if I could tell from within a single prerm script which > package the script is ran for.) I don’t understand why you are trying to do something so incredibly complicated. Instead, you should: 1. remove any customization that places stuff in /usr/share/python-support directly; 2. remove all the useless hacks you added as a result of this; 3. let dh_pysupport do the job of moving the right files to the right directories and add the proper prerm/postinst snippets. Cheers, -- .''`. : :' : We are debian.org. Lower your prices, surrender your code. `. `' We will add your hardware and software distinctiveness to `-our own. Resistance is futile. signature.asc Description: Ceci est une partie de message numériquement signée
Re: Debian has switched to python2.5
On Mon, Apr 14, 2008 at 12:49 PM, Piotr Ożarowski <[EMAIL PROTECTED]> wrote: > python2.5 is default since less than 24h, binNMUs were requested, please give > our build daemons some time. In the mean time you can take a look at [1] > and try to fix some old DPMT bugs :-) > > [1] http://qa.debian.org/[EMAIL PROTECTED] Yeah, I am fixing this recent RC bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475990 :) Ondrej
Bugs that'll block python 2.5
Hello guys. Yesterday about 100 binNMUs (per arch) were scheduled to rebuild stuff against the new default python version. amd64 and others seem to have attempted them all already, so I took a peek at what failed, and tagged the existing bugs (or submitted new ones) with the "goal-python2.5" usertag. So, you can find a list of the 9 FTBFSes that need attention here (these are not 7 days old yet, but patches would be always welcome): http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=goal-python2.5;[EMAIL PROTECTED] There is also in that list a couple trivial uploads that'll be needed (#476170 and #476173, though a proper patch for #476173 would be nice). Finally, and quite importantly, there is what to do with modules that have been added to the standard library in 2.5 (ctypes, celementtree, wgsiref). These use either pycentral or pysupport, and since they mark themselves as for python << 2.5 only, the dependency generated is on python (<< 2.5), rendering them uninstallable. This means that these three packages either are to be dropped, or (preferably) fixed so that they can provide modules for python 2.4 (which will still be supported for lenny), yet be co-installable with python=2.5. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org «Ara que ets la meva dona, te la fotré fins a la melsa, bacona!» -- Terenci Moix, “Chulas y famosas” -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: bytecompiling python modules of a multipel binary source package
On Mon, Apr 14, 2008 at 04:10:00PM +0200, Josselin Mouette wrote [edited]: > On lun, 2008-04-14 at 00:52 +0100, Serafeim Zanikolas wrote: [..] > This is where things are wrong. There should be one directory > in /usr/share/python-support for each package, and not a single > directory for the three packages. Josselin, thank you for the feedback. I've modified the package accordingly but I still have to use .install files to denote which files go to what package. Cheers, Serafeim ps. please do not cc me, I am subscribed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
