On Wed, Jul 23, 2014 at 03:33:03PM +0200, Matthias Klose wrote: > Asking what will happen with packages depending on wxPython 2.8 and > which cannot be converted to 3.0.
There aren't many incompatible changes between wxPython 2.8 and 3.0. With the C++ API, the Unicode changes have been quite painful, but that's simply not relevant to wxPython. My hope is that we will get all packages converted, though I know from the wxwidgets2.8 transition that there are a few rdeps which are dead upstream and effectively unmaintained in Debian. If such a package isn't actually working currently and nobody has reported it, removal might be the best option. I've had a go at updating 20 of the rdeps of python-wxgtk2.8, so I've now got some concrete information. I've done all the orphaned ones (since it seemed unlikely anyone else would), the two which also depend libwxgtk2.8-dev, and a selection of others biased towards those with the highest popcon scores. Several packages work without any changes (including p9m4, the last upload of which was an NMU by me in 2011 for the wxwidgets2.8 transition!) For most of the others the updates needed are mechanical (e.g. wx.Color is no longer supported as an alias for wx.Colour). I've produced a script which automates most of these (link below). The 5 orphaned packages I just QA uploaded, and of the other 15, 5 have either been uploaded by the maintainer or NMUed by me. Of the other 10, 8 are ready to upload (so 18 are uploaded or ready to upload). The other two are: grass: grass 7.0.0 is close to release, but would require a transition for dependencies. For grass 6.4.3 I have a patch which makes the wizard work, but the main gui needs more work. playonlinux: The maintainer reports problems with layout. I've not yet tried it myself (the description warns "PlayOnLinux downloads and execute unchecked third-party scripts"), so I'm not sure what the cause is. Extrapolating to the ~80 rdeps, that suggests something like 8 that won't be trivial to update, is a realistic number to have to address before the freeze. Here are the user tagged bugs: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=wxpy3.0;users=freewx-ma...@lists.alioth.debian.org And the transition tracker: https://release.debian.org/transitions/html/wxpython3.0.html And finally, the repo with the script in, and a README about using it and updating packages for wxPython 3.0 in general: http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git I'd like to encourage maintainers of affected packages to try this script out. In many cases, it should be enough to get your packages working (if they don't already) - if it does, please upload them. If the script doesn't do the job, let me know (or improve the script if you can figure out what it needs to do to get your package working). Cheers, Olly -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140818105818.gp14...@survex.com
