[opensuse-buildservice] How to build KMP's against latest 10.3 update kernel?
Hi, I have problems building a KMP against the latest 10.3 update kernel at [1]. I selected "openSUSE:10.3:Update/standard" as repository but it is still built against the original 10.3 kernel. Can somebody give me a hint? Regards, Helmut [1] https://build.opensuse.org/project/show?project=driver%3Awireless%3A10.3 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi, Helmut Schaa wrote:
I have problems building a KMP against the latest 10.3 update kernel at [1]. I selected "openSUSE:10.3:Update/standard" as repository but it is still built against the original 10.3 kernel.
Can somebody give me a hint?
I've been pondering about this for a while, since I'd like to compile modules for a variety of kernel-versions. In my understanding, you'll always get only one version (the original) with the repositories. I think what I'll do is to include the header files of all kernels I'd like to have the binary-module for as source files in the spec file and then compile it against those. But maybe someone has a better idea. Christof --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Fri, Dec 07, 2007 at 01:32:24PM +0200, Christof Hanke wrote:
Hi,
Helmut Schaa wrote:
I have problems building a KMP against the latest 10.3 update kernel at [1]. I selected "openSUSE:10.3:Update/standard" as repository but it is still built against the original 10.3 kernel.
Can somebody give me a hint?
I've been pondering about this for a while, since I'd like to compile modules for a variety of kernel-versions. In my understanding, you'll always get only one version (the original) with the repositories. I think what I'll do is to include the header files of all kernels I'd like to have the binary-module for as source files in the spec file and then compile it against those. But maybe someone has a better idea.
The Update repository should have our latest kernel update too. If not, ask Adrian. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Freitag, 7. Dezember 2007 12:35:20 schrieb Marcus Meissner: <snip>
The Update repository should have our latest kernel update too. If not, ask Adrian.
Ok, I was just informed about bug 346768 - "Kernel on openSUSE 10.3 Update in the BS is still the one from GM". Thanks, Helmut --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 07 December 2007 12:35:20 wrote Marcus Meissner:
On Fri, Dec 07, 2007 at 01:32:24PM +0200, Christof Hanke wrote:
Hi,
Helmut Schaa wrote:
I have problems building a KMP against the latest 10.3 update kernel at [1]. I selected "openSUSE:10.3:Update/standard" as repository but it is still built against the original 10.3 kernel.
Can somebody give me a hint?
I've been pondering about this for a while, since I'd like to compile modules for a variety of kernel-versions. In my understanding, you'll always get only one version (the original) with the repositories. I think what I'll do is to include the header files of all kernels I'd like to have the binary-module for as source files in the spec file and then compile it against those. But maybe someone has a better idea.
The Update repository should have our latest kernel update too. If not, ask Adrian.
We had a missconfiguration for 10.3. This is fixed now, kernel packages gets uploaded to the :Update repo. You do not need to do anything, the build service scheduler will see the change and trigger all affected packages. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Freitag, 7. Dezember 2007 13:02:52 schrieb Adrian Schröter:
On Friday 07 December 2007 12:35:20 wrote Marcus Meissner:
On Fri, Dec 07, 2007 at 01:32:24PM +0200, Christof Hanke wrote:
Hi,
Helmut Schaa wrote:
I have problems building a KMP against the latest 10.3 update kernel at [1]. I selected "openSUSE:10.3:Update/standard" as repository but it is still built against the original 10.3 kernel.
Can somebody give me a hint?
I've been pondering about this for a while, since I'd like to compile modules for a variety of kernel-versions. In my understanding, you'll always get only one version (the original) with the repositories. I think what I'll do is to include the header files of all kernels I'd like to have the binary-module for as source files in the spec file and then compile it against those. But maybe someone has a better idea.
The Update repository should have our latest kernel update too. If not, ask Adrian.
We had a missconfiguration for 10.3. This is fixed now, kernel packages gets uploaded to the :Update repo.
You do not need to do anything, the build service scheduler will see the change and trigger all affected packages.
Thanks :) Helmut --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Marcus Meissner wrote:
On Fri, Dec 07, 2007 at 01:32:24PM +0200, Christof Hanke wrote:
The Update repository should have our latest kernel update too. If not, ask Adrian. Well, yes, but I'm not interested in updated kernels only but past kernels also.
Thanks, Christof --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Friday 07 December 2007 07:28:36 am Christof Hanke wrote:
Marcus Meissner wrote:
On Fri, Dec 07, 2007 at 01:32:24PM +0200, Christof Hanke wrote:
The Update repository should have our latest kernel update too. If not, ask Adrian.
Well, yes, but I'm not interested in updated kernels only but past kernels also.
I agree. We need to figure out how to support driver package maintainers well inside the build service. This is especially true for SLE, where service packs also make things complicated. Are there any elegant solutions to this problem? Thanks! Donavan --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Dec 11, 2007 at 09:01:04PM -0500, Donavan Pantke wrote:
On Friday 07 December 2007 07:28:36 am Christof Hanke wrote:
Marcus Meissner wrote:
On Fri, Dec 07, 2007 at 01:32:24PM +0200, Christof Hanke wrote:
The Update repository should have our latest kernel update too. If not, ask Adrian.
Well, yes, but I'm not interested in updated kernels only but past kernels also.
I agree. We need to figure out how to support driver package maintainers well inside the build service. This is especially true for SLE, where service packs also make things complicated.
Are there any elegant solutions to this problem?
I do not see why you would want to build drivers against the older kernels (of the same distribution) with security problems. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 11 December 2007 10:16:02 pm Marcus Meissner wrote:
On Tue, Dec 11, 2007 at 09:01:04PM -0500, Donavan Pantke wrote:
On Friday 07 December 2007 07:28:36 am Christof Hanke wrote:
Marcus Meissner wrote:
On Fri, Dec 07, 2007 at 01:32:24PM +0200, Christof Hanke wrote:
The Update repository should have our latest kernel update too. If not, ask Adrian.
Well, yes, but I'm not interested in updated kernels only but past kernels also.
I agree. We need to figure out how to support driver package maintainers well inside the build service. This is especially true for SLE, where service packs also make things complicated.
Are there any elegant solutions to this problem?
I do not see why you would want to build drivers against the older kernels (of the same distribution) with security problems.
The problem lies with organizations that have tighter change control mechanisms. In these cases, someone may choose to skip over a particular update, either waiting for a good time, or deciding that the security issues addressed aren't worth the expense to do an update (especially since kernel updates require reboots). If someone needs to do a driver update, they would have to perform a manual rebuild if the drivers rebuilt against a newer kernel. Note that rebuilds for other packages, downstream packages won't fundamentally break unless it's a huge problem, in which case people have a big incentive to update. However, kernel updates can introduce incompatibilities at a much finer grain. I think the build service could help in these situations, or is it too big a deal for the build service to support? Thanks! Donavan
Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wednesday 12 December 2007 03:01:04 wrote Donavan Pantke:
On Friday 07 December 2007 07:28:36 am Christof Hanke wrote:
Marcus Meissner wrote:
On Fri, Dec 07, 2007 at 01:32:24PM +0200, Christof Hanke wrote:
The Update repository should have our latest kernel update too. If not, ask Adrian.
Well, yes, but I'm not interested in updated kernels only but past kernels also.
I agree. We need to figure out how to support driver package maintainers well inside the build service. This is especially true for SLE, where service packs also make things complicated.
For SLE it is planned to provide versions the past SP as well (including the kernel). It is currently not planned to provide the different released kernel versions for SLE in the opensuse build service. Matthias would be the person to speak about that :) bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Donavan Pantke
I agree. We need to figure out how to support driver package maintainers well inside the build service. This is especially true for SLE, where service packs also make things complicated.
Are there any elegant solutions to this problem?
I haven't had time to do it yet however this is what I will explore in January: I import repositories for each kernel update (so you have them all as build targets). I then host the driver package version as individual packages in an umbrella project for this package, like this (I'll motivate later on why): project: some-driver package: some-driver-v1.2.3 (tested for chipset rev X) package: some-driver-v1.3.4 (tested for chipset rev Y) package: some-driver-v1.4.2 (tested for chipset rev Z) Then I use some code like this to automatically build all these packages for all the target kernels: https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/clientlib/p... (I intend to give this a tad more testing at the beginning of the new year) Then I aggregate the exact packages I need for some chipset revision or for some product into a project for that product: project: some cool card (has chipset rev Y) aggregates: cool-card-driver-kit from: some-driver-v1.3.4 If the driver turns out to be broken for this hardware, the some-driver project gets a new pacakge: project: some-driver package: some-driver-v1.2.3 (tested for chipset rev X) package: some-driver-v1.3.4 (tested for chipset rev Y) package: some-driver-v1.4.2 (tested for chipset rev Z) package: some-driver-v1.4.7 (tested for chipset rev AA, updated for Y) And the some cool card project is updated to now aggregate the new driver: project: some cool card (has chipset rev Y) aggregates: cool-card-driver-kit from: some-driver-v1.4.7 That's the rough idea, I've got to rush but I wanted to reply already :) Which driver packages do you maintain? S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Helmut,
Helmut Schaa
I have problems building a KMP against the latest 10.3 update kernel at [1]. I selected "openSUSE:10.3:Update/standard" as repository but it is still built against the original 10.3 kernel.
Can somebody give me a hint?
It looks to me the update kernel has not made it into that repo yet. At least there is no kernel listed here: osc req -m GET https://api.opensuse.org/build/openSUSE:10.3:Update/standard/i586/_repositor... So the build server rightfully so falls back to the openSUSE:10.3/standard kernel... S. -- Susanne Oberhauser +49-911-74053-574 SUSE -- a Novell Business OPS Engineering Maxfeldstraße 5 Processes and Infrastructure Nürnberg SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (6)
-
Adrian Schröter -
Christof Hanke -
Donavan Pantke -
Helmut Schaa -
Marcus Meissner -
Susanne Oberhauser