Hi Adrian, I am currently restricted to using the web client. As a first step I now uploaded the tar and the spec seperatly. The local build using rpmbuild -ba e1000e.spec works but obs gives me https://build.opensuse.org/package/live_build_log?arch=i586&package=e1000e&project=home%3Atef32%3Ae1000e&repository=openSUSE_11.3 "Booting from ROM... doing fast boot FATAL: Module kqemu not found. FATAL: Module ext2 not found." Are there missing some features in my spec file? Mit freundlichen Grüßen / Best regards Martin Konold Robert Bosch GmbH Automotive Electronics Postfach 13 42 72703 Reutlingen GERMANY www.bosch.com Tel. +49 7121 35 3322 Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Hermann Scholl; Geschäftsführung: Franz Fehrenbach, Siegfried Dais; Stefan Asenkerschbaumer, Bernd Bohr, Rudolf Colm, Volkmar Denner, Wolfgang Malchow, Peter Marks, Uwe Raschke, Wolf-Henning Scheider, Peter Tyroller -----Original Message----- From: Adrian Schröter [mailto:adrian@suse.de] Sent: Montag, 7. November 2011 13:56 To: opensuse-buildservice@opensuse.org Cc: EXTERNAL Konold Martin (erfrakon, RtP2/TEF72) Subject: Re: [opensuse-buildservice] Creating KMPs Hi Martin, Am Montag, 7. November 2011, 12:47:00 schrieb EXTERNAL Konold Martin:

I am following the documentation in http://www.novell.com/communities/node/9226/using-opensuse-build-service-cr eate-and-distribute-kernel-module-packages#4 .

I have created locally a SRPM containing a SPEC-file for creating a kernel-driver package, a library package and an examples binary RPM.

I am now wondering how to upload a SRPM to obs.

I have the impression that OBS does not expect uploads of SRPMs.

src.rpms are also a built result, so OBS expects the single source files (tar ball and .spec file) to be uploaded. However, there are tools to automate the unpack of srcrpms, either * osc importsrcpkg * add a URL in webui to a src.rpm, it will use the download_src_package source service. bye adrian

Is this correct?

Mit freundlichen Grüßen / Best regards

Martin Konold

Robert Bosch GmbH Automotive Electronics Postfach 13 42 72703 Reutlingen GERMANY www.bosch.com

Tel. +49 7121 35 3322

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Hermann Scholl; Geschäftsführung: Franz Fehrenbach, Siegfried Dais; Stefan Asenkerschbaumer, Bernd Bohr, Rudolf Colm, Volkmar Denner, Wolfgang Malchow, Peter Marks, Uwe Raschke, Wolf-Henning Scheider, Peter Tyroller -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Hi Adrian,

...

Are there missing some features in my spec file?

These are just bugs in our general initrd (just fixed in the appliance).

Thanks for this info! However, they are not FATAL and just ignored. So please do also :) Now I get another error when trying to create a KMP: + make -j -C /usr/src/linux M=/usr/src/packages/BUILD/e1000e-1.6.3/src make: Entering directory `/usr/src/linux-2.6.34-12' ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it. How should I run make in the kernel sources from within my KMP? Mit freundlichen Grüßen / Best regards Martin Konold Robert Bosch GmbH Automotive Electronics Postfach 13 42 72703 Reutlingen GERMANY www.bosch.com Tel. +49 7121 35 3322 Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Hermann Scholl; Geschäftsführung: Franz Fehrenbach, Siegfried Dais; Stefan Asenkerschbaumer, Bernd Bohr, Rudolf Colm, Volkmar Denner, Wolfgang Malchow, Peter Marks, Uwe Raschke, Wolf-Henning Scheider, Peter Tyroller -----Original Message----- bye adrian

Mit freundlichen Grüßen / Best regards

Martin Konold

Robert Bosch GmbH Automotive Electronics Postfach 13 42 72703 Reutlingen GERMANY www.bosch.com

Tel. +49 7121 35 3322

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Hermann Scholl; Geschäftsführung: Franz Fehrenbach, Siegfried Dais; Stefan Asenkerschbaumer, Bernd Bohr, Rudolf Colm, Volkmar Denner, Wolfgang Malchow, Peter Marks, Uwe Raschke, Wolf-Henning Scheider, Peter Tyroller

-----Original Message----- From: Adrian Schröter [mailto:adrian@suse.de] Sent: Montag, 7. November 2011 13:56 To: opensuse-buildservice@opensuse.org Cc: EXTERNAL Konold Martin (erfrakon, RtP2/TEF72) Subject: Re: [opensuse-buildservice] Creating KMPs

Hi Martin,

Am Montag, 7. November 2011, 12:47:00 schrieb EXTERNAL Konold Martin:

...

I am following the documentation in http://www.novell.com/communities/node/9226/using-opensuse-build-service -cr eate-and-distribute-kernel-module-packages#4 .

I have created locally a SRPM containing a SPEC-file for creating a kernel-driver package, a library package and an examples binary RPM.

I am now wondering how to upload a SRPM to obs.

I have the impression that OBS does not expect uploads of SRPMs.

src.rpms are also a built result, so OBS expects the single source files (tar ball and .spec file) to be uploaded.

However, there are tools to automate the unpack of srcrpms, either

* osc importsrcpkg * add a URL in webui to a src.rpm, it will use the download_src_package source service.

bye adrian

...

Is this correct?

Mit freundlichen Grüßen / Best regards

Martin Konold

Robert Bosch GmbH Automotive Electronics Postfach 13 42 72703 Reutlingen GERMANY www.bosch.com

Tel. +49 7121 35 3322

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000; Aufsichtsratsvorsitzender: Hermann Scholl; Geschäftsführung: Franz Fehrenbach, Siegfried Dais; Stefan Asenkerschbaumer, Bernd Bohr, Rudolf Colm, Volkmar Denner, Wolfgang Malchow, Peter Marks, Uwe Raschke, Wolf-Henning Scheider, Peter Tyroller

-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de

-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

...

...

On 11/7/2011 at 09:54 AM, in message <CAGpXXZ+UAUGfXCDfEacmrAHZzf_Ya5fgYGrnxEzEEBHmizGJvQ@mail.gmail.com>, Greg Freemyer <greg.freemyer@gmail.com> wrote: On Mon, Nov 7, 2011 at 11:31 AM, EXTERNAL Konold Martin (erfrakon, RtP2/TEF72) <external.Martin.Konold@de.bosch.com> wrote: Hi Adrian,

...

...

Are there missing some features in my spec file?

...

These are just bugs in our general initrd (just fixed in the appliance).

Thanks for this info!

However, they are not FATAL and just ignored. So please do also :)

Now I get another error when trying to create a KMP:

+ make -j -C /usr/src/linux M=/usr/src/packages/BUILD/e1000e-1.6.3/src make: Entering directory `/usr/src/linux-2.6.34-12'

ERROR: Kernel configuration is invalid. include/generated/autoconf.h or include/config/auto.conf are missing. Run 'make oldconfig && make prepare' on kernel src to fix it.

How should I run make in the kernel sources from within my KMP?

Mit freundlichen Grüßen / Best regards

Martin Konold

Martin,

I have a pretty simple KMP specfile which works for me.

The source and patches are kernel specific, but the specfile should be generic:

https://build.opensuse.org/package/view_file?file=ext4dev.spec&package=ext4de v-snapshots&project=home%3Anext4&srcmd5=27686765b21f1b56480196f1c3a8a66c

Also, the package https://build.opensuse.org/package/show?package=sampledriver&project=home%3Aandavis%3Alinuxcon2011 should pretty much match the sample in http://www.novell.com/communities/node/9226/using-opensuse-build-service-cre... . HTH, Ann

Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

Hi,

...

...

On 11/7/2011 at 10:55 AM, in message <CAGpXXZ+76rDiBfH-5ME3-ojvNGHGrw6h-z6bO79ah=+TDu5XhQ@mail.gmail.com>, Greg Freemyer <greg.freemyer@gmail.com> wrote: On Mon, Nov 7, 2011 at 12:04 PM, Ann Davis <andavis@suse.com> wrote:

Also, the package

https://build.opensuse.org/package/show?package=sampledriver&project=home%3Aan davis%3Alinuxcon2011 should pretty much match the sample in

...

http://www.novell.com/communities/node/9226/using-opensuse-build-service-cre... d-distribute-kernel-module-packages#4 .

...

HTH,

Ann

Ann,

If you are maintaining that as an example, you should move the changelog out of the specfile and into a *.changes file. A submission to factory with it the way you have it would be rejected I believe.

Good point, but I have a few questions/comments: 1) This sample is intended target enterprise distros (like SLE and RHEL). Reasons: a) IMO, KMPs are of limited use unless there's an expectation of kABI stability across kernel updates. Enterprise distros (like SLE and RHEL) generally have kABI-stability policies; I'm not sure about other distros like openSUSE, Fedora, etc. Of course, the situation is improved now that many distros have symbol-granularity (rather than symset-granularity) kABI-matching at an rpm level. b) This sample will build and install fine on openSUSE. But it doesn't work on Fedora, because Fedora did not incorporate the standard KMP macros that we worked on in the LF Driver Backport workgroup. I'd be very happy to see folks in the Fedora community exert some pressure in this area... ;) 2) The whole *.changes thing has always confused me. Is this a cross-distro standard? What is the reason to have a *.changes file rather than just tracking the changes in the spec file? 3) Given the above notes, would it make sense to submit this to factory? I'm not opposed to it, I just haven't given it much thought. TIA, Ann

Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org

On Mon, Nov 07, 2011 at 11:36:58AM -0700, Ann Davis wrote: [ 8< ]

2) The whole *.changes thing has always confused me. Is this a cross-distro standard? What is the reason to have a *.changes file rather than just tracking the changes in the spec file?

http://lizards.opensuse.org/2009/04/21/how-to-track-changes-in-packages-osc-... might be a good explanation why we're doing it this way. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

Am Dienstag, 8. November 2011, 10:35:18 schrieb Ann Davis:

...

...

...

On 11/8/2011 at 10:05 AM, in message <20111108170532.GB4977@giles.fritz.box>, Lars Müller<lmuelle@suse.de> wrote: On Mon, Nov 07, 2011 at 11:36:58AM -0700, Ann Davis wrote: [ 8< ]

...

2) The whole *.changes thing has always confused me. Is this a

cross-distro standard? What is the reason to have a *.changes file rather than just tracking the changes in the spec file?

Inside of the spec file you increase the rpm database size on the installed system. So we need a stripped one inside of it while we don't want to loose the full change log in the .changes file.

...

http://lizards.opensuse.org/2009/04/21/how-to-track-changes-in-packages- osc- vc/ might be a good explanation why we're doing it this way.

Thanks for the link. I was worried that using a *.changes file instead of a %changelog wouldn't work when building rpms for non-SUSE distros. But I tested and the *.changes info gets into my RHEL rpms so I guess it's all good. :)

Ann

...

Lars -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org