[opensuse] zypper inconsistent?
Can anyone explain to me why the openSUSE-updater and zypper command line would give different results? Or should I raise this as a bug? openSUSE-updater (after running a Check Now): Available Updates: Upgrades: DirectFB - Graphics Library for Framebuffer Devices - New Version 1.1.1-32.1 - Restart No kde4-gtk-qt-engine - GTK-Style Engine for Use with Qt Plug-Ins and Settings - New Version 1.1svn20080614-3.1 - Restart No yet zypper on the command line gives: (run both before and after the Check Now from the updater icon) alpha:~ # zypper refresh; zypper update Repository 'openSUSE BuildService - X11:XOrg' is up to date. Repository 'Main Repository (OSS)' is up to date. Repository 'openSUSE BuildService - Mozilla' is up to date. Repository 'openSUSE BuildService - KDE4' is up to date. Refreshing 'openSUSE BuildService - Wine CVS Builds' * Cleaning repository 'openSUSE BuildService - Wine CVS Builds' cache * Building repository 'openSUSE BuildService - Wine CVS Builds' cache Refreshing 'openSUSE BuildService - KDE4:Community' * Cleaning repository 'openSUSE BuildService - KDE4:Community' cache * Building repository 'openSUSE BuildService - KDE4:Community' cache Repository 'openSUSE BuildService - KDE:Backports' is up to date. Repository 'openSUSE BuildService - KDE:Community' is up to date. Repository 'openSUSE BuildService - KDE4:Extra-Apps' is up to date. Repository 'home:cb400f' is up to date. Repository 'openSUSE BuildService - X11:XGL' is up to date. Repository 'openSUSE BuildService - OpenOffice.org Extras' is up to date. Repository 'Main Update Repository' is up to date. Refreshing 'Packman Repository' * Cleaning repository 'Packman Repository' cache * Building repository 'Packman Repository' cache Repository 'Google Linux Repository' is up to date. Repository 'VideoLan Repository' is up to date. Repository 'openSUSE BuildService - KDE Playground' is up to date. Repository 'openSUE BuildService - Drivers for Wireless LAN' is up to date. Repository 'NVIDIA Drivers' is up to date. Refreshing 'openSUSE BuildService - Education' * Cleaning repository 'openSUSE BuildService - Education' cache * Building repository 'openSUSE BuildService - Education' cache Repository 'home:the_daemon:yast2' is up to date. Repository 'openSUSE BuildService - KDE3' is up to date. Repository 'Main Repository (NON-OSS)' is up to date. Refreshing 'openSUSE BuildService - Games' * Cleaning repository 'openSUSE BuildService - Games' cache * Building repository 'openSUSE BuildService - Games' cache Repository 'openSUSE BuildService - OpenOffice.org' is up to date. All repositories have been refreshed. * Reading repository 'openSUSE BuildService - X11:XOrg' cache * Reading repository 'Main Repository (OSS)' cache * Reading repository 'openSUSE BuildService - Mozilla' cache * Reading repository 'openSUSE-10.3-OSS-KDE 10.3' cache * Reading repository 'openSUSE BuildService - KDE4' cache * Reading repository 'openSUSE BuildService - Wine CVS Builds' cache * Reading repository 'openSUSE BuildService - KDE4:Community' cache * Reading repository 'openSUSE BuildService - KDE:Backports' cache * Reading repository 'openSUSE BuildService - KDE:Community' cache * Reading repository 'openSUSE BuildService - KDE4:Extra-Apps' cache * Reading repository 'home:cb400f' cache * Reading repository 'openSUSE BuildService - X11:XGL' cache * Reading repository 'openSUSE BuildService - OpenOffice.org Extras' cache * Reading repository 'Main Update Repository' cache * Reading repository 'Packman Repository' cache * Reading repository 'Google Linux Repository' cache * Reading repository 'VideoLan Repository' cache * Reading repository 'openSUSE BuildService - KDE Playground' cache * Reading repository 'openSUE BuildService - Drivers for Wireless LAN' cache * Reading repository 'NVIDIA Drivers' cache * Reading repository 'openSUSE BuildService - Education' cache * Reading repository 'home:the_daemon:yast2' cache * Reading repository 'openSUSE BuildService - KDE3' cache * Reading repository 'Main Repository (NON-OSS)' cache * Reading repository 'openSUSE BuildService - Games' cache * Reading repository 'Repository' cache * Reading repository 'openSUSE BuildService - OpenOffice.org' cache * Reading installed packages [100%] Nothing to do. Version: openSUSE 10.3 alpha:~ # rpm -qa | grep -i zypp zypper-0.8.25-0.1 libzypp-3.26.8-0.1 Thanks -- Regards Scott Newton -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
2008/6/15 Scott Newton
Can anyone explain to me why the openSUSE-updater and zypper command line would give different results? Or should I raise this as a bug?
It looks like you have asked openSUSE-updater to also show upgrades as well as updates. On 10.3 you probably want "zypper up -t package" to also show upgraded packages. -- Benjamin Weber -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 16 June 2008 10:09:07 Benji Weber wrote:
2008/6/15 Scott Newton
: Can anyone explain to me why the openSUSE-updater and zypper command line would give different results? Or should I raise this as a bug?
It looks like you have asked openSUSE-updater to also show upgrades as well as updates. On 10.3 you probably want "zypper up -t package" to also show upgraded packages.
Thanks Benji Doing that gives me what is below which is probably not what I want but at least its more consistent. Any chance we can have zypper to be more consistent with other packaging tools so that zypper update works the same as yum updae, apt-get update and smart update? My logic would be that if I subscribed to a particular repository then I would assume that if I do an update I would automatically get any upgraded packages. Well that gives me: alpha:~ # zypper up -t package * Reading repository 'openSUSE BuildService - X11:XOrg' cache * Reading repository 'Main Repository (OSS)' cache * Reading repository 'openSUSE BuildService - Mozilla' cache * Reading repository 'openSUSE-10.3-OSS-KDE 10.3' cache * Reading repository 'openSUSE BuildService - KDE4' cache * Reading repository 'openSUSE BuildService - Wine CVS Builds' cache * Reading repository 'openSUSE BuildService - KDE4:Community' cache * Reading repository 'openSUSE BuildService - KDE:Backports' cache * Reading repository 'openSUSE BuildService - KDE:Community' cache * Reading repository 'openSUSE BuildService - KDE4:Extra-Apps' cache * Reading repository 'home:cb400f' cache * Reading repository 'openSUSE BuildService - X11:XGL' cache * Reading repository 'openSUSE BuildService - OpenOffice.org Extras' cache * Reading repository 'Main Update Repository' cache * Reading repository 'Packman Repository' cache * Reading repository 'Google Linux Repository' cache * Reading repository 'VideoLan Repository' cache * Reading repository 'openSUSE BuildService - KDE Playground' cache * Reading repository 'openSUE BuildService - Drivers for Wireless LAN' cache * Reading repository 'NVIDIA Drivers' cache * Reading repository 'openSUSE BuildService - Education' cache * Reading repository 'home:the_daemon:yast2' cache * Reading repository 'openSUSE BuildService - KDE3' cache * Reading repository 'Main Repository (NON-OSS)' cache * Reading repository 'openSUSE BuildService - Games' cache * Reading repository 'Repository' cache * Reading repository 'openSUSE BuildService - OpenOffice.org' cache * Reading installed packages [100%] The following packages are going to be upgraded: kde4-gtk-qt-engine DirectFB The following packages are going to be REMOVED: MPlayer gstreamer-0_10-plugins-bad Overall download size: 1.2 M. After the operation, 40.7 M will be freed. -- Regards Scott Newton -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Scott Newton escribió: My logic would be that if I subscribed to a
particular repository then I would assume that if I do an update I would automatically get any upgraded packages.
The current behaviour is expected, zypper update only updates patches by default. It is not inconsistent, it is just different, for very good reasons. -- “First they ignore you, then they laugh at you, then they fight you, then you win.” - Gandhi Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
On Sun, Jun 15, 2008 at 06:47:08PM -0400, Cristian Rodríguez wrote:
Scott Newton escribió: My logic would be that if I subscribed to a
particular repository then I would assume that if I do an update I would automatically get any upgraded packages.
The current behaviour is expected, zypper update only updates patches by default.
It is not inconsistent, it is just different, for very good reasons.
Well, backward compatibility is probably not a "very good reason". I'm in favour of changing 'zypper up' to "update my packages" and renaming the "patch update" to something else, like "zypper pup" or "zypper patch". The reasoning is that most external repositories (like the build service repositories) don't come with patches, so that "update all packages" is needed more often. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Jun 16, 2008 at 10:33:12AM +1200, Scott Newton wrote:
Well that gives me:
alpha:~ # zypper up -t package [...] * Reading installed packages [100%]
The following packages are going to be upgraded: kde4-gtk-qt-engine DirectFB
The following packages are going to be REMOVED: MPlayer gstreamer-0_10-plugins-bad
Hmm, why is it removing packages if you do a 'zypper up'? This looks very strange to me. If you can reproduce this behaviour, can you please create a solver testcase (--debug-solver) and send it to me? Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, 16 Jun 2008 18:24:35 Michael Schroeder wrote:
On Mon, Jun 16, 2008 at 10:33:12AM +1200, Scott Newton wrote:
Well that gives me:
alpha:~ # zypper up -t package [...] * Reading installed packages [100%]
The following packages are going to be upgraded: kde4-gtk-qt-engine DirectFB
The following packages are going to be REMOVED: MPlayer gstreamer-0_10-plugins-bad
Hmm, why is it removing packages if you do a 'zypper up'? This looks very strange to me. If you can reproduce this behaviour, can you please create a solver testcase (--debug-solver) and send it to me?
Michael, I too have seen the same behaviour running the SuSE-updater applet - when configured to show upgrades as well as patches, particularly in the most recent batch of updates of multimedia apps that I've applied, I have seen one or two packages get removed as part of the "upgrade" process. Unfortunately I can't remember exactly what they were - I just figured that there was probably a reason for it so I didn't take much notice. If it happens again I'll note the details. Rodney. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== Necessity is a mother.
participants (5)
-
Benji Weber
-
Cristian Rodríguez
-
Michael Schroeder
-
Rodney Baker
-
Scott Newton