I just tried upgrading from Ubuntu 10.04 to 12.04.1 (i.e. from LTS to LTS). It failed. The error message I'm getting is: An unresolvable problem occurred while calculating the upgrade: The package 'update-manager-kde' is marked for removal but it is in the removal blacklist. Google suggests that "apt-get remove update-manager-kde" should fix it [1], but that's giving me the following; Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libasound2: Breaks: libasound2-plugins (< 1.0.24) but 1.0.22-0ubuntu6 is to be installed libglib2.0-0: Breaks: gnome-control-center (< 1:3) but 1:2.30.1-0ubuntu2 is to be installed Breaks: gvfs (< 1.8) but 1.6.1-0ubuntu1build1 is to be installed libgnome-keyring0: Breaks: gnome-keyring (< 3.0) but 2.92.92.is.2.30.3-0ubuntu1.1 is to be installed libpango1.0-0: Breaks: plymouth (< 0.8.2-2ubuntu19) but 0.8.2-2ubuntu2.2 is to be installed ppp: Breaks: network-manager (<= 0.8.0.999-1) but 0.8-0ubuntu3.3 is to be installed Breaks: network-manager-pptp (<= 0.8.0.999-1) but 0.8-0ubuntu3 is to be installed E: Broken packages Have I completely hosed my setup, and is a fresh re-install due? Or is there a way around this? Thanks, Greg [1] http://www.hoaglun.com/blog/2011/5/8/ubuntu-1010-1104-upgrade.html
On Mon, 27 Aug 2012, Greg Thomas wrote:
I just tried upgrading from Ubuntu 10.04 to 12.04.1 (i.e. from LTS to LTS).
It failed. ..... Have I completely hosed my setup, and is a fresh re-install due? Or is there a way around this?
Thanks,
Greg
I'm no IT expert but i do recall a number of posts on the ubuntu list concerning failed upgrades from 10.04 to 12.04. You are attempting upgrade from 10.04 to 12.04.1 [revamped 12.04]. It should work... each time the recommendation that i've seen is do a fresh install from checked iso. I've always done that and not had any problems.... a pain copying to a CD each time but seems to pay off. I have also seen problems installing from USB... but that's not something i've attempted yet. I'd say do a fresh CD install every time. james
On Mon, Aug 27, 2012 at 06:18:49PM +0100, Greg Thomas wrote:
Google suggests that "apt-get remove update-manager-kde" should fix it
Try apt-get -f remove update-manager-kde (or apt-get -f install). You might want to try those with the -s option first to simulate what it will do, just in case it tries to break stuff even more. :) Adam
On 27 August 2012 20:29, Adam Bower <adam@thebowery.co.uk> wrote:
On Mon, Aug 27, 2012 at 06:18:49PM +0100, Greg Thomas wrote:
Google suggests that "apt-get remove update-manager-kde" should fix it
Try apt-get -f remove update-manager-kde (or apt-get -f install).
Neither of those worked :( On 27 August 2012 20:11, James Freer <jessejazza3.uk@gmail.com> wrote: ...
I'd say do a fresh CD install every time.
It looks like I'm going to have to bite the bullet. Drat. Thanks for listening! Greg
On Tue, Aug 28, 2012 at 08:46:30PM +0100, Greg Thomas wrote:
On 27 August 2012 20:29, Adam Bower <adam@thebowery.co.uk> wrote:
On Mon, Aug 27, 2012 at 06:18:49PM +0100, Greg Thomas wrote:
Google suggests that "apt-get remove update-manager-kde" should fix it
Try apt-get -f remove update-manager-kde (or apt-get -f install).
Neither of those worked :(
So what happened? If you report back we might be able to fix it!
On 27 August 2012 20:11, James Freer <jessejazza3.uk@gmail.com> wrote: ...
I'd say do a fresh CD install every time.
It looks like I'm going to have to bite the bullet. Drat.
That's never the way to do something like this! One of the nice things about using systems with reasonably sane package managers is because it lets you upgrade without doing things like a clean install. Adam
On 28 August 2012 21:42, Adam Bower <adam@thebowery.co.uk> wrote:
On Tue, Aug 28, 2012 at 08:46:30PM +0100, Greg Thomas wrote:
Neither of those worked :(
So what happened? If you report back we might be able to fix it!
"apt-get -f remove update-manager-kde" gave exactly the same as without the -f flag - i.e. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libasound2: Breaks: libasound2-plugins (< 1.0.24) but 1.0.22-0ubuntu6 is to be installed libglib2.0-0: Breaks: gnome-control-center (< 1:3) but 1:2.30.1-0ubuntu2 is to be installed Breaks: gvfs (< 1.8) but 1.6.1-0ubuntu1build1 is to be installed libgnome-keyring0: Breaks: gnome-keyring (< 3.0) but 2.92.92.is.2.30.3-0ubuntu1.1 is to be installed libpango1.0-0: Breaks: plymouth (< 0.8.2-2ubuntu19) but 0.8.2-2ubuntu2.2 is to be installed ppp: Breaks: network-manager (<= 0.8.0.999-1) but 0.8-0ubuntu3.3 is to be installed Breaks: network-manager-pptp (<= 0.8.0.999-1) but 0.8-0ubuntu3 is to be installed E: Broken packages "apt-get -f install" did nothing.
That's never the way to do something like this! One of the nice things about using systems with reasonably sane package managers is because it lets you upgrade without doing things like a clean install.
Never say never. I suspect it would be quicker to back up my data and re-install than spend hours poking at packages ... Greg
On 29 August 2012 09:18, Greg Thomas <greg.d.thomas@gmail.com> wrote:
On 28 August 2012 21:42, Adam Bower <adam@thebowery.co.uk> wrote:
On Tue, Aug 28, 2012 at 08:46:30PM +0100, Greg Thomas wrote:
Neither of those worked :(
So what happened? If you report back we might be able to fix it!
"apt-get -f remove update-manager-kde" gave exactly the same as without the -f flag - i.e.
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies. libasound2: Breaks: libasound2-plugins (< 1.0.24) but 1.0.22-0ubuntu6 is to be installed libglib2.0-0: Breaks: gnome-control-center (< 1:3) but 1:2.30.1-0ubuntu2 is to be installed Breaks: gvfs (< 1.8) but 1.6.1-0ubuntu1build1 is to be installed libgnome-keyring0: Breaks: gnome-keyring (< 3.0) but 2.92.92.is.2.30.3-0ubuntu1.1 is to be installed libpango1.0-0: Breaks: plymouth (< 0.8.2-2ubuntu19) but 0.8.2-2ubuntu2.2 is to be installed ppp: Breaks: network-manager (<= 0.8.0.999-1) but 0.8-0ubuntu3.3 is to be installed Breaks: network-manager-pptp (<= 0.8.0.999-1) but 0.8-0ubuntu3 is to be installed E: Broken packages
"apt-get -f install" did nothing.
That's never the way to do something like this! One of the nice things about using systems with reasonably sane package managers is because it lets you upgrade without doing things like a clean install.
Never say never. I suspect it would be quicker to back up my data and re-install than spend hours poking at packages ...
Would it be worth trying to upgrade those packages one at a time? apt-get upgrade network-manager-pptp apt-get upgrade ppp etc? (I don't know it will help, but if your data is backed up, it can't hurt to try.) Jenny
On 29 August 2012 09:23, Jenny Hopkins <hopkins.jenny@gmail.com> wrote:
Would it be worth trying to upgrade those packages one at a time? apt-get upgrade network-manager-pptp apt-get upgrade ppp etc?
Unfortunately that gives basically the same message; attempting to upgrade results in a complaint that the package in question is broken. Greg
On Wed, Aug 29, 2012 at 09:42:07AM +0100, Greg Thomas wrote:
Unfortunately that gives basically the same message; attempting to upgrade results in a complaint that the package in question is broken.
I've just done a search online for this problem, how did you attempt to do the upgrade? Did you use the Ubuntu upgrade manager tool or some other method? It seems that you may have bad package listings somewhere which is causing this problem. What is in the file /etc/apt/sources.list and are there any other software repositories in /etc/apt/sources.list.d/ ? Adam
On 29 August 2012 10:43, Adam Bower <adam@thebowery.co.uk> wrote:
I've just done a search online for this problem, how did you attempt to do the upgrade?
Using the Ubtunu upgrade manager.
What is in the file /etc/apt/sources.list
as below - looks normal to me. deb http://archive.ubuntu.com/ubuntu precise main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu precise-updates main restricted universe multiverse deb http://archive.ubuntu.com/ubuntu precise-security main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu precise-updates main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu precise universe multiverse main restricted deb-src http://archive.ubuntu.com/ubuntu precise-security main restricted universe multiverse # deb http://ppa.launchpad.net/amoog/ppa/ubuntu karmic main # disabled on upgrade to karmic # deb-src http://ppa.launchpad.net/amoog/ppa/ubuntu karmic main # disabled on upgrade to karmic
and are there any other software repositories in /etc/apt/sources.list.d/ ?
There are three files (medibuntu.list, medibuntu.list.distUpgrade and medibuntu.list.save) but the only repositories are commented out ("Ubuntu 9.10 "karmic koala" disabled on upgrade to lucid") - presumably when I went to 10.04 a couple of years back. Greg
On 28 August 2012 20:46, Greg Thomas <greg.d.thomas@gmail.com> wrote:
On 27 August 2012 20:11, James Freer <jessejazza3.uk@gmail.com> wrote: ...
I'd say do a fresh CD install every time.
It looks like I'm going to have to bite the bullet. Drat.
Thanks for listening!
I finally got a round tuit. A surprisingly slick process, it preserved my settings so I didn't need to check the validity of my backup! Greg
participants (4)
-
Adam Bower -
Greg Thomas -
James Freer -
Jenny Hopkins