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

Re: Growing number of packages not being upgraded



On 10/12/13 11:29 AM, Reco wrote:
On Tue, 10 Dec 2013 11:22:37 -0500
Frank McCormick <debianlist@videotron.ca> wrote:

On 10/12/13 11:10 AM, Reco wrote:

Well that solves most of the problem...but 2 are still
being held

root@frank-debian:/home/frank# apt-get dist-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:
    libtiffxx0c2
Use 'apt-get autoremove' to remove it.
The following packages will be REMOVED:
    foomatic-filters libharfbuzz0a
The following NEW packages will be installed:
    libamd2.3.1 libcamd2.3.1 libccolamd2.8.0 libcholmod2.1.2 libcolamd2.8.0
    libharfbuzz-gobject0 libharfbuzz0b libicu52 liblzma-dev libtiff5-dev
libtiffxx5
    libumfpack5.6.2
The following packages have been kept back:
    libmateweather-common libmatewnck-common
The following packages will be upgraded:
    cups-filters gir1.2-pango-1.0 libcdr-0.0-0 libdee-1.0-4 libgegl-0.2-0
libharfbuzz-dev
    libharfbuzz-icu0 libjavascriptcoregtk-1.0-0
libjavascriptcoregtk-3.0-0 libmspub-0.0-0
    libpango-1.0-0 libpango1.0-0 libpango1.0-dev libpangocairo-1.0-0
libpangoft2-1.0-0
    libpangoxft-1.0-0 libtiff4 libtiff4-dev libtiffxx0c2 libwebkitgtk-1.0-0
    libwebkitgtk-3.0-0
21 upgraded, 12 newly installed, 2 to remove and 2 not upgraded.
Need to get 29.1 MB of archives.
After this operation, 30.1 MB of additional disk space will be used.
Do you want to continue? [Y/n]

Anyway to find out what's holding them ?

Try it like this:

apt-get install libmateweather-common=1.6.2-1 libmatewnck-common=1.6.2-1

That should not upgrade these packages, but it should show why apt
refuses to do anything about them.


  apt-get says it can't find them.

  Trying to install the original packages:

root@frank-debian:/home/frank# apt-get install libmateweather-common libmatewnck-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required: apache2.2-bin caja caja-common dmz-cursor-theme engrampa engrampa-common eom eom-common ffmpegthumbnailer gir1.2-mate-panel gstreamer0.10-alsa gtk2-engines-murrine hddtemp indicator-messages indicator-messages-gtk2 indicator-status-provider-mc5 libdbusmenu-glib4
  libdbusmenu-gtk3-4 libdbusmenu-gtk4 libffmpegthumbnailer4 libindicate5
libindicator-messages-status-provider1 libindicator3-7 libindicator7 libmatebluetooth libmatekbd-common libmatekbd4 libmatepanelapplet libmatepolkit libmatesensorsappletplugin liboobs-1-5 libopts25 mate-applets-common mate-backgrounds mate-bluetooth mate-calc mate-control-center mate-desktop mate-desktop-common mate-media mate-media-common mate-media-gstreamer mate-menus mate-netspeed mate-panel-common mate-polkit mate-power-manager mate-power-manager-common mate-screensaver-common mate-sensors-applet mate-settings-daemon mate-settings-daemon-common mate-settings-daemon-gstreamer mate-system-tools mate-themes mate-user-share mate-utils mate-utils-common mozo murrine-themes ntp pluma pluma-common python-gst0.10 python-gtksourceview2 python-mate-menu system-tools-backends
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
libmateweather libmatewnck mate-applets mate-core mate-desktop-environment mate-desktop-environment-extra mate-indicator-applet mate-notification-daemon mate-panel
  mate-screensaver mate-session-manager mate-system-monitor
The following packages will be upgraded:
  libmateweather-common libmatewnck-common
2 upgraded, 0 newly installed, 12 to remove and 3 not upgraded.
Need to get 14.6 MB of archives.
After this operation, 13.9 MB disk space will be freed.
Do you want to continue? [Y/n] n


 Basically it wants to remove all of Mate :)

Another user..Jack Malmostoso says

MATE is slowly transitioning from the MATE repository to Debian.
Give it a few days and they will all be "upgraded". I think it's just
about version numbering, more than updates proper.


We'll see.

Thanks all




Reply to: