[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: apt-get doesn't upgrade, but synaptic does

On Thu, 10 Apr 2014, Frank McCormick wrote:

> Had a strange problem this morning for the second time recently:
> root@frank-debian:/home/frank# apt-get upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> The following package was automatically installed and is no longer
> required: python-gtksourceview2
> Use 'apt-get autoremove' to remove it.
> The following packages have been kept back:
>    eom-common mate-panel mate-panel-common
> The following packages will be upgraded:
>    base-passwd cups cups-bsd cups-client cups-common
> cups-core-drivers cups-daemon
>    cups-ppdc cups-server-common dnsmasq-base geoip-database libcups2 
> libcupscgi1
>    libcupsimage2 libcupsmime1 libcupsppdc1 man-db pluma pluma-common
> ruby 20 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
> Need to get 7,645 kB of archives.
> After this operation, 4,731 kB disk space will be freed.
> Do you want to continue? [Y/n]
> Apt-get then did what it said it would upgrading everything except
> mate-panel, mate-panel-commong and eom

This is the proper behavior for "upgrade."  To "upgrade" the
held-back files use "dist-upgrade" instead. The apt-get man explains
the difference between the two, and why it is done that way.


Reply to: