Mailinglist Archive: opensuse-factory (594 mails)

< Previous Next >
Re: [opensuse-factory] 'zypper dup' updating kernel when 'zypper up' does not? (fwd)
  • From: Gerald Pfeifer <gp@xxxxxxxxxx>
  • Date: Mon, 7 Sep 2009 01:55:05 +0200 (CEST)
  • Message-id: <alpine.LNX.2.00.0909070151560.3178@xxxxxxxxxxxxx>
[ -> 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@xxxxxxxxxx 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@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups