[sles-beta] Kernel Update SP2 > SP3

[Decker Maximilian]

Alright but I think rpm -vFh kernel* or similar would still fail when upgrading SLES 11 SP2 including latest Post-SP2-patches to SP3 GA ?
That would not be the case if we had lets say latest SP2 kernel named "kernel-default-3.0.2085-0.9.3" and SP3 GA "kernel-default-3.0.3074-0.9.3".
(SP2 is offset 2000, SP3 is offset 3000)

Anyway, although it is not a big issue at all, I always wondered if that would not just simplify things.
Especially if a SP is not only an accumulation of updates but also changes the platform to some degree ...


Thanks

- Maximilian 

-----Ursprüngliche Nachricht-----
Von: sles-beta-bounces at lists.suse.com [mailto:sles-beta-bounces at lists.suse.com] Im Auftrag von Marcus Meissner
Gesendet: Freitag, 5. Juli 2013 15:47
An: SUSE Linux Enterprise Server Authorized Beta Program
Betreff: Re: [sles-beta] Kernel Update SP2 > SP3

On Fri, Jul 05, 2013 at 02:40:51PM +0200, Decker Maximilian wrote:
> hm what about adding some sort of SP offset to the minor version ? 
> wouldn't that be an easy way to solve this "lower version number" issue, even if the base version is the same ?
> 
> So let's say all SP2 kernels are 3.0.x-2yyy and for SP3 that would be 3.0.x-3yyy.
> This way the SP3 kernels would always be ahead of the SP2 kernels as far as RPM/zypper is concerned.
> 
> just a thought.

If the RPM version is stable, this would work and we have mechanisms in place for exactly this case.

The RPM version is however not stable, as we are tracking the 3.0.x stable series, where "x" follows the upstream stable version.

This will be a non issue as soon as we have released the first SLES 11 SP3 kernel update, as we will be taking care internally not to let this imbalance happen in the 6 concurrent maintenance months.

Ciao, Marcus
_______________________________________________
sles-beta mailing list
sles-beta at lists.suse.com
http://lists.suse.com/mailman/listinfo/sles-beta