[Dx-packages] [Bug 1013171] Re: Many package hooks not ported to python3
** Changed in: unity
Status: New => Fix Released
** Changed in: unity
Assignee: (unassigned) => Matthieu Baerts (matttbe)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
https://bugs.launchpad.net/bugs/1013171
Title:
Many package hooks not ported to python3
Status in Unity:
Fix Released
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 Released
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 Released
Status in “gnome-settings-daemon” package in Ubuntu:
Fix Released
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 Released
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 Released
Status in “gnome-settings-daemon” source package in Quantal:
Fix Released
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
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 noti
[Dx-packages] [Bug 1013171] Re: Many package hooks not ported to python3
This report was already getting too big for Launchpad to handle quickly,
and is all marked fixed. In these cases I'm usually advised to leave
the closed report as it is, and handle the new occurrence with the new
bug. You can certainly put a link to this bug, there, for informational
purposes. Maybe I can get to that.
Thanks!
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-applet in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
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 Released
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 Released
Status in “gnome-settings-daemon” package in Ubuntu:
Fix Released
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 Released
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 Released
Status in “gnome-settings-daemon” source package in Quantal:
Fix Released
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
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.
[Dx-packages] [Bug 1013171] Re: Many package hooks not ported to python3
Hi,
I see reoccurence of this bug in gnome-control-center 3.6.3 (3.6.3-0ubuntu49).
Also, there is a separate bug reported for that -
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1237119
Should we mark the other one a duplicate for this one or is there another way
we want to cope with it?
Thanks,
Tobiasz
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-applet in Ubuntu.
Matching subscriptions: dx-packages, dx-packages
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 Released
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 Released
Status in “gnome-settings-daemon” package in Ubuntu:
Fix Released
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 Released
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 Released
Status in “gnome-settings-daemon” source package in Quantal:
Fix Released
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
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.
S
