This bug was fixed in the package mysql-5.5 - 5.5.25a-0ubuntu1

---------------
mysql-5.5 (5.5.25a-0ubuntu1) quantal; urgency=low

  [ Clint Byrum ]
  * New upstream release.
  * d/additions/my.cnf: Ensure mysql errors are written to log file.
    (LP: #1014732)
  * d/mysql-server-5.5.mysql-server.logrotate: Add
    /var/log/mysql/error.log so it is rotated properly. (LP: #879560)
  * d/control: remove Vcs-* as they are inaccurate in Ubuntu.
  * d/rules: use WITH_SSL=bundled to ensure that we do not accidentally
    build against openssl.
  * d/control, d/rules: cherry pick fix from Debian to use gcc 4.4 only
    for i386 to work around problems with yaSSL assembly (LP: #1012139)

  [ Matthieu Baerts (matttbe) ]
  * Update apport hook for python3 ; patch by Edward Donovan (LP: #1013171)
 -- Clint Byrum <cl...@ubuntu.com>   Thu, 19 Jul 2012 16:14:50 -0700

** Changed in: mysql-5.5 (Ubuntu Quantal)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1013171

Title:
  Many package hooks not ported to python3

Status in “apache2” package in Ubuntu:
  Fix Released
Status in “apport” package in Ubuntu:
  Fix Released
Status in “apport-symptoms” package in Ubuntu:
  Fix Released
Status in “bluez” package in Ubuntu:
  Fix Released
Status in “cairo-dock” package in Ubuntu:
  Fix Released
Status in “chromium-browser” package in Ubuntu:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Committed
Status in “connman” package in Ubuntu:
  Fix Released
Status in “dkms” package in Ubuntu:
  Fix Released
Status in “gnome-control-center” package in Ubuntu:
  Fix Committed
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-applet” package in Ubuntu:
  Fix Released
Status in “libatasmart” package in Ubuntu:
  Fix Released
Status in “lxpanel” package in Ubuntu:
  Fix Released
Status in “mdadm” package in Ubuntu:
  Fix Released
Status in “mysql-5.5” package in Ubuntu:
  Fix Released
Status in “mythtv” package in Ubuntu:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “shadow” package in Ubuntu:
  Fix Released
Status in “udisks2” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “xdiagnose” package in Ubuntu:
  Fix Released
Status in “apache2” source package in Quantal:
  Fix Released
Status in “apport” source package in Quantal:
  Fix Released
Status in “apport-symptoms” source package in Quantal:
  Fix Released
Status in “bluez” source package in Quantal:
  Fix Released
Status in “cairo-dock” source package in Quantal:
  Fix Released
Status in “chromium-browser” source package in Quantal:
  Fix Released
Status in “compiz” source package in Quantal:
  Fix Committed
Status in “connman” source package in Quantal:
  Fix Released
Status in “dkms” source package in Quantal:
  Fix Released
Status in “gnome-control-center” source package in Quantal:
  Fix Committed
Status in “gnome-settings-daemon” source package in Quantal:
  Fix Committed
Status in “indicator-applet” source package in Quantal:
  Fix Released
Status in “libatasmart” source package in Quantal:
  Fix Released
Status in “lxpanel” source package in Quantal:
  Fix Released
Status in “mdadm” source package in Quantal:
  Fix Released
Status in “mysql-5.5” source package in Quantal:
  Fix Released
Status in “mythtv” source package in Quantal:
  Fix Released
Status in “nautilus” source package in Quantal:
  Fix Released
Status in “network-manager” source package in Quantal:
  Fix Released
Status in “shadow” source package in Quantal:
  Fix Released
Status in “udisks2” source package in Quantal:
  Fix Released
Status in “unity” source package in Quantal:
  Fix Released
Status in “xdiagnose” source package in Quantal:
  Fix Released

Bug description:
  Since the description here is the only post that can be updated, it
  seems the best place to keep a changing list of packages that need
  examining.  (The original description was brief, and about only one
  package.)

  We've fixed all the packages that found in the apt logs uploaded in
  the first round of breakage.  Now I've tried to review all the other
  apport hooks I could find in Quantal.  Working from the archive's
  Contents file, I got the list of packages that have files under
  /usr/share/apport/package-hooks .  I skipped the packages already
  fixed above, and those that were on my system, during the first round
  of breakage, and had no problems.  For the rest, I downloaded the
  debs, extracted the apport hooks, and ran '2to3' on them.  I've posted
  patches for every package that broke under python3.

  Thanks - Edward Donovan <edward.dono...@numble.net>

  These packages didn't break during the apport upgrade that forced a
  recompile, but they get warnings from the 2to3 tool:

    compiz-core
    eclipse-platform
    gnome-control-center-data
    gnome-settings-daemon
    grub-common
    nautilus-data
    unity-common
    apache2.2-common

  Now we have a bug report for at least gnome-control-center, bug
  1018537, which I've duped here.  So these may need patching, too.

  Hm...from a preliminary look, a number of those use the same code:

      if report.has_key("Stacktrace")

  which generates an exception with python3.  We're probably going to
  want to change those to

     if "Stacktrace" in report

  and I'll try to post some of those simple patches, soon.

  Side note:

    rss-glx: the python is fine, but the hook file is just named
  'source', with no package name or extension, so I filed bug 1017780
  about that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1013171/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to