PDA

View Full Version : Apt-get upgrade "kept back" question


OBnascar
July 17th, 2006, 10:12 AM
obnascar@ubuntu:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
The following packages have been kept back:
gnome-cups-manager python-netcdf
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded

Can someone please tell me why these packages would be held back ?

reacocard
July 17th, 2006, 10:34 AM
thay depend on another package that isn't being installed. use sudo apt-get dist-upgrade instead, it automatically installs nessecary dependencies.

OBnascar
July 17th, 2006, 11:15 AM
obnascar@ubuntu:~$ sudo apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Calculating upgrade... Done
The following packages have been kept back:
gnome-cups-manager python-netcdf
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

dist-upgrade tells me the same thing

SigmaX
July 24th, 2006, 09:17 PM
I have the same issue -- except mine's with a fresh Breezy-to-Dapper telling me 73 packages have been kept back.

Any ideas?

SigmaX

dolby
July 25th, 2006, 08:04 PM
u need to update the package which apt-get tells u is being kept back. use update manager or synaptic instead

OBnascar
July 25th, 2006, 09:22 PM
u need to update the package which apt-get tells u is being kept back. use update manager or synaptic instead

You are correct dolby, I used synaptic to update those two packages and now I do not get a "kept back" message.

thanks,
Obnascar

SigmaX
July 27th, 2006, 04:47 PM
Well in my case the inconsistancy prevented X from installing -- so synaptic wasn't an option (And why would synaptic solve what apt-get and aptitude did not?). I just reinstalled.

For those who wish to avoid my situation in the future, I think it had something to do with installing automatix before the upgrade. Don't remember exactly what I did, but the only thing I'd touched between Breezy install and Dapper upgrade was Automatix.

SigmaX

napzilla
June 19th, 2008, 02:14 AM
This problem typically crops up every time I do an Ubuntu version upgrade. Sometimes, dist-upgrade works. In other cases, I've found that telling apt to remove the offending packages and then telling apt to install them again convinces it to find the required dependencies and resolves the problem.