[opensuse-factory] 'zypper dup' updating kernel when 'zypper up' does not? (fwd)
The following surprised me a bit; is this related to preload-kmp-default or the new kernel-desktop? tomonaga# zypper up ; echo "====" ; zypper -v dup : Nothing to do. ==== : The following packages are going to be upgraded: kernel-default 2.6.30-10.1 -> 2.6.30.2-1.1 kernel-default-base 2.6.30-10.1 -> 2.6.30.2-1.1 kernel-default-extra 2.6.30-10.1 -> 2.6.30.2-1.1 The following packages are going to be downgraded: libgimpprint 4.2.7-67.1 -> 4.2.7-5.1 preload-kmp-default 1.0_2.6.30_10-15.9 -> 1.0_2.6.30.2_1-17.2 3 packages to upgrade, 2 to downgrade. And when I try to remove preload-kmp-default I get: # zypper rm preload-kmp-default Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW packages are going to be installed: kernel-desktop kernel-desktop-base preload-kmp-desktop The following package is going to be REMOVED: preload-kmp-default 3 new packages to install, 1 to remove. At which point I figured I'd better ask here. ;-) Gerald -- Dr. Gerald Pfeifer E gp@novell.com SUSE Linux Products GmbH Director Product Management F +49(911)74053-483 HRB 16746 (AG Nuremberg) SUSE Linux Enterprise, openSUSE, Appliances GF Markus Rex -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Am Mittwoch 29 Juli 2009 schrieb Gerald Pfeifer:
The following surprised me a bit; is this related to preload-kmp-default or the new kernel-desktop?
tomonaga# zypper up ; echo "====" ; zypper -v dup
Nothing to do. ====
The following packages are going to be upgraded: kernel-default 2.6.30-10.1 -> 2.6.30.2-1.1 kernel-default-base 2.6.30-10.1 -> 2.6.30.2-1.1 kernel-default-extra 2.6.30-10.1 -> 2.6.30.2-1.1
The following packages are going to be downgraded: libgimpprint 4.2.7-67.1 -> 4.2.7-5.1 preload-kmp-default 1.0_2.6.30_10-15.9 -> 1.0_2.6.30.2_1-17.2
3 packages to upgrade, 2 to downgrade.
I'm afraid the problem is that it sees 2.6.30_10 as higher version than 2.6.30.2_1 because it compares by split(/\./, $version) - and there you only compare 30 with 30_10 - and there usually _10 is the higher one. The fix would be to always name our kernel 2.6.30.0
And when I try to remove preload-kmp-default I get:
# zypper rm preload-kmp-default Loading repository data... Reading installed packages... Resolving package dependencies...
The following NEW packages are going to be installed: kernel-desktop kernel-desktop-base preload-kmp-desktop
The following package is going to be REMOVED: preload-kmp-default
3 new packages to install, 1 to remove.
At which point I figured I'd better ask here. ;-)
preload recommends a preload-kmp and there is only -desktop and -default available. So if you remove -default, it will pull the next recommended package I guess and that pulls kernel-desktop. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Jul 29, 2009 at 10:16:55AM +0200, Stephan Kulow wrote:
I'm afraid the problem is that it sees 2.6.30_10 as higher version than 2.6.30.2_1 because it compares by split(/\./, $version) - and there you only compare 30 with 30_10 - and there usually _10 is the higher one
Just to clarify things, rpm splits by /[^a-zA-Z0-9]/, so 2.6.30_10 compares to 2.6.30.2_1 as 2 6 30 10 2 6 30 2 1 and 10 > 2. 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-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
[ -> opensuse-kernel ] On Wed, 29 Jul 2009, Michael Schroeder wrote:
On Wed, Jul 29, 2009 at 10:16:55AM +0200, Stephan Kulow wrote:
I'm afraid the problem is that it sees 2.6.30_10 as higher version than 2.6.30.2_1 because it compares by split(/\./, $version) - and there you only compare 30 with 30_10 - and there usually _10 is the higher one Just to clarify things, rpm splits by /[^a-zA-Z0-9]/, so 2.6.30_10 compares to 2.6.30.2_1 as
2 6 30 10 2 6 30 2 1
and 10 > 2.
So, reading this again, it seems the best workaround/fix will be to name the next version of the kernel 2.6.32.0 instead of 2.6.32? For somewhat similar reasons this is why I got upstream GCC versioning for the first release from any given branch changed from 4.x to 4.x.0. Can we do the same for the openSUSE kernel? Or actually upstream even? Gerald -- Dr. Gerald Pfeifer E gp@novell.com SUSE Linux Products GmbH Director Product Management F +49(911)74053-483 HRB 16746 (AG Nuremberg) SUSE Linux Enterprise, openSUSE, Appliances GF Markus Rex -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Gerald Pfeifer napsal(a):
[ -> opensuse-kernel ]
On Wed, 29 Jul 2009, Michael Schroeder wrote:
On Wed, Jul 29, 2009 at 10:16:55AM +0200, Stephan Kulow wrote:
I'm afraid the problem is that it sees 2.6.30_10 as higher version than 2.6.30.2_1 because it compares by split(/\./, $version) - and there you only compare 30 with 30_10 - and there usually _10 is the higher one Just to clarify things, rpm splits by /[^a-zA-Z0-9]/, so 2.6.30_10 compares to 2.6.30.2_1 as
2 6 30 10 2 6 30 2 1
and 10 > 2.
So, reading this again, it seems the best workaround/fix will be to name the next version of the kernel 2.6.32.0 instead of 2.6.32?
Or maybe just change it for KMPs? kernel-default 2.6.31-10 -> foo-kmp-default-1.0_2.6.31.0_10 ^^ kernel-default 2.2.31.1-5 -> foo-kmp-default-1.0_2.6.31.1_5 (no change) Michal -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Gerald Pfeifer -
Michael Schroeder -
Michal Marek -
Stephan Kulow