[opensuse-buildservice] Create Add-On product with OBS: Setup and repos?
Hi all, I'd like to build an addon CD using a private OBS instance. I've taken a look at an existing product osc co OBS:Server:2.5 _product and tried to create a first minimal example from that. My group definition contains just this: <?xml version="1.0" encoding="UTF-8"?> <group name="Test"> <packagelist> <package name="bash" /> </packagelist> </group> After checking all the files in via osc, I get the following packages: _product _product:Test-Addon-cd-cd-i586_x86_64 _product:Test-Addon-release However, the only package that get's actually built is _product:Test-Addon-release. The others are in state 'excluded'. How can I find out, *why* they are excluded? I've tried to configure the repositories according to: https://build.opensuse.org/project/meta/OBS:Server:2.5 where it reads: <repository name="images"> <path project="OBS:Server:2.5" repository="openSUSE_13.1"/> <path project="openSUSE:Tools" repository="openSUSE_13.1"/> <path project="openSUSE:13.1:NonFree" repository="standard"/> <path project="openSUSE:13.1:Update" repository="standard"/> <arch>x86_64</arch> </repository> I assume I don't need the first nor the NonFree one. The standard openSUSE 13.1 repo is locally available and configured. What about openSUSE:Tools? Is this generally needed for building addons? TIA and regards, Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de Tel. +49 - 40 - 244 2407 - 14 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, 2015-10-20 at 19:07 +0200, Till Dörges wrote:
Hi all,
I'd like to build an addon CD using a private OBS instance.
<snip>
I've tried to configure the repositories according to:
https://build.opensuse.org/project/meta/OBS:Server:2.5
where it reads:
<repository name="images"> <path project="OBS:Server:2.5" repository="openSUSE_13.1"/> <path project="openSUSE:Tools" repository="openSUSE_13.1"/> <path project="openSUSE:13.1:NonFree" repository="standard"/> <path project="openSUSE:13.1:Update" repository="standard"/> <arch>x86_64</arch> </repository>
I assume I don't need the first nor the NonFree one. The standard openSUSE 13.1 repo is locally available and configured.
What about openSUSE:Tools? Is this generally needed for building addons?
You should only need a repo that contains the dependencies for building a kiwi image. So, base build system, plus kiwi and the proper kiwi -instsource-plugins package and a few other things. Should be all in the 13.1 repo you have. Pay attention to the project config. Specifically the following definition: %if "%_repository" == "images" Type: kiwi Repotype: staticlinks Patterntype: none %endif That will instruct the build service to build kiwi images in the "images" repo target. Also the following line is required to pull in the right packages for building the add-on image: Substitute: kiwi-packagemanager:instsource kiwi-instsource cdrkit-cdrtools-compat syslinux kiwi-instsource-plugins-openSUSE-12-1 The kiwi-instsource-plugins package needs to match the distribution you are building for to be sure it creates a compatible add-on. The proper one should be provided with the target distribution. The other kiwi substitutions are for live images and not required for add-on images. -Scott
Hi Scott, Andreas, Adrian, thanks for your answers! Am 20.10.2015 um 19:40 schrieb Scott Bahling:
On Tue, 2015-10-20 at 19:07 +0200, Till Dörges wrote:
I'd like to build an addon CD using a private OBS instance.
<snip>
Pay attention to the project config. Specifically the following definition:
%if "%_repository" == "images" Type: kiwi Repotype: staticlinks Patterntype: none %endif [...] Substitute: kiwi-packagemanager:instsource kiwi-instsource cdrkit-cdrtools-compat syslinux kiwi-instsource-plugins-openSUSE-12-1
I did this and things changed. ;-) But somewhere something's still wrong... If I add an "images" repository with just the openSUSE 13.1 standard repository for x86_64: <repository name="images"> <path project="openSUSE.org:13.1" repository="standard"/> <arch>x86_64</arch> </repository> I get: nothing provides master-boot-code needed by kiwi for the package _product:Test-Addon-cd-cd-x86_64 I'm not sure why it does that because the RPM generally is available, however only as an i586 RPM. I solved it by adding a repo with a dummy x86_64 RPM which simply contains a "Provides: master-boot-code", which works fine for a different instance of the problem (dependency solving works, right RPM actually get's pulled in). After having added the 2nd path to the images repository I now get No live log available: remote error: _product Test-Addon-cd-cd-x86_64 no logfile for the package _product:Test-Addon-cd-cd-x86_64 I'm trying this on OBS 2.6.3 on openSUSE 13.1, x86-64. Regards and TIA -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de Tel. +49 - 40 - 244 2407 - 14 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hello all, I still can't create an addon CD. Neither on our local OBS instance nor on build.opensuse.org. In order to rule out a problem with our private OBS instance I tried a testbuild on build.opensuse.org, but I'm already stuck when trying to commit the package: --- snip (osc commit ... (version with --debug below)) --- user@box:~/tmp/home:tdoerges/TestB> osc commit -m "Initial commit" Server returned an error: HTTP Error 401: basic auth failed --- snap --- Login with a browser via the webinterface works just fine. I've tried both removing ~/.oscrc and setting a new password via the webinterface. I'm using the standard OSC 0.152 supplied with openSUSE 13.1. I'd greatly appreciate any help in resolving either issue - auth problem with build.opensuse.org - finding the cause (see below) for this error message No live log available: remote error: _product Test-Addon-cd-cd-x86_64 no logfile Thanks and regards -- Till --- snip (osc --debug commit ...) --- user@box:~/tmp/home:tdoerges/TestB> osc --debug commit -v -m "Initial commit" GET https://build.opensuse.org/source/home:tdoerges GET https://build.opensuse.org/source/home:tdoerges/TestB?rev=latest POST https://build.opensuse.org/source/home:tdoerges/TestB?cmd=getprojectservices Server returned an error: HTTP Error 401: basic auth failed Date: Thu, 22 Oct 2015 13:49:54 GMT Server: Apache/2.2.12 (Linux/SUSE) Strict-Transport-Security: max-age=31536000 cache-control: no-cache vary: Accept-Encoding x-xss-protection: 1; mode=block www-authenticate: basic realm="API login" x-opensuse-runtimes: {"view":0.8557540131732821,"db":0.49792299999999995,"backend":0,"xml":0} x-request-id: 0b7f10e8-fc49-4ff7-9c1f-ade4a3471c83 x-opensuse-apiversion: 2.6.51.git20151013.08e8db5 x-runtime: 0.007432 x-frame-options: SAMEORIGIN x-content-type-options: nosniff x-opensuse-errorcode: anonymous_user X-Powered-By: Phusion Passenger 5.0.7 Status: 401 Unauthorized Content-Type: application/xml; charset=utf-8 Connection: close Transfer-Encoding: chunked --- snap --- Am 21.10.2015 um 18:19 schrieb Till Dörges:
Hi Scott, Andreas, Adrian,
thanks for your answers!
Am 20.10.2015 um 19:40 schrieb Scott Bahling:
On Tue, 2015-10-20 at 19:07 +0200, Till Dörges wrote:
I'd like to build an addon CD using a private OBS instance.
<snip>
Pay attention to the project config. Specifically the following definition:
%if "%_repository" == "images" Type: kiwi Repotype: staticlinks Patterntype: none %endif [...] Substitute: kiwi-packagemanager:instsource kiwi-instsource cdrkit-cdrtools-compat syslinux kiwi-instsource-plugins-openSUSE-12-1
I did this and things changed. ;-) But somewhere something's still wrong...
If I add an "images" repository with just the openSUSE 13.1 standard repository for x86_64:
<repository name="images"> <path project="openSUSE.org:13.1" repository="standard"/> <arch>x86_64</arch> </repository>
I get:
nothing provides master-boot-code needed by kiwi
for the package _product:Test-Addon-cd-cd-x86_64
I'm not sure why it does that because the RPM generally is available, however only as an i586 RPM. I solved it by adding a repo with a dummy x86_64 RPM which simply contains a "Provides: master-boot-code", which works fine for a different instance of the problem (dependency solving works, right RPM actually get's pulled in).
After having added the 2nd path to the images repository I now get
No live log available: remote error: _product Test-Addon-cd-cd-x86_64 no logfile
for the package _product:Test-Addon-cd-cd-x86_64
I'm trying this on OBS 2.6.3 on openSUSE 13.1, x86-64.
Regards and TIA -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de Tel. +49 - 40 - 244 2407 - 14 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Oct 22, 2015 at 4:02 PM, Till Dörges
--- snip (osc commit ... (version with --debug below)) --- user@box:~/tmp/home:tdoerges/TestB> osc commit -m "Initial commit" Server returned an error: HTTP Error 401: basic auth failed --- snap --- […]
I'd greatly appreciate any help in resolving either issue - auth problem with build.opensuse.org
Moin Till, I'm seeing this every few months. I don't know the reason (I have a suspicion it has to do with "gnome_keyring=1" in my config), but my quickfix ist to: - rm ~/.osc_cookiejar (admittedly, I haven't tested if this step is actually needed). - comment the "[https://api.opensuse.org]" section in your ~/.oscrc - run a command like "osc -A https://api.opensuse.org ls" to recreate the section (you will need to reenter your credentials) - afterwards, re-add any options besides "user" and "passx" you had (like "keyring=1", "email" etc.) -- Kind regards Christopher 'm4z' Holm / 686f6c6d "We must respect the other fellow's religion, but only in the sense and to the extent that we respect his theory that his wife is beautiful and his children smart." --H. L. Mencken -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am 22.10.2015 um 19:18 schrieb 686f6c6d:
On Thu, Oct 22, 2015 at 4:02 PM, Till Dörges
wrote: --- snip (osc commit ... (version with --debug below)) --- user@box:~/tmp/home:tdoerges/TestB> osc commit -m "Initial commit" Server returned an error: HTTP Error 401: basic auth failed --- snap --- […]
I'd greatly appreciate any help in resolving either issue - auth problem with build.opensuse.org
I'm seeing this every few months. I don't know the reason (I have a suspicion it has to do with "gnome_keyring=1" in my config), but my quickfix ist to: - rm ~/.osc_cookiejar (admittedly, I haven't tested if this step is actually needed). - comment the "[https://api.opensuse.org]" section in your ~/.oscrc - run a command like "osc -A https://api.opensuse.org ls" to recreate the section (you will need to reenter your credentials) - afterwards, re-add any options besides "user" and "passx" you had (like "keyring=1", "email" etc.)
Thanks for your reply. Unfortunately this doesn't do the trick. I've also tried removing both .osc_cookiejar and .oscrc in order to start from scratch. Doesn't work either. I'm currently working around this using the "Add file" button in the web UI ... Regards -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de Tel. +49 - 40 - 244 2407 - 14 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Till Dörges
Thanks for your reply. Unfortunately this doesn't do the trick. I've also tried removing both .osc_cookiejar and .oscrc in order to start from scratch. Doesn't work either.
Use "osc --http-full-debug" and look for the "Authorization:" header to see what osc sends as credentials. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am 21.10.2015 um 18:19 schrieb Till Dörges:
I'm not sure why it does that because the RPM generally is available, however only as an i586 RPM. I solved it by adding a repo with a dummy x86_64 RPM which simply contains a "Provides: master-boot-code", which works fine for a different instance of the problem (dependency solving works, right RPM actually get's pulled in).
As an aside: "FileProvides: master-boot-code kiwi" in the project config seems to accomplish this, too.
After having added the 2nd path to the images repository I now get
No live log available: remote error: _product Test-Addon-cd-cd-x86_64 no logfile
for the package _product:Test-Addon-cd-cd-x86_64
I managed to build my test case on build.opensuse.org (https://build.opensuse.org/project/show/home:tdoerges). The important change was to include the repo <repository path="obs://home:tdoerges/openSUSE_13.1"/> in the project definition, because here these automatically built, but required RPMs could be found: Test-Addon-release-0.0-1.1.x86_64.rpm Test-Addon-release-cd-0.0-1.1.x86_64.rpm As for building an addon CD on our private instance: With an updated repository configuration kiwi actually starts doing things, but complained about: --- snip --- [ 48s] [E] Metapackage <skelcd-openSUSE> not available for required i586 architecture! --- snap --- Simply excluding the <metadata> tag seems to do the trick. And a quick check whether YaST actually accepts the generated ISO looked good. :-) Regards -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de Tel. +49 - 40 - 244 2407 - 14 Fax +49 - 40 - 244 2407 - 24 PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Till Dörges
Am 21.10.2015 um 18:19 schrieb Till Dörges:
I'm not sure why it does that because the RPM generally is available, however only as an i586 RPM. I solved it by adding a repo with a dummy x86_64 RPM which simply contains a "Provides: master-boot-code", which works fine for a different instance of the problem (dependency solving works, right RPM actually get's pulled in).
As an aside: "FileProvides: master-boot-code kiwi" in the project config seems to accomplish this, too.
To ignore dependencies use "Ignore: master-boot-code" or "Ignore: kiwi:master-boot-code". Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Till Dörges
After checking all the files in via osc, I get the following packages:
_product _product:Test-Addon-cd-cd-i586_x86_64 _product:Test-Addon-release
However, the only package that get's actually built is _product:Test-Addon-release. The others are in state 'excluded'.
How can I find out, *why* they are excluded?
Did you create a repository with Type: kiwi? Take a look at the top of the prjconf of OBS:Server:2.5. %if "%_repository" == "images" Type: kiwi Repotype: staticlinks Patterntype: none %endif Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 20. Oktober 2015, 20:19:37 CEST wrote Andreas Schwab:
Till Dörges
writes: After checking all the files in via osc, I get the following packages:
_product _product:Test-Addon-cd-cd-i586_x86_64 _product:Test-Addon-release
However, the only package that get's actually built is _product:Test-Addon-release. The others are in state 'excluded'.
How can I find out, *why* they are excluded?
Did you create a repository with Type: kiwi? Take a look at the top of the prjconf of OBS:Server:2.5.
Or just use the webui, all that happens when you click on adding a kiwi repository.
%if "%_repository" == "images" Type: kiwi Repotype: staticlinks Patterntype: none %endif
Andreas.
-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Dienstag, 20. Oktober 2015, 19:07:44 CEST wrote Till Dörges: ...
What about openSUSE:Tools? Is this generally needed for building addons?
No, all our base distros should provide kiwi* packages which are sufficient to build products. At least they were used to build their own distro medias :) -- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (5)
-
686f6c6d
-
Adrian Schröter
-
Andreas Schwab
-
Scott Bahling
-
Till Dörges