[Bug 973747] Re: apport hook gzips apt-clone_system_state two times

[Launchpad Bug Tracker]

This bug was fixed in the package update-manager - 1:0.152.25.9

---------------
update-manager (1:0.152.25.9) oneiric-proposed; urgency=low

  * In the apport package hook continue if unable to import gconf data
    (LP: #880704)
  * In the apport package hook do not gzip the apt-clone attachment two times
    (LP: #973747)
  * check-new-release-gtk:
    - ensure to write a integer when calculating the next time that
      the release available window will be presented (LP: #873424)
    - hide redundant release-notes button (LP: #873432)
  * check-new-release-gtk:
    - write the time to check the new release to the update-notifier schema
      not the update-manager one (LP: #873424)
 -- Brian Murray <brian at ubuntu.com>   Wed, 04 Apr 2012 13:04:28 -0700

** Changed in: update-manager (Ubuntu Oneiric)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/973747

Title:
  apport hook gzips apt-clone_system_state two times

Status in “update-manager” package in Ubuntu:
  Fix Released
Status in “update-manager” source package in Oneiric:
  Fix Released

Bug description:
  The apport hook for update-manager in oneiric gzips the attachment
  apt-clone_system_state two times so when you are working with those
  attachments you end up having to do the following:

  gunzip VarLogDistupgradeAptclonesystemstatetargz.gz.
  mv VarLogDistupgradeAptclonesystemstatetargz VarLogDistupgradeAptclonesystemstate.tar.gz
  tar xfvz VarLogDistupgradeAptclonesystemstate.tar.gz

  and that depends on you knowing that the log file is gzipped two
  times.

  Test Case:
  1) execute 'APPORT_LAUNCHPAD_INSTANCE=staging.launchpad.net ubuntu-bug update-manager'
  2) say yes to the distribution upgrade question
  3) report the bug in launchpad
  4) download the apt-clone attachment
  5) gunzip it
  6) using file determine that it is still a gzip file

  7) install the proposed version of update-manager
  8) repeat steps 1-5
  9) observe that file says the file is a tar file now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/973747/+subscriptions