[Bug 1316032] Re: ubiquity fails to complete automated upgrade with python traceback in _restore_package_selection_in_cache

job jeppekdahl at hotmail.com
Wed Jan 6 20:21:53 UTC 2016


** Package changed: ubiquity (Ubuntu Trusty) => clean-ubiquity-ubuntu
(Ubuntu Trusty)

** Changed in: clean-ubiquity-ubuntu (Ubuntu Trusty)
     Assignee: (unassigned) => job (jeppekdahl)

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

Title:
  ubiquity fails to complete automated upgrade with python traceback in
  _restore_package_selection_in_cache

Status in apt-clone package in Ubuntu:
  New
Status in clean-ubiquity-ubuntu package in Ubuntu:
  New
Status in apt-clone source package in Trusty:
  New
Status in clean-ubiquity-ubuntu source package in Trusty:
  New

Bug description:
  While upgrading to 14.04, I got the following during the 'upgrade'
  phase of the installation :

  WARNING:root:can't add zenity (E:Unable to correct problems, you have held broken packages.)
  May  5 06:56:52 ubuntu ubiquity: WARNING:root:can't add zenity-common (E:Unable to correct problems, you have held broken packages.)
  May  5 06:56:52 ubuntu ubiquity: WARNING:root:can't add zip (E:Unable to correct problems, you have held broken packages.)
  May  5 06:56:52 ubuntu ubiquity: WARNING:root:can't add zlib1g (E:Unable to correct problems, you have held broken packages.)
  May  5 06:56:52 ubuntu ubiquity: WARNING:root:can't add zlib1g-dev (E:Unable to correct problems, you have held broken packages.)
  May  5 06:56:52 ubuntu ubiquity: WARNING:root:can't add zsync (E:Unable to correct problems, you have held broken packages.)
  May  5 06:56:52 ubuntu ubiquity: Traceback (most recent call last):
  May  5 06:56:52 ubuntu ubiquity:   File "/usr/bin/apt-clone", line 131, in <module>
  May  5 06:56:52 ubuntu ubiquity:     args.source, args.destination, args.new_distro_codename, protect_installed)
  May  5 06:56:52 ubuntu ubiquity:   File "/usr/lib/python3/dist-packages/apt_clone.py", line 473, in restore_state
  May  5 06:56:52 ubuntu ubiquity:     self._restore_package_selection(statefile, targetdir, protect_installed)
  May  5 06:56:52 ubuntu ubiquity:   File "/usr/lib/python3/dist-packages/apt_clone.py", line 607, in _restore_package_selection
  May  5 06:56:52 ubuntu ubiquity:     self._restore_package_selection_in_cache(statefile, cache, protect_installed)
  May  5 06:56:52 ubuntu ubiquity:   File "/usr/lib/python3/dist-packages/apt_clone.py", line 584, in _restore_package_selection_in_cache
  May  5 06:56:52 ubuntu ubiquity:     resolver.resolve()

  This was already reported in Bug #847475 but apparently never looked
  at.

  I don't know if the "Unable to correct problems, you have held broken
  packages" have something to do with the issue, but the traceback does
  bring failure to the 'apt-clone' phase.

  The system is installed and usable with one single user, but the rest
  of the environment has not been recovered

  Since the problem happened during installation, running ubuntu-bug is
  mostly useless.  I can have the logs in /var/log/installer available
  if needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/1316032/+subscriptions



More information about the foundations-bugs mailing list