[opensuse-kernel] Re: [opensuse-factory] 'zypper dup' updating kernel when 'zypper up' does not? (fwd)
[ -> 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-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Monday 2009-09-07 01:55, Gerald Pfeifer wrote:
[ -> 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.
It sounds a little like all you want/need is that rpm sorts "_" < "." as a special case. That would not seem incongruous to do so, given "" < "~" is done in some distros and/or code (zypper too partially). -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+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-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Mon, 7 Sep 2009, Michal Marek wrote:
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)
I don't have a personal preference. Whatever fixes the update problem (bug, actually) I ran into will do. :-) I guess it's your call what is easier to implement and maintain... 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-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Gerald Pfeifer napsal(a):
On Mon, 7 Sep 2009, Michal Marek wrote:
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)
I don't have a personal preference. Whatever fixes the update problem (bug, actually) I ran into will do. :-) I guess it's your call what is easier to implement and maintain...
I kept the kernel versioning as it is, because RPM can cope with it and there is no need to diverge from upstream, and changed KMPs to use version_2.6.x.0_... for mainline kernels. KMP versions are already obfuscated enough so the additional .0 should not make it any worse ;). Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (3)
-
Gerald Pfeifer -
Jan Engelhardt -
Michal Marek