[opensuse] zypper refuses to update some software
![](https://seccdn.libravatar.org/avatar/708e4fea71341205414825c27ee7e84e.jpg?s=120&d=mm&r=g)
I switched from zypper dup to sypper up a few months ago, and lately I've been getting a long list of packages that won't be updated. Some of them have been in this message for weeks (I update a couple of times a week), and look pretty important to me. THe update I just did, for instance: The following package updates will NOT be installed: NetworkManager-kde4-libs NetworkManager-kde4-libs-lang NetworkManager-openvpn-kde4 NetworkManager-pptp-kde4 NetworkManager-vpnc-kde4 amarok bluedevil choqok cln clucene-core-devel digikam digikam-lang ffmpeg gstreamer-0_10 gstreamer-0_10-plugin-gnomevfs gstreamer-0_10-plugin-hal gstreamer-0_10-plugins-base gstreamer-0_10-plugins-good gstreamer-0_10-plugins-good-lang k3b k3b-codecs kaffeine kde4-printer-applet kdeadmin4 kdeartwork4-desktopthemes kdeartwork4-emoticons kdeartwork4-icons kdeartwork4-sounds kdeartwork4-wallpapers kdebase4-runtime-xine kdebase4-wallpapers kdetoys4 kdeutils4 kdewebdev4 kipi-plugins kipi-plugins-acquireimage ksshaskpass ktorrent ktorrent-lang libavcodec52 libavdevice52 libavfilter1 libavformat52 libavutil50 libblas3 libbluedevil1 libgstapp-0_10-0 libgstinterfaces-0_10-0 libgstreamer-0_10-0 libindi0 libktorrent3 libktorrent3-lang liblapack3 liblash1 libpostproc51 libshout3 libswscale0 libtag-extras1 libva1 libvpx0 libwavpack1 libxine1 libxine1-gnome-vfs libxine1-pulse libxvidcore4 linphone mjpegtools mobile-broadband-provider-info oxygen-gtk python-numpy qt4-qtscript-doc qtcurve-kde4 shared-desktop-ontologies shared-desktop-ontologies-devel skanlite smb4k smb4k-lang sox taglib The following packages are going to be upgraded: libzypp python-satsolver satsolver-tools zypper The repositories: embelex:~ # zypper up Retrieving repository 'openSUSE BuildService - KDE:Extra' metadata [done] Building repository 'openSUSE BuildService - KDE:Extra' cache [done] Retrieving repository 'openSUSE BuildService - KDE:UpdatedApps' metadata [done] Building repository 'openSUSE BuildService - KDE:UpdatedApps' cache [done] Retrieving repository 'Main Repository (Contrib)' metadata [done] Building repository 'Main Repository (Contrib)' cache [done] Retrieving repository 'Packman Repository' metadata [done] Building repository 'Packman Repository' cache [done] Retrieving repository 'openSUSE-11.4-Update' metadata [done] Building repository 'openSUSE-11.4-Update' cache [done] Retrieving repository 'science' metadata [done] Building repository 'science' cache [done] Loading repository data... Reading installed packages... Am I missing something? Is my database corrupt? Is everything ok? There is a long list of kde modules, for instance, that has been in the "no update" list forever. Seems to me kde should be moving along, but I can't remember a kde update at all recently -- that's prompted this message. Do I need to fix something? What? john perry -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/cabdbf4d350ab6a15265803acab1634d.jpg?s=120&d=mm&r=g)
j.e.perry@cox.net said the following on 08/04/2011 09:46 PM:
Do I need to fix something? What?
No. You said
zypper dup to sypper up
(Supper? Slipper?) What you are seeing is the difference between "dup" and "up" The man page says update (up) [options] [packagename] ... Update installed packages with newer versions, where possible. This command will not update packages which would require change of package vendor unless the vendoris specified in /etc/zypp/vendors.d, or which would require manual resolution of problems with dependencies. Such non-installable updates will then be listed in separate section of the summary as "The following package updates will NOT be installed:". and dist-upgrade (dup) [options] Perform a distribution upgrade. This command applies the state of (specified) repositories onto the system; upgrades (or even downgrades) installed packages to versions found in repositories, removes packages that are no longer in the repositories and pose a dependency problem for the upgrade, handles package splits and renames, etc. One letter different but a vast difference in result -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/7946a5581e1e0b25e548f2b41c69d273.jpg?s=120&d=mm&r=g)
On Thu, 2011-08-04 at 22:36 -0400, Anton Aylward wrote:
j.e.perry@cox.net said the following on 08/04/2011 09:46 PM:
Do I need to fix something? What?
No.
You said
zypper dup to sypper up
(Supper? Slipper?)
What you are seeing is the difference between "dup" and "up"
The man page says
update (up) [options] [packagename] ... Update installed packages with newer versions, where possible.
This command will not update packages which would require change of package vendor unless the vendoris specified in /etc/zypp/vendors.d, or which would require manual resolution of problems with dependencies. Such non-installable updates will then be listed in separate section of the summary as "The following package updates will NOT be installed:".
and
dist-upgrade (dup) [options] Perform a distribution upgrade. This command applies the state of (specified) repositories onto the system; upgrades (or even downgrades) installed packages to versions found in repositories, removes packages that are no longer in the repositories and pose a dependency problem for the upgrade, handles package splits and renames, etc.
Indeed. I have a laptop that I have been using 'up' on. I get similar things not being installed (especially NetworkManager, gstreamer stuff, and the python numpy stuff). If I do a 'dup' it wants to revert many things to older versions to be able to install these things 'up' won't install. I suspect there is some issue with versions of packages in some combinations of repos. In fact, it wants to revert so many things that I have not done the 'dup'. Mine is on 11.4. I don't have any real problems, so I have let these packages be as 'up' leaves them. I would imagine one should use care when using 'dup'. Depending on the repos you have enabled, I could imagine some unexpected results. Having said that, I have never had a problem when I have used it. Yours sincerely, Roger Oberholtzer OPQ Systems / Ramböll RST Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/eeaa070dd6317ec84ae2eb35d4eaf01f.jpg?s=120&d=mm&r=g)
On 08/05/2011 02:28 AM, Roger Oberholtzer pecked at the keyboard and wrote:
On Thu, 2011-08-04 at 22:36 -0400, Anton Aylward wrote:
j.e.perry@cox.net said the following on 08/04/2011 09:46 PM:
Do I need to fix something? What?
No.
You said
zypper dup to sypper up
(Supper? Slipper?)
What you are seeing is the difference between "dup" and "up"
The man page says
update (up) [options] [packagename] ... Update installed packages with newer versions, where possible.
This command will not update packages which would require change of package vendor unless the vendoris specified in /etc/zypp/vendors.d, or which would require manual resolution of problems with dependencies. Such non-installable updates will then be listed in separate section of the summary as "The following package updates will NOT be installed:".
and
dist-upgrade (dup) [options] Perform a distribution upgrade. This command applies the state of (specified) repositories onto the system; upgrades (or even downgrades) installed packages to versions found in repositories, removes packages that are no longer in the repositories and pose a dependency problem for the upgrade, handles package splits and renames, etc.
Indeed. I have a laptop that I have been using 'up' on. I get similar things not being installed (especially NetworkManager, gstreamer stuff, and the python numpy stuff). If I do a 'dup' it wants to revert many things to older versions to be able to install these things 'up' won't install. I suspect there is some issue with versions of packages in some combinations of repos. In fact, it wants to revert so many things that I have not done the 'dup'.
This is where priorities come into play. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
![](https://seccdn.libravatar.org/avatar/bff0c215e01f23fcee6fe49e65fae458.jpg?s=120&d=mm&r=g)
On Thu, Aug 04, 2011 at 09:46:32PM -0400, j.e.perry@cox.net wrote:
I switched from zypper dup to sypper up a few months ago, and lately I've been getting a long list of packages that won't be updated. Some of them have been in this message for weeks (I update a couple of times a week), and look pretty important to me. THe update I just did, for instance:
The following package updates will NOT be installed: NetworkManager-kde4-libs NetworkManager-kde4-libs-lang NetworkManager-openvpn-kde4 NetworkManager-pptp-kde4 NetworkManager-vpnc-kde4 amarok bluedevil choqok cln clucene-core-devel digikam digikam-lang ffmpeg gstreamer-0_10 gstreamer-0_10-plugin-gnomevfs gstreamer-0_10-plugin-hal gstreamer-0_10-plugins-base gstreamer-0_10-plugins-good gstreamer-0_10-plugins-good-lang k3b k3b-codecs kaffeine kde4-printer-applet kdeadmin4 kdeartwork4-desktopthemes kdeartwork4-emoticons kdeartwork4-icons kdeartwork4-sounds kdeartwork4-wallpapers kdebase4-runtime-xine kdebase4-wallpapers kdetoys4 kdeutils4 kdewebdev4 kipi-plugins kipi-plugins-acquireimage ksshaskpass ktorrent ktorrent-lang libavcodec52 libavdevice52 libavfilter1 libavformat52 libavutil50 libblas3 libbluedevil1 libgstapp-0_10-0 libgstinterfaces-0_10-0 libgstreamer-0_10-0 libindi0 libktorrent3 libktorrent3-lang liblapack3 liblash1 libpostproc51 libshout3 libswscale0 libtag-extras1 libva1 libvpx0 libwavpack1 libxine1 libxine1-gnome-vfs libxine1-pulse libxvidcore4 linphone mjpegtools mobile-broadband-provider-info oxygen-gtk python-numpy qt4-qtscript-doc qtcurve-kde4 shared-desktop-ontologies shared-desktop-ontologies-devel skanlite smb4k smb4k-lang sox taglib
The following packages are going to be upgraded: libzypp python-satsolver satsolver-tools zypper
The repositories:
embelex:~ # zypper up Retrieving repository 'openSUSE BuildService - KDE:Extra' metadata [done] Building repository 'openSUSE BuildService - KDE:Extra' cache [done] Retrieving repository 'openSUSE BuildService - KDE:UpdatedApps' metadata [done] Building repository 'openSUSE BuildService - KDE:UpdatedApps' cache [done] Retrieving repository 'Main Repository (Contrib)' metadata [done] Building repository 'Main Repository (Contrib)' cache [done] Retrieving repository 'Packman Repository' metadata [done] Building repository 'Packman Repository' cache [done] Retrieving repository 'openSUSE-11.4-Update' metadata [done] Building repository 'openSUSE-11.4-Update' cache [done] Retrieving repository 'science' metadata [done] Building repository 'science' cache [done] Loading repository data... Reading installed packages...
Am I missing something? Is my database corrupt? Is everything ok? There is a long list of kde modules, for instance, that has been in the "no update" list forever. Seems to me kde should be moving along, but I can't remember a kde update at all recently -- that's prompted this message.
Do I need to fix something? What?
It looks like it wants to install the update stack patch first. After you have done it, the rest will also be installable. zypper patch // first run will install update stack update (new zypper/libzypp) zypper patch // second run will install the rest updates Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Anton Aylward
-
j.e.perry@cox.net
-
Ken Schneider - openSUSE
-
Marcus Meissner
-
Roger Oberholtzer