mythbuntu-bugs team mailing list archive

[Launchpad Bug Tracker <1013171@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package network-manager -
0.9.6.0~git201207161259.00297f4-0ubuntu1

---------------
network-manager (0.9.6.0~git201207161259.00297f4-0ubuntu1) quantal; urgency=low

  * upstream snapshot 2012-07-16 12:59:59 (GMT)
    + 00297f49fbbe05c51c02da43cda254c35e053589

  [ Edward Donovan ]
  * debian/source_network-manager.py: port package hook to python3.
    (LP: #1013171)

  [ Mathieu Trudel-Lapierre ]
  * debian/patches/lp292054_tune_supplicant_timeout_60s.patch: disable the
    patch. It adds unnecessary delays to things like detecting that hidden
    networks are not in range, and since Jaunty drivers have changed a lot.
    If we're still seeing timing issues with the supplicant, then perhaps the
    drivers should be fixed instead, or we'll re-enable the patch. (LP: #446623)
  * debian/network-manager.dnsmasq, debian/rules:
    install a config file to /etc/dnsmasq.d to avoid system-wide instances of
    dnsmasq to bind to 0.0.0.0 and the loopback interface, so that the NM-
    spawned instance can claim an IP on lo and provide local resolution.
    (LP: #959037)
  * debian/patches/add-veth-support.diff: add support for the veth* virtual
    ethernet devices. Thanks to Stéphane Graber for the patch.
  * debian/patches/nm-ip6-rs.patch: dropped, applied upstream.
  * debian/libnm-util2.symbols: add symbols:
    + nm_utils_file_is_pkcs12@Base
  * debian/control: move policykit-1 from Recommends to Depends: without it
    calls to the backend (e.g. when starting nm-tool), will fail. Thanks to
    Stéphane Graber for the testing and solution.
  * debian/rules: fix clean to properly remove m4/intltool.m4.
  * debian/tests/control, debian/tests/nm: add an autopkgtest control file and
    initial test to verify that NM works once installed.
  * debian/control: add XS-Testsuite: autopkgtest.
 -- Mathieu Trudel-Lapierre <mathieu-tl@xxxxxxxxxx>   Mon, 16 Jul 2012 17:17:51 -0400

** Changed in: network-manager (Ubuntu Quantal)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythtv in Ubuntu.
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 Committed
Status in “mythtv” package in Ubuntu:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Fix Committed
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 Committed
Status in “mythtv” source package in Quantal:
  Fix Released
Status in “nautilus” source package in Quantal:
  Fix Committed
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.donovan@xxxxxxxxxx>

  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