| ||||||||||||||||||||||
Jaunty python upgrade prevents pygtk apps from working
This morning python2.6 version 2.6.1-1ubuntu5 made it in to Jaunty after being held for a few days for the freeze. Unfortunately this package contained an ABI break that meant some python extensions no longer worked, most notably pygtk. In other words if you installed this version you would see some apps fail to start with a message "undefined symbol: PyUnicodeUCS4_DecodeUTF8". Most importantly update-manager was affected, making it harder to upgrade to a fixed version. https://bugs.launchpad.net/ubuntu/+source/python2.6/+bug/... Access to the bad packages was blocked, which is why you might have seen 403 errors if you attempted to upgrade this morning, and fixed packages have been uploaded as version 2.6.1-1ubuntu5.1. To find out if you have the bad version of the package installed you can run dpkg -l python2.6 | cat If the version is not 2.6.1-1ubuntu5 then you are unaffected, you should just be sure that you don't install that version if it is still accessible on your mirror. If you do have the bad version installed then you can upgrade using apt-get. sudo apt-get update sudo apt-get upgrade The fixed packages have only just been made available on the primary mirror, so you may need to wait a few hours before they can become available. Thanks, James -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-an... (Log in to post comments)
Jaunty python upgrade prevents pygtk apps from working Posted Mar 27, 2009 20:16 UTC (Fri) by khc (subscriber, #45209) [Link]
> dpkg -l python2.6 | cat
Huh?
Jaunty python upgrade prevents pygtk apps from working Posted Mar 27, 2009 22:57 UTC (Fri) by sbdep (subscriber, #13282) [Link]
hmm, that's actually a neat trick.
Usually dpkg -l will try to limit it's output based on the COLUMNS env variable. As a result, dpkg cuts off part of the package name, the version, and the description.
This ensures that dpkg does not look at the COLUMNS variable (since it is writing to a pipe instead) and this you get the full data from the dpkg -l command.
Jaunty python upgrade prevents pygtk apps from working Posted Mar 28, 2009 14:43 UTC (Sat) by james_w (subscriber, #51167) [Link]
As sbdep pointed out dpkg trims its output by default. mdz spotted that the way dpkg does that makes the two version numbers indistinguishable on an 80 column terminal, so I added the "| cat" to make sure that everybody saw the full version number.
Jaunty python upgrade prevents pygtk apps from working Posted Mar 29, 2009 0:48 UTC (Sun) by khc (subscriber, #45209) [Link]
ah, thanks!
Jaunty python upgrade prevents pygtk apps from working Posted Apr 8, 2009 11:25 UTC (Wed) by fjorba (subscriber, #6175) [Link]
Neat. The trick I knew so far was:
$ COLUMNS=132 dpkg -l python2.6
132 columns being a magic number that we, the elder, know as the width of a wide, continuous paper dot-matrix printer.
Told you so Posted Mar 29, 2009 19:17 UTC (Sun) by job (guest, #670) [Link]
... and that's why people thought it may not be such a good idea to have a package manager depending on the python runtime.
Told you so Posted Mar 30, 2009 13:39 UTC (Mon) by clugstj (subscriber, #4020) [Link]
It has to depend upon something, and that something could occasionally be broken. Actually, it is probably a bad idea to have the package manager depend upon a bleeding-edge version of anything.
|
||||||||||||||||||||||