apt-get upgrade packages have been kept back

cccc · 04-09-2007, 05:06 PM

hi

I have sarge stable sarge installed:

Code:

# uname -a
Linux cc.mydomain.net 2.6.8-2-686 #1 Tue Aug 16 13:22:48 UTC 2005 i686 GNU/Linux

knows someone why some packages have been kept back and howto solve this problem ?

Code:

# apt-get update
Hit http://ftp.ch.debian.org sarge/main Packages
Hit http://ftp.ch.debian.org sarge/main Release
Hit http://ftp.ch.debian.org sarge/main Sources
Hit http://ftp.ch.debian.org sarge/main Release
Hit http://security.debian.org stable/updates/main Packages
Hit http://security.debian.org stable/updates/main Release
Reading Package Lists... Done
# apt-get upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages have been kept back:
  dia-common dia-gnome dia-libs file inkscape libkrb53 libmagic1
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.

carlosinfl · 04-09-2007, 05:11 PM

I have seen it do that before. Have you tried using the --force option?

cccc · 04-09-2007, 05:29 PM

Quote:

Originally Posted by Carlwill

I have seen it do that before. Have you tried using the --force option?

thanks, but how it shoud work ?

HappyTux · 04-09-2007, 05:54 PM

Quote:

Originally Posted by cccc

thanks, but how it shoud work ?

Just try apt-get install dia-common dia-gnome dia-libs file inkscape libkrb53 libmagic1 and the packages should install, if apt complains about a package(s) missing add it/them to the end of the line until it will install.

jdog006 · 04-10-2007, 11:10 AM

The easiest way to install packages which have been kept back is to do "apt-get dist-upgrade".

cccc · 04-11-2007, 03:22 AM

thanks a lot !

rickh · 04-11-2007, 08:11 AM

Something that might bite you soon ... You're pulling application updates from "Sarge" and security updates from "stable" ... Those two are no longer the same. Consider uprading to Etch, the new Stable, soon.

Read the Release Notes first.

jdog006 · 04-11-2007, 02:35 PM

One more tip. Besides using dist-upgrade, I'd recommend changing your sources list.

Instead of specifying a release name in your sources list (etch, sarge, etc), list the repository name (stable, testing, unstable). That way you won't really be affected by future releases. You will always pull updates from the debian branch that you want (stable, testing, unstable) regardless of what it might be named at the time.