[Bug 876519] Re: Not able to upgrade friom 11.04 to 10.10

Gabriel 876519 at bugs.launchpad.net
Fri Oct 21 13:50:18 UTC 2011


Ok, so I tried doing an "aptitude safe-upgrade", I figured out what went
wrong, our firewall didn't like linux-firmware_1.60_all.deb, because it
couldn't scan it, it just returned an error (504 if I remember
correctly). I had to download it manually from home and add it to
/var/cache/apt/archives/. All the other files were ok and the setup is
now installing the files.

I still think this situation should not occur, if there is a problem
downloading something it should give the user some feedback, not just
silently wait forever. If I had received an explicit msg (e.g. file &
link posing problem, error that occurred, etc) I'd have been able to fix
it quicker, aptitude can do it, so should your update manager
(commandline and GUI).

-- 
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/876519

Title:
  Not able to upgrade friom 11.04 to 10.10

Status in “update-manager” package in Ubuntu:
  New

Bug description:
  I started the upgrade manager (11.04 to 11.10) and had to stop during
  the "Getting new packages" part. I then later on re-started the
  process and libimobiledevice2 was upgradable, so I decided to upgrade
  it before finishing the system upgrade. Bad choice as now the system
  upgrade process stops doing anything at "Getting new packages"... I
  then tried downgrading libimobiledevice2 from 1.1.0-3ubuntu1 to
  1.1.0-3, but that doesn't help...

  While I agree that wasn't the best thing to do, I think in a system
  upgrade is stopped you should have a way of restarting it from scratch
  or continuing where it left off; currently it continues from what the
  UI says. I think it build an original list of packages to be upgraded
  and now it's stuck because of a mismatch.

  BTW, running "ubuntu-bug update-manager" stays stuck in the
  "Collecting problem information" step, and "ubuntu-bug" then choosing
  "other" closes with an error that a PID has to be given, even though
  there is no visible way of providing that.

  
  $ lsb_release -rd
  Description:	Ubuntu 11.04
  Release:	11.04

  $ apt-cache policy update-manager
  update-manager:
    Installed: 1:0.150.3
    Candidate: 1:0.150.3
    Version table:
   *** 1:0.150.3 0
          500 http://ch.archive.ubuntu.com/ubuntu/ natty-updates/main amd64 Packages
          100 /var/lib/dpkg/status
       1:0.150 0
          500 http://ch.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages

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




More information about the foundations-bugs mailing list