Re: python3.3 status
On Friday, August 02, 2013 09:13:56 Scott Kitterman wrote: python3.3 is the default python3. We're going straight to dropping python3.2 from supported python3 versions. binNMUs were already done for morse- simulator,postgresql-9.1,yafaray,and znc after python3.3 became default. These issues from the switch to 3.3 as default are fixed: libguestfs - FTBFS i386, Fixed pytango - FTBFS on s390 - fixed Other changes done: pycxx - Will need sourceful update after python3.3 is default Here's the full binNMU list: libsigrokdecode mod-wsgi python-kyotocabinet python-leveldb python-pylibacl python-pyxattr libtorrent-rasterbar pygobject uwsgi yp-svipc pyepr pystemmer python-llfuse brltty pyepr pystemmer pandas pykde4 qscintilla2 mpi4py python- numpy sip4 apparmor cracklib2 cython deltarpm gearman-interface hivex libfiu libguestfs libkdtree++ lxml markupsafe newt psycopg2 py-postgresql py3cairo pyfits pyicu pyopenssl pysubnettree pytango python-apt python-bitarray python- bsddb3 python-cffi python-crypto python-drizzle python-libdiscid python-regex python-scipy pyyaml pyzmq urwid zope.interface morse-simulator dbus-python pycuda pyopencl In addtion, python3-stdlib-extensions and python-qt4 needed uploads anyway, so that was done in lieu of a binNMU. There were a couple of other packages that needed fixing (these are all uploaded): ibtorrent-rasterbar - binNMU failed, fix uploaded bpython - NMU uploaded uucp-lmtp - NMU based on patch in BTS uploaded python-dvdvideo - NMU based on patch in BTS uploaded Still waiting: blender - Sent patch to build with 3.3 to BTS and maintainer is working on it Once blender is uploaded, I think it's just a matter of waiting for things to migrate and we can remove python3.2. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4412659.9JX8IomEzt@scott-latitude-e6320
Re: python3.3 status
python3.3 is the default python3. We're going straight to dropping python3.2 from supported python3 versions. binNMUs were already done for morse- simulator,postgresql-9.1,yafaray,and znc after python3.3 became default. These issues still remain: libguestfs - No longer FTBFS on amd64, but does on i386, #710545, now builds for all python3 versions pytango - FTBFS on s390 - #711761, patch sent upstream, waiting for feedback. Once python3-defaults 3.3.2-4 is installed everywhere, we can proceed: morse-simulator - NMUed for #712014 - will need binNMU after python3.3 is default boost1.* - Will need binNMU file- No effect on the transition #709269 pycxx - Will need sourceful update after python3.3 is default Once I have an updated ben to look at, I'll have a full binNMU list for dropping python3.2 support. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1381234.iUqLIRTDSM@scott-latitude-e6320
Re: python3.3 status
On Saturday, July 06, 2013 10:22:22 PM Scott Kitterman wrote: On Wednesday, July 03, 2013 01:55:07 PM Scott Kitterman wrote: On Friday, June 21, 2013 01:30:00 AM Scott Kitterman wrote: On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote: Here's a further update on packages pertaining to the 3.3 transition: libguestfs - No longer FTBFS on amd64, but does on i386, #710545, now builds for all python3 versions nuitka FTBFS unrepoducible pytango - FTBFS on s390 - #711761, patch sent upstream, waiting for feedback. morse-simulator - NMUed for #712014 - will need binNMU after python3.3 is default boost1.53 - builds, but doesn't generate python related depends right (not related to the transition) file - No effect on the transition #709269 libsigrokdecode - #709406 marked pending since May 28, can ignore packagekit - Not affected by the transition postgresql-9.1 - Only depends on libpython3.2. Will need binNMU after 3.3 is default. I think this should have an interpreter dependency as well, but didn't file a bug as I'm not sure. I would appreciate it if someone would have a look. pycxx - Will need sourceful update after python3.3 is default pymongo - If it was packaged properly, it would need a binNMU, but it's not, so it's not an issue for the transition, #712112. sqlalchemy - Builds fine, no action needed for transition, ideally would build- dep on python3-all subunit - No action needed for transition, but multiple bugs need dealing with, #708077, #709540, and #712203 yafaray - FTBFS fixed. Only supports default python3, so it will need binNMU after python3.3 is default. shiboken - done znc - Will need binNMU after 3.3 is default. magics++ - No python3 content in the binaries, no effect on transition pygrib - Doesn't actually build python3 packages yet, no effect on transition. uwsgi - uwsgi-plugin-python3 only depends on libpython3.2 (and also 3.3 when rebuilt). Like postgresql-9.1, I think this should probably have a python3 dependency. It'd be nice if someone could have a look. python-astropy Builds fine, but doesn't actually put the python3 build in a binary, no impact on the transition Looking at where we are now, the open issues are down to #711761 and #710545. I don't think they are enough of a reason to hold back switching to python3.3 as default. My proposal is that once scipy reaches Testing, we switch to python3.3 as default python3 and then very shortly after, once all the rebuilds/uploads that can't be done until after 3.3 is the default are complete and python3- defaults with the default set to python3.3 is in Testing, we drop python3.2 from supported and start working on it's removal. If people are generally OK with that, I'll run it past the release team and unless they object, we'll do it. There's 10 days before we can do this in any case. No one objected, so I'll run this by the release team. No one objected here and the release team said go ahead, so I've just uploaded python3-defaults to unstable that makes python3.3 default. After the next dinstall, we should be able to start on the once 3.3 is default actions. Hopefully, this python3-defaults upload gets to testing in 10 days and then we can start working on getting rid of 3.2. Congratulations to everyone that helped out. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/14166419.iUaCqKE0vz@scott-latitude-e6320
Re: python3.3 status
On Friday, June 21, 2013 01:30:00 AM Scott Kitterman wrote: On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote: Here's a further update on packages pertaining to the 3.3 transition: libguestfs - No longer FTBFS on amd64, but does on i386, #710545, now builds for all python3 versions nuitka FTBFS unrepoducible pyepr builds successfully, but puts dbg extensions into wrong package: #708011 - bug marked as pending python-scipy - Updated version uploaded, no reason the latest upload shouldn't make it to testing. pytango - FTBFS on s390 - #711761 morse-simulator - NMUed for #712014 - will need binNMU after python3.3 is default pyopencl - Fixed. boost1.53 - builds, but doesn't generate python related depends right (not related to the transition) file - No effect on the transition #709269 liblouis - Shouldn't be part of the transition, build-dep is wrong #712076 - fixed, dropped off the tracker. libsigrokdecode - #709406 marked pending since May 28, can ignore packagekit - Not affected by the transition postgresql-9.1 - Only depends on libpython3.2. Will need binNMU after 3.3 is default. I think this should have an interpreter dependency as well, but didn't file a bug as I'm not sure. I would appreciate it if someone would have a look. pycxx - Will need sourceful update after python3.3 is default pymongo - If it was packaged properly, it would need a binNMU, but it's not, so it's not an issue for the transition, #712112. sqlalchemy - Builds fine, no action needed for transition, ideally would build- dep on python3-all subunit - No action needed for transition, but multiple bugs need dealing with, #708077, #709540, and #712203 yafaray - FTBFS fixed. Only supports default python3, so it will need binNMU after python3.3 is default. shiboken - done znc magics++ - No python3 content in the binaries, no effect on transition pygrib - Doesn't actually build python3 packages yet, no effect on transition. uwsgi - uwsgi-plugin-python3 only depends on libpython3.2 (and also 3.3 when rebuilt). Like postgresql-9.1, I think this should probably have a python3 dependency. It'd be nice if someone could have a look. python-astropy Builds fine, but doesn't actually put the python3 build in a binary, no impact on the transition Looking at where we are now, the open issues are down to #711761 and #711761. I don't think they are enough of a reason to hold back switching to python3.3 as default. My proposal is that once scipy reaches Testing, we switch to python3.3 as default python3 and then very shortly after, once all the rebuilds/uploads that can't be done until after 3.3 is the default are complete and python3- defaults with the default set to python3.3 is in Testing, we drop python3.2 from supported and start working on it's removal. If people are generally OK with that, I'll run it past the release team and unless they object, we'll do it. There's 10 days before we can do this in any case. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1955660.rWeJWdMMAG@scott-latitude-e6320
Re: python3.3 status
On Jul 03, 2013, at 01:55 PM, Scott Kitterman wrote: Looking at where we are now, the open issues are down to #711761 and #711761. Don't forget #711761 and #711761. :) I don't think they are enough of a reason to hold back switching to python3.3 as default. My proposal is that once scipy reaches Testing, we switch to python3.3 as default python3 and then very shortly after, once all the rebuilds/uploads that can't be done until after 3.3 is the default are complete and python3- defaults with the default set to python3.3 is in Testing, we drop python3.2 from supported and start working on it's removal. If people are generally OK with that, I'll run it past the release team and unless they object, we'll do it. There's 10 days before we can do this in any case. +1 Thanks for working on this transition. -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130703140408.78ec44ed@anarchist
Re: python3.3 status
On Wednesday, July 03, 2013 02:04:08 PM Barry Warsaw wrote: On Jul 03, 2013, at 01:55 PM, Scott Kitterman wrote: Looking at where we are now, the open issues are down to #711761 and #711761. Don't forget #711761 and #711761. :) Meh. #710545. Scott K I don't think they are enough of a reason to hold back switching to python3.3 as default. My proposal is that once scipy reaches Testing, we switch to python3.3 as default python3 and then very shortly after, once all the rebuilds/uploads that can't be done until after 3.3 is the default are complete and python3- defaults with the default set to python3.3 is in Testing, we drop python3.2 from supported and start working on it's removal. If people are generally OK with that, I'll run it past the release team and unless they object, we'll do it. There's 10 days before we can do this in any case. +1 Thanks for working on this transition. -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2721345.iNSnGMENbN@scott-latitude-e6320
RE : python3.3 status
Looking at where we are now, the open issues are down to #711761 and #711761. To my opinion, (I am the maintainer of pytango) this is not a problem if pytango is not available on s390. I forwarded the bug to the upstream with a patch, I am waiting for the approval of the upstream. Nevertheless I do not know when they will answer :(. cheers Fred -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/a2a20ec3b8560d408356cac2fc148e5358edc...@sun-dag1.synchrotron-soleil.fr
Re: python3.3 status
On Wednesday, July 03, 2013 06:15:11 PM PICCA Frédéric-Emmanuel wrote: Looking at where we are now, the open issues are down to #711761 and #711761. To my opinion, (I am the maintainer of pytango) this is not a problem if pytango is not available on s390. I forwarded the bug to the upstream with a patch, I am waiting for the approval of the upstream. Nevertheless I do not know when they will answer :(. Thanks for the update. Would you please add that information to #711761. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1992457.BTnMQsih0F@scott-latitude-e6320
Re: python3.3 status
On Wednesday, June 19, 2013 12:53:40 AM Scott Kitterman wrote: Here's a further update on packages pertaining to the 3.3 transition: libguestfs - No longer FTBFS on amd64, but does on i386, #710545, now builds for all python3 versions nuitka FTBFS unrepoducible pyepr builds successfully, but puts dbg extensions into wrong package: #708011 - bug marked as pending pyside Fixed, needs python3.3 as default to migrate to testing, nothing further to do for transition python-scipy FTBFS with new Cython/Numpy: #707315 Needs new, new cython which is ready in svn, needs new upstream release, needs python3-imaging pytango - FTBFS on s390 - #711761 morse-simulator - NMUed for #712014 - will need binNMU after python3.3 is default pyopencl package fixing FTBFS #711926 is in NEW now. boost1.53 - builds, but doesn't generate python related depends right (not related to the transition) file - No effect on the transition #709269 liblouis - Shouldn't be part of the transition, build-dep is wrong #712076 libsigrokdecode - #709406 marked pending since May 28, can ignore postgresql-9.1 - Only depends on libpython3.2. Will need NMU after 3.3 is default. I think this should have an interpreter dependency as well, but didn't file a bug as I'm not sure. I would appreciate it if someone would have a look. pycxx - Will need sourceful update after python3.3 is default pymongo - If it was packaged properly, it would need a binNMU, but it's not, so it's not an issue for the transition, #712112. sqlalchemy - Builds fine, no action needed for transition, ideally would build- dep on python3-all subunit - No action needed for transition, but multiple bugs need dealing with, #708077, #709540, and #712203 yafaray - FTBFS fixed. Only supports default python3, so it will need binNMU after python3.3 is default. shiboken - built on mipsel finally, all done znc magics++ - No python3 content in the binaries, no effect on transition pygrib - Doesn't actually build python3 packages yet, no effect on transition. uwsgi - uwsgi-plugin-python3 only depends on libpython3.2 (and also 3.3 when rebuilt). Like postgresql-9.1, I think this should probably have a python3 dependency. It'd be nice if someone could have a look. python-astropy Builds fine, but doesn't actually put the python3 build in a binary, no impact on the transition I've marked the things that I think block python3.3 as default a blocking the transition bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708536 Is there anything there that shouldn't be a blocker? I think scipy is the biggest issue and that apparently needs cython updated first. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5083101.rh4oTHWSE3@scott-latitude-e6320
Re: python3.3 status
Here's a further update on packages pertaining to the 3.3 transition: boost1.49 Fixed flufl.bounce builds now that zope.interface is updated hivex FTBFS fixed, dependencies fixed, nothing further to do. libguestfs - No longer FTBFS on amd64, but does on i386, #710545, now builds for all python3 versions nuitka FTBFS unrepoducible pyepr builds successfully, but puts dbg extensions into wrong package: #708011 pyside Fixed, needs python3.3 as default to migrate to testing, needs shiboken fixed on mipsel. python-astropy Builds fine, but doesn't actually put the python3 build in a binary, no impact on the transition python-cffi - Built against 3.2/3.3 - nothing further to do. python-csb - Builds now, nothing further to do. python-scipy FTBFS with new Cython/Numpy: #707315 Needs new, new cython which is ready in svn python-stem Builds now, but has other issues unrelated to transition python-wadllib - Builds now pytango - Shouldn't have been removed from the list, FTBFS on s390 - #711761 yapsy - builds now, nothing further to do. zope.interface - Uploaded zope.exceptions - Uploaded zope.component - Uploaded morse-simulator - Builds, but depends are FUBAR: #712014 All of the red in http://release.debian.org/transitions/html/python3.3.html is due to open bugs. The binNMUs that could be done after python-numpy was uploaded are done except those blocked by bugs. It would still be worth doing some investigation of the unknown packages to see if they are generating dependencies correctly. Here's the other unknown packages: boost1.53 - builds, but doesn't generate python related depends right file - No effect on the transition #709269 liblouis - Shouldn't be part of the transition, build-dep is wrong #712076 libsigrokdecode - #709406 marked pending since May 28, can ignore postgresql-9.1 - Only depends on libpython3.2. Will need NMU after 3.3 is default. I think this should have an interpreter dependency as well, but didn't file a bug as I'm not sure. I would appreciate it if someone would have a look. pycxx - Will need sourceful update after python3.3 is default pymongo - If it was packaged properly, it would need a binNMU, but it's not, so it's not an issue for the transition, #712112. sqlalchemy - Builds fine, no action needed for transition, ideally would build- dep on python3-all subunit - No action needed for transition, but multiple bugs need dealing with, #708077, #709540, and #712203 yafaray - FTBFS fixed. Only supports default python3, so it will need binNMU after python3.3 is default. shiboken - back on the list after FTBFS on mipsel - blocking pyside build znc magics++ - No python3 content in the binaries, no effect on transition pygrib - Doesn't actually build python3 packages yet, no effect on transition. uwsgi - uwsgi-plugin-python3 only depends on libpython3.2 (and also 3.3 when rebuilt). Like postgresql-9.1, I think this should probably have a python3 dependency. It'd be nice if someone could have a look. I've marked the things that I think block python3.3 as default a blocking the transition bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708536 Is there anything there that shouldn't be a blocker? I think scipy is the biggest issue and that apparently needs cython updated first. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1431099.aGNH6O39L1@scott-latitude-e6320
Re: python3.3 status
Dnia 2013-06-19, śro o godzinie 00:53 -0400, Scott Kitterman pisze: [ cut ] I've marked the things that I think block python3.3 as default a blocking the transition bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708536 pyopencl package fixing FTBFS #711926 (which block #708536) is in NEW now. -- Tomasz Rybak GPG/PGP key ID: 2AD5 9860 Fingerprint A481 824E 7DD3 9C0E C40A 488E C654 FB33 2AD5 9860 http://member.acm.org/~tomaszrybak signature.asc Description: This is a digitally signed message part
Re: python3.3 status
Hi, Gediminas Paulauskas mene...@pov.lt writes: Please also upload zope.component 3.11.0 at the same time, to match a big move of code to zope.interface = 3.8 Thanks, I have just uploaded these 4 packages. Cheers, -- Arnaud Fontaine -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/874ncxmey2@duckcorp.org
Re: python3.3 status
On Wednesday, June 12, 2013 03:13:38 PM Scott Kitterman wrote: On Wednesday, June 12, 2013 12:48:45 AM Scott Kitterman wrote: On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote: More updates and added all the unknown packages from the transition tracker. Items marked as fixed in the last update have been removed. On Thursday, May 23, 2013 06:19:06 PM Scott Kitterman wrote: I've been working on this a bit ... On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote: python3-defaults maintainer(s?) decided to make python3.3 a supported version without prior notice. Yay. Now we have dozens of packages failing to build: boost1.49 FTBFS TODO (could not find an open bug) - I plan to ignore this this and wait until the boost1.53 transition starts and we can not care. flufl.bounce FTBFS #707086, needs new zope.interface hivex FTBFS fixed, but still doesn't generate dependencies right #709516 libguestfs - No longer FTBFS, only builds for default python3, will need binNMU after python3.3 is default nuitka FTBFS unrepoducible pyepr builds successfully, but puts dbg extensions into wrong package: #708011 pyopencl FTBFS, #711926, maintainer is active on this pyside Fixed by Odyx python-astropy Builds fine, but doesn't actually put the python3 build in a binary, no impact on the transition python-cffi FTBFS TODO python-csb FTBFS TODO python-distutils-extra Builds fine now, no issues python-scipy FTBFS with new Cython/Numpy: #707315 Needs new, new cython which is ready in svn python-stem FTBFS TODO python-wadllib FTBFS #686332 pytango - Shouldn't have been removed, FTBFS on s390 - #711761 yapsy FTBFS TODO zope.interface - Needs update to 4.0.2 or later, needs updated zope.exceptions zope.exceptions needs updated to 4.0.1 zope.component update to 3.11.0 due to code shifted between interface and component. morse-simulator - Builds, but depends are FUBAR: #712014 Many of the FTBFS packages above could probably stand to be rebuilt again to see if they build now (most of the ones I've tried do). Getting zope.interface/exceptions updated would be helpful as well, but seems to need sponsoring. Arnaud Fontaine is looking into this. All of the red in http://release.debian.org/transitions/html/python3.3.html is due to open bugs (except pyside, I didn't get to look at that yet). The binNMUs that could be done after python-numpy was uploaded are done except those blocked by bugs. It would still be worth doing some investigation of the unknown packages to see if they are generating dependencies correctly. Here's the other unknown packages: boost1.53 - builds, but doesn't generate python related depends right file - No effect on the transition #709269 liblouis - Shouldn't be part of the transition, build-dep is wrong #712076 libsigrokdecode - #709406 marked pending since May 28, can ignore postgresql-9.1 - Only depends on libpython3.2. Will need NMU after 3.3 is default. I think this should have an interpreter dependency as well, but didn't file a bug as I'm not sure. I would appreciate it if someone would have a look. pycxx - Will need sourceful update after python3.3 is default pymongo - If it was packaged properly, it would need a binNMU, but it's not, so it's not an issue for the transition, #712112. sqlalchemy subunit yafaray znc magics++ - No python3 content in the binaries, no effect on transition pygrib - Doesn't actually build python3 packages yet, no effect on transition. uwsgi - uwsgi-plugin-python3 only depends on libpython3.2 (and also 3.3 when rebuilt). Like postgresql-9.1, I think this should probably have a python3 dpeendency. It'd be nice if someone could have a look. The list is getting smaller ... Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4341482.9XzRDt7SLD@scott-latitude-e6320
Re: python3.3 status
On 13 June 2013 07:01, Scott Kitterman deb...@kitterman.com wrote: On Wednesday, June 12, 2013 03:13:38 PM Scott Kitterman wrote: On Wednesday, June 12, 2013 12:48:45 AM Scott Kitterman wrote: On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote: More updates and added all the unknown packages from the transition tracker. Items marked as fixed in the last update have been removed. On Thursday, May 23, 2013 06:19:06 PM Scott Kitterman wrote: I've been working on this a bit ... On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote: python3-defaults maintainer(s?) decided to make python3.3 a supported version without prior notice. Yay. Now we have dozens of packages failing to build: boost1.49 FTBFS TODO (could not find an open bug) - I plan to ignore this this and wait until the boost1.53 transition starts and we can not care. boost1.49 fixed in the 1.49.0-4 upload. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANBHLUi0rvVWs60=D_Pya-NxYczsh2AV=jm1x=1yexcub2-...@mail.gmail.com
Re: python3.3 status
2013/6/11 Arnaud Fontaine ar...@debian.org Hello, Arnaud Fontaine ar...@debian.org writes: I can sponsor zope.interface upload if that's ok for Gediminas. I have prepared zope.interface for upload and noticed that tests fail with python 3.3 because of a bug in zope.exceptions fixed in 4.0.1 (only 4.0.0.1 is currently available in Debian). This is probably not required to fix for the upload but I thought it would be a good thing to fix it. So, I imported the changes in zope.exceptions from Ubuntu and bumped required versionof python3-zope.exceptions inDepends for python3-zope.testrunner. Gediminas: I think these changes are fine but could you please confirm that these 3 packages can be uploaded as available in the SVN? Thank you very much! Yes. I have joined the changelog entries of zope.exception into one for unstable. Please also upload zope.component 3.11.0 at the same time, to match a big move of code to zope.interface = 3.8 Thanks -- Gediminas
Re: python3.3 status
On Wednesday, June 12, 2013 12:48:45 AM Scott Kitterman wrote: On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote: More updates and added all the unknown packages from the transition tracker. Items marked as fixed in the last update have been removed. On Thursday, May 23, 2013 06:19:06 PM Scott Kitterman wrote: I've been working on this a bit ... On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote: python3-defaults maintainer(s?) decided to make python3.3 a supported version without prior notice. Yay. Now we have dozens of packages failing to build: boost1.49 FTBFS TODO (could not find an open bug) cairosvg Builds now - flufl.bounce FTBFS #707086, needs new zope.interface hivex FTBFS fixed, but still doesn't generate dependencies right #709516 libguestfs - No longer FTBFS, only builds for default python3, will need binNMU after python3.3 is default nuitka FTBFS unrepoducible pyepr builds successfully, but puts dbg extensions into wrong package: #708011 pyopencl FTBFS, #711926 pyside FTBFS TODO python-astropy Builds fine, but doesn't actually put the python3 build in a binary, no impact on the transition python-cffi FTBFS TODO python-csb FTBFS TODO python-distutils-extra FTBFS needs rebuilt pygobject python-scipy FTBFS with new Cython/Numpy: #707315 Needs new, new cython which is ready in svn python-stem FTBFS TODO python-wadllib FTBFS #686332 shiboken Fixed. yapsy FTBFS TODO zope.interface - Needs update to 4.0.2 or later, needs updated zope.exceptions zope.exceptions needs updated to 4.0.1 zope.component update to 3.11.0 due to code shifted between interface and component. morse-simulator - Builds, but depends are FUBAR: #712014 Many of the FTBFS packages above could probably stand to be rebuilt again to see if they build now (most of the ones I've tried do). Getting zope.interface/exceptions updated would be helpful as well, but seems to need sponsoring. Arnaud Fontaine is looking into this. All of the red in http://release.debian.org/transitions/html/python3.3.html is due to open bugs (except pyside, I didn't get to look at that yet). The binNMUs that could be done after python-numpy was uploaded are done except those blocked by bugs. It would still be worth doing some investigation of the unknown packages to see if they are generating dependencies correctly. Here's the other unknown packages: boost1.53 - builds, but doesn't generate python related depends right file- No effect on the transition #709269 liblouis - Shouldn't be part of the transition, build-dep is wrong #712076 libsigrokdecode postgresql-9.1 pycxx - Will need sourceful update after python3.3 is default pymongo sqlalchemy subunit yafaray znc magics++ - No python3 content in the binaries, no effect on transition pygrib - Doesn't actually build python3 packages yet, no effect on transition. uwsgi The list is getting smaller ... Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4634522.ParOI93oKa@scott-latitude-e6320
Re: python3.3 status
Hello, Arnaud Fontaine ar...@debian.org writes: I can sponsor zope.interface upload if that's ok for Gediminas. I have prepared zope.interface for upload and noticed that tests fail with python 3.3 because of a bug in zope.exceptions fixed in 4.0.1 (only 4.0.0.1 is currently available in Debian). This is probably not required to fix for the upload but I thought it would be a good thing to fix it. So, I imported the changes in zope.exceptions from Ubuntu and bumped required versionof python3-zope.exceptions inDepends for python3-zope.testrunner. Gediminas: I think these changes are fine but could you please confirm that these 3 packages can be uploaded as available in the SVN? Thank you very much! Cheers, -- Arnaud Fontaine pgpCv9UF7Nx7b.pgp Description: PGP signature
Re: python3.3 status
On Thursday, June 06, 2013 12:46:05 PM Scott Kitterman wrote: Here's another update based on work I've done, noticed other people did, or responses to the last one of these I sent. It does not include work which I neither notice nor people told me about. Items marked as fixed in the last update have been removed. On Thursday, May 23, 2013 06:19:06 PM Scott Kitterman wrote: I've been working on this a bit ... On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote: python3-defaults maintainer(s?) decided to make python3.3 a supported version without prior notice. Yay. Now we have dozens of packages failing to build: boost1.49 FTBFS TODO (could not find an open bug) boost1.50 Resolved - package has been removed. cairosvg FTBFS, needs fixed py3cairo distribute Fixed. flufl.bounce FTBFS #707086, needs new zope.interface germinate Fine now hivex FTBFS fixed, but still doesn't generate dependencies right #709516 libguestfs FTBFS TODO mdp Fine now. mpi4py OK nuitka FTBFS unrepoducible objgraph Fixed now pyepr builds successfully, but puts dbg extensions into wrong package: #708011 pyfits binNMUed successfully pyopencl FTBFS, #711926 pyside FTBFS TODO pystemmer OK python-apt Fixed python-astropy Builds fine, but doesn't actually put the python3 build in a binary. python-cffi FTBFS TODO python-csb FTBFS TODO python-distutils-extra FTBFS needs rebuilt pygobject python-llfuse OK python-numpy Fixed in unstable python-scipy FTBFS with new Cython/Numpy: #707315 Needs new, new cython which is ready in svn python-stem FTBFS TODO python-wadllib FTBFS #686332 shiboken FTBFS TODO yapsy FTBFS TODO yp-svipc fixed - binNMUed zope.interface - Needs update to 4.0.2 or later, needs updated zope.exceptions zope.exceptions needs updated to 4.0.1 morse-simulator - Builds, but depends are FUBAR: #712014 Many of the FTBFS packages above could probably stand to be rebuilt again to see if they build now (most of the ones I've tried do). Getting zope.interface/exceptions updated would be helpful as well, but seems to need sponsoring. Arnaud Fontaine is looking into this. All of the red in http://release.debian.org/transitions/html/python3.3.html is due to open bugs (except pyside, I didn't get to look at that yet). The binNMUs that could be done after python-numpy was uploaded are done except those blocked by bugs. It would still be worth doing some investigation of the unknown packages to see if they are generating dependencies correctly. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2366362.9uueqvkskS@scott-latitude-e6320
Re: python3.3 status
On Jun 07, 2013, at 05:27 PM, Arnaud Fontaine wrote: zope.interface - Needs update to 4.0.2 or later Getting zope.interface updated would be helpful as well, but seems to need sponsoring. If someone has some sponsoring cycles available, please have a look. I can sponsor zope.interface upload if that's ok for Gediminas. \o/ -Barry signature.asc Description: PGP signature
Re: python3.3 status
On Thursday, May 23, 2013 06:19:06 PM Scott Kitterman wrote: I've been working on this a bit ... On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote: python3-defaults maintainer(s?) decided to make python3.3 a supported version without prior notice. Yay. Now we have dozens of packages failing to build: boost1.49 FTBFS TODO boost1.50 FTBFS TODO cairosvg FTBFS, needs fixed py3cairo cssutils - Fixed distribute FTBFS TODO flufl.bounce FTBFS #707086, needs new zope.interface germinate FTBFS, needs fixed python-apt hivex FTBFS fixed, but still doesn't generate dependencies right #709516 libguestfs FTBFS TODO mdp FTBFS, needs fixed python-numpy mod-wsgi, Now fixed mpi4py needs fixed cython nuitka FTBFS TODO objgraph FTBFS #686331 pyepr needs fixed cython pyfits FTBFS, needs fixed python-numpy pymarkups - Fixed pyopencl FTBFS, needs fixed boost1.49 pyside FTBFS TODO pystemmer needs fixed cython pytest - Fixed python-apt FTBFS #681744 python-astropy needs fixed cython python-cffi FTBFS TODO python-csb FTBFS TODO python-distutils-extra FTBFS needs rebuilt pygobject python-docutils - Fixed python-flexmock - Fixed python-llfuse needs fixed cython python-notify2 - Fixed python-numpy Fixed in experimental + SVN python-scipy needs fixed cython, then likely FTBFS #691254 python-stem FTBFS TODO python-wadllib FTBFS #686332 shiboken FTBFS TODO yapsy FTBFS TODO yp-svipc FTBFS, needs fixed python-numpy zope.interface - Needs update to 4.0.2 or later FTBFS TODO means that a package fails to build, but there's no bug filed yet. I plan to file bugs today or tomorrow, unless there are other volunteers to do it. I've updated this list by removing ones that were reported fixed in the last mail I sent and then updating again based on responses to it. mpi4py, pyepr, pystemmer, python-llfuse, python-scipy, and python-astropy all needed a fixed cython, which is now available. It would be nice if someone would check those. Getting zope.interface updated would be helpful as well, but seems to need sponsoring. If someone has some sponsoring cycles available, please have a look. Most of the red in http://release.debian.org/transitions/html/python3.3.html can be binNMUed after python-numpy is uploaded (promised this weekend, AIUI). It would be worth doing some investigation of the unknown packages to see if they are generating dependencies correctly. Any other progress? Did anyone file bugs for jwilk's FTBFS TODO packages? Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3082334.MxQK4dTUX1@scott-latitude-e6320
Re: python3.3 status
* Scott Kitterman deb...@kitterman.com, 2013-06-06, 12:46: mpi4py, pyepr, pystemmer, python-llfuse, python-scipy, and python-astropy all needed a fixed cython, which is now available. pyepr builds successfully, but puts dbg extensions into wrong package: #708011 python-scipy FTBFS with new Cython: #707315 python-astropy needs fixed Numpy mpi4py, pystemmer, python-llfuse are OK -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130606170405.gb6...@jwilk.net
Re: python3.3 status
* Scott Kitterman deb...@kitterman.com, 2013-06-06, 12:46: Did anyone file bugs for jwilk's FTBFS TODO packages? I've file them all, with one exception: I couldn't reproduce nuitka's FTBFS in a different build environment. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130606204443.ga8...@jwilk.net
Re: python3.3 status
On Fri, May 24, 2013 at 2:19 AM, Scott Kitterman deb...@kitterman.com wrote: Did anyone else fix stuff? cssutils FTBFS, needs rebuilt nosetests, then FTBFS #686340 Fixed. python-docutils FTBFS #681723 Excellently fixed by Jakub. pymarkups FTBFS TODO No longer FTBFS with the latest docutils. python-flexmock FTBFS, needs rebuilt nosetests Fixed. Also committed a fix for python-pip (#692384) and submitted a fix for dep-8 tests for pandas. -- Dmitry Shachnev -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKimPHWLK+dYRkUGqnQqE_8irG=_8gfvjnghukjfh7dyxkv...@mail.gmail.com
Re: python3.3 status
Quoting Scott Kitterman (2013-05-24 00:19:06) On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote: [...] pytest FTBFS TODO Fixed signature.asc Description: signature
Re: python3.3 status
On May 07, 2013, at 02:01 PM, Jakub Wilk wrote: flufl.bounce FTBFS #707086 This one is really because of the ancient version of zope.interface in sid/jessie. It's not until z.i 4.0.2 that Python 3.3 support was added, although 4.0.5 is the latest version in the Cheeseshop. CC pkg-zope-developers to get their feedback. FWIW, we have 4.0.5 in Ubuntu, so I'd be willing to help merge the Ubuntu changes back into Debian if the Zope team wants. zope.interface | 3.5.3-1 | squeeze | source zope.interface | 3.6.1-3 | wheezy | source zope.interface | 3.6.1-3 | jessie | source zope.interface | 3.6.1-3 | sid | source -Barry signature.asc Description: PGP signature
Re: python3.3 status
On Fri, May 24, 2013 at 11:24:20AM -0400, Barry Warsaw wrote: On May 07, 2013, at 02:01 PM, Jakub Wilk wrote: flufl.bounce FTBFS #707086 This one is really because of the ancient version of zope.interface in sid/jessie. It's not until z.i 4.0.2 that Python 3.3 support was added, although 4.0.5 is the latest version in the Cheeseshop. CC pkg-zope-developers to get their feedback. FWIW, we have 4.0.5 in Ubuntu, so I'd be willing to help merge the Ubuntu changes back into Debian if the Zope team wants. Please do. We recently discussed what to do now that Wheezy is out: http://lists.alioth.debian.org/pipermail/pkg-zope-developers/2013-May/008547.html The gist is that we got to a consensus on: * Merge changes from Ubuntu * add python3 support where possible * try stick to versions in http://docs.zope.org/zopetoolkit/releases/packages-2.0a1.html where possible Any help with that agenda would be appreciated :) -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130524154805.GA69767@Brians-MacBook-Air.local
Re: python3.3 status
On May 24, 2013, at 05:48 PM, Brian Sutherland wrote: On Fri, May 24, 2013 at 11:24:20AM -0400, Barry Warsaw wrote: On May 07, 2013, at 02:01 PM, Jakub Wilk wrote: flufl.bounce FTBFS #707086 This one is really because of the ancient version of zope.interface in sid/jessie. It's not until z.i 4.0.2 that Python 3.3 support was added, although 4.0.5 is the latest version in the Cheeseshop. CC pkg-zope-developers to get their feedback. FWIW, we have 4.0.5 in Ubuntu, so I'd be willing to help merge the Ubuntu changes back into Debian if the Zope team wants. Please do. We recently discussed what to do now that Wheezy is out: http://lists.alioth.debian.org/pipermail/pkg-zope-developers/2013-May/008547.html The gist is that we got to a consensus on: * Merge changes from Ubuntu * add python3 support where possible * try stick to versions in http://docs.zope.org/zopetoolkit/releases/packages-2.0a1.html where possible Any help with that agenda would be appreciated :) Looks like, at least for zope.interface, Gediminas is way ahead of me: http://lists.alioth.debian.org/pipermail/pkg-zope-developers/2013-May/008563.html Alioth's svn looks ready to go for 4.0.5-1. I only added a get-orig-source target to repack the .zip, but that's mostly unimportant for this particular issue. The last message in that thread was 15-May, so it seems like maybe zope.interface, if not more of zope.* is just waiting for uploads (something that I can't *quite* help with yet ;). -Barry -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130524182947.18309019@anarchist
Re: python3.3 status
Į will sync the rest of zope packages from ubuntu in a few days. Anyone able to upload? What is the latest snippet to add for python3 support?.. 2013.05.25 01:36, Barry Warsaw ba...@python.org rašė: On May 24, 2013, at 05:48 PM, Brian Sutherland wrote: On Fri, May 24, 2013 at 11:24:20AM -0400, Barry Warsaw wrote: On May 07, 2013, at 02:01 PM, Jakub Wilk wrote: flufl.bounce FTBFS #707086 This one is really because of the ancient version of zope.interface in sid/jessie. It's not until z.i 4.0.2 that Python 3.3 support was added, although 4.0.5 is the latest version in the Cheeseshop. CC pkg-zope-developers to get their feedback. FWIW, we have 4.0.5 in Ubuntu, so I'd be willing to help merge the Ubuntu changes back into Debian if the Zope team wants. Please do. We recently discussed what to do now that Wheezy is out: http://lists.alioth.debian.org/pipermail/pkg-zope-developers/2013-May/008547.html The gist is that we got to a consensus on: * Merge changes from Ubuntu * add python3 support where possible * try stick to versions in http://docs.zope.org/zopetoolkit/releases/packages-2.0a1.html where possible Any help with that agenda would be appreciated :) Looks like, at least for zope.interface, Gediminas is way ahead of me: http://lists.alioth.debian.org/pipermail/pkg-zope-developers/2013-May/008563.html Alioth's svn looks ready to go for 4.0.5-1. I only added a get-orig-source target to repack the .zip, but that's mostly unimportant for this particular issue. The last message in that thread was 15-May, so it seems like maybe zope.interface, if not more of zope.* is just waiting for uploads (something that I can't *quite* help with yet ;). -Barry
Re: python3.3 status
I've been working on this a bit ... On Tuesday, May 07, 2013 02:01:26 PM Jakub Wilk wrote: python3-defaults maintainer(s?) decided to make python3.3 a supported version without prior notice. Yay. Now we have dozens of packages failing to build: boost1.49 FTBFS TODO boost1.50 FTBFS TODO cairosvg FTBFS, needs fixed py3cairo cracklib2 - Fixed cssutils FTBFS, needs rebuilt nosetests, then FTBFS #686340 cython Fixed dbus-python Fixed distribute FTBFS TODO flufl.bounce FTBFS #707086 germinate FTBFS, needs fixed python-apt hivex FTBFS fixed, but still doesn't generate dependencies right #709516 libguestfs FTBFS TODO mdp FTBFS, needs fixed python-numpy mod-wsgi, Fixed in experimental mpi4py needs fixed cython nuitka FTBFS TODO objgraph FTBFS #686331 py3cairo Fixed pyepr needs fixed cython pyfits FTBFS, needs fixed python-numpy pykde4 Fixed pymarkups FTBFS TODO pyopencl FTBFS, needs fixed boost1.49 pyside FTBFS TODO pystemmer needs fixed cython pytest FTBFS TODO python-apt FTBFS #681744 python-astropy needs fixed cython python-cffi FTBFS TODO python-csb FTBFS TODO python-distutils-extra FTBFS needs rebuilt pygobject python-docutils FTBFS #681723 python-flexmock FTBFS, needs rebuilt nosetests python-llfuse needs fixed cython python-notify2 FTBFS, needs fixed dbus-python python-numpy Fixed in experimental + SVN python-qt4 Fixed python-scipy needs fixed cython, then likely FTBFS #691254 python-stem FTBFS TODO python-wadllib FTBFS #686332 pyyaml Fixed pyzmq Fixed shiboken FTBFS TODO urwid Fixed yafaray Fixed yapsy FTBFS TODO yp-svipc FTBFS, needs fixed python-numpy FTBFS TODO means that a package fails to build, but there's no bug filed yet. I plan to file bugs today or tomorrow, unless there are other volunteers to do it. Fixed includes binNMUs where needed. Did anyone else fix stuff? Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2590786.sCKX4LoaYO@scott-latitude-e6320
python3.3 status
python3-defaults maintainer(s?) decided to make python3.3 a supported version without prior notice. Yay. Now we have dozens of packages failing to build: boost1.49 FTBFS TODO boost1.50 FTBFS TODO cairosvg FTBFS, needs fixed py3cairo cracklib2 FTBFS #681749 cssutils FTBFS, needs rebuilt nosetests, then FTBFS #686340 cython produces broken code #681697 dbus-python FTBFS due to a bug in python3.3 #707084 distribute FTBFS TODO flufl.bounce FTBFS #707086 germinate FTBFS, needs fixed python-apt hivex FTBFS #692387 libguestfs FTBFS TODO mdp FTBFS, needs fixed python-numpy mod-wsgi, FTBFS #692390 mpi4py needs fixed cython nuitka FTBFS TODO objgraph FTBFS #686331 py3cairo FTBFS TODO pyepr needs fixed cython pyfits FTBFS, needs fixed python-numpy pykde4 FTBFS TODO pymarkups FTBFS TODO pyopencl FTBFS, needs fixed boost1.49 pyside FTBFS TODO pystemmer needs fixed cython pytest FTBFS TODO python-apt FTBFS #681744 python-astropy needs fixed cython python-cffi FTBFS TODO python-csb FTBFS TODO python-distutils-extra FTBFS needs rebuilt pygobject python-docutils FTBFS #681723 python-flexmock FTBFS, needs rebuilt nosetests python-llfuse needs fixed cython python-notify2 FTBFS, needs fixed dbus-python python-numpy FTBFS TODO python-qt4 FTBFS TODO python-scipy needs fixed cython, then likely FTBFS #691254 python-stem FTBFS TODO python-wadllib FTBFS #686332 pyyaml needs fixed cython pyzmq needs fixed cython shiboken FTBFS TODO urwid FTBFS #692383 yafaray FTBFS #692381 yapsy FTBFS TODO yp-svipc FTBFS, needs fixed python-numpy FTBFS TODO means that a package fails to build, but there's no bug filed yet. I plan to file bugs today or tomorrow, unless there are other volunteers to do it. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130507120126.ga6...@jwilk.net
Re: python3.3 status
Thanks Jakub, FWIW: cython produces broken code #681697 update WiP (for some reason did not build using python-dbg at all thus dh_install failed... will troubleshoot shortly) nuitka FTBFS TODO I believe fixed upstream -- if not -- will be, i.e. nothing to worry for the team -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130507124212.ge9...@onerussian.com
Re: python3.3 status
* Jakub Wilk jw...@debian.org, 2013-05-07, 14:01: Now we have dozens of packages failing to build: I should have said that I initially tested only packages build-depending on python3-all(-dev). There are also these, that build-depended only on the default version: pyinotify #692385 python-pip #692384 (and presumably more...) boost1.49 FTBFS TODO boost1.50 FTBFS TODO Cloned #691378 into #707114 and #707114 dbus-python FTBFS due to a bug in python3.3 #707084 Filed #707139. distribute FTBFS TODO #707140 (not related to Python 3.3) libguestfs FTBFS TODO 707141 nuitka FTBFS TODO No bug yet; doesn't look related to Python 3.3. py3cairo FTBFS TODO #707145 pykde4 FTBFS TODO #707148 pymarkups FTBFS TODO This one needs fixed docutils. pyside FTBFS TODO #707150 pytest FTBFS TODO #707151 python-cffi FTBFS TODO #707164 python-csb FTBFS TODO No bug yet; doesn't look related to Python 3.3. python-numpy FTBFS TODO #707156 python-qt4 FTBFS TODO #707157 python-stem FTBFS TODO #707160 shiboken FTBFS TODO #707161 yapsy FTBFS TODO #707162 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130507204947.ga5...@jwilk.net
