[Bug 1070043] Re: DistUpgradeApport.py should check to see if --tags is available

Adam Conrad adconrad at 0c3.net
Tue Oct 23 20:03:44 UTC 2012


Hello Kees, or anyone else affected,

Accepted ubuntu-release-upgrader into precise-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:0.190.3 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from
verification-needed to verification-done.  If it does not, change the
tag to verification-failed.  In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

** Changed in: ubuntu-release-upgrader (Ubuntu Quantal)
       Status: In Progress => Fix Committed

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

Title:
  DistUpgradeApport.py should check to see if --tags is available

Status in “ubuntu-release-upgrader” package in Ubuntu:
  In Progress
Status in “ubuntu-release-upgrader” source package in Quantal:
  Fix Committed

Bug description:
  = Impact =
  If apport is not upgraded before a package installation failure happens the package installation failure mechanism will fail as it will try to use a feature of apport that isn't available.  This prevents us from receiving some package install failures that we should receive.

  = Test Case=
  On a precise sytem
  1) run do-release-upgrade -d in a terminal
  2) choose not to continue with the distribution upgrade when you see the Unity3D warning
  3) cd to /tmp/update-manager-SOMETHING (this is where the dist-upgrader for quantal was downloaded)
  4) download test.py from bug 1070043
  5) in the quantal dist-upgrader folder run "sudo python test.py"
  6) observe the error message 'package_hook: error: no such option: --tags'
  Now to use test the version from proposed:
  1) run do-release-upgrade -d -p in a terminal
  2) choose not to continue with the distribution upgrade when you see the Unity3D warning
  3) cd to /tmp/update-manager-SOMETHINGELSE (this is where the dist-upgrader for quantal from proposed was downloaded)
  4) copy test.py from /tmp/update-manager-SOMETHING to /tmp/update-manager-SOMETHINGELSE
  5) in the SOMETHINGELSE folder run "sudo python test.py"
  6) there should not be an error in the terminal
  7) confirm that there is a /var/crash/2vcard.0.crash file

  During a failed upgrade, I saw these errors, indicating that the
  apport package hook hadn't been upgraded before attempting to call
  some new features:

  dpkg: error processing libasyncns0 (--configure):
   no package named `libasyncns0' is installed, cannot configure
  Setting up libjson0:amd64 (0.10-1ubuntu1) ...
  Usage: package_hook [options]
  package_hook: error: no such option: --tags

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1070043/+subscriptions




More information about the foundations-bugs mailing list