Mailinglist Archive: opensuse-kernel (48 mails)

< Previous Next >
Re: [opensuse-kernel] How do you adjust or generate the series.conf for linux kernel v3.0.1 so it can compile.
On Tuesday, August 09, 2011 12:20:24 Michal Marek wrote:
On 9.8.2011 11:17, Jiri Slaby wrote:
On 08/09/2011 10:43 AM, Andreas Jaeger wrote:
On Sunday, August 07, 2011 18:46:00 Jiri Slaby wrote:
On 08/07/2011 04:36 AM, doiggl@xxxxxxxxxxxxxxxxxx wrote:
Hello
How do you adjust or generate the series.conf for linux kernel v3.0.1
so it can compile.

We look what patches are contained in the stable release and prune them
from the series.conf. Then we apply all the remaining patches from
series.conf and fix the conflicts which might appear.

project is located at
--
https://build.opensuse.org/package/show?package=kernel-default&project
=ho me%3Adoiggl

So far this this patch has failed in series.conf
*** patch ../patches.fixes/SCSI-fix-crash-in-scsi_dispatch_cmd.patch
failed ***
Thanks Glenn

Why do you bother anyway? Kernel:stable already has 3.0.1 in.

Mmh, but Kernel:HEAD does not have it - and openSUSE:Factory is still at
3.0,

Yes, when I last asked if I should push stable trees into HEAD, I got no
reply, so I'm not doing that. Hence HEAD/factory is now supposed to
contain only "non-stable" releases and -rcs.

Jeff usually skips -rc1 in master, to avoid too much breakage (those who
wish to test -rc1s can use the vanilla branch). So it IMO would not hurt
to track the latest stable tree if there is no -rc2 yet. So that the
Factory kernel shows some progress :-). But it's only my opinion.

Or submit from stable to Factory...

Andreas
--
Andreas Jaeger, Program Manager openSUSE
aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kernel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups