[opensuse-buildservice] Building OBS 2.9 in own OBS issues
Hi, yesterday I tried to import and build the OBS:Server:2.9 project in my private OBS 2.8 instance and found some issues. Import was done with osc copypac, build was tried for SLE12 SP3. 1.) package build failed to extract some spec/changes files (build-mkbaselibs-sle stuff), seems that was removed some time after the _service was written and last service run. Solution for me, I added <param name="version">20180111</param> <param name="revision">4db855ee8d1b81ac46c4b54a41724de587782bb4</param> to the _service to get the same version as used in the official build. 2.) Lot of ruby gems did stay unresolved because of ruby > 2.2.2 build requirements. Hmm, looked at the project config, but it was empty and indeed SLE12 SP3 prefers ruby2.1. Seems somebody did delete the project config after building the stable release (Is this normal ?). Solution for me: using the project config from the OBS:Server:2.9:Staging project. After this everything did build. Another issue was building openSUSE:Tools, the service file of obs-service-generator_pom points to a dead link, so it stays broken, maybe somebody can fix it, I did download the the service result and removed the _service file. Thanks Karsten -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 06/01/2018 10:13 AM, Karsten Keil wrote:
Hi,
yesterday I tried to import and build the OBS:Server:2.9 project in my private OBS 2.8 instance and found some issues. Import was done with osc copypac, build was tried for SLE12 SP3.
1.) package build failed to extract some spec/changes files (build-mkbaselibs-sle stuff), seems that was removed some time after the _service was written and last service run. Solution for me, I added <param name="version">20180111</param> <param name="revision">4db855ee8d1b81ac46c4b54a41724de587782bb4</param> to the _service to get the same version as used in the official build.
2.) Lot of ruby gems did stay unresolved because of ruby > 2.2.2 build requirements. Hmm, looked at the project config, but it was empty and indeed SLE12 SP3 prefers ruby2.1. Seems somebody did delete the project config after building the stable release (Is this normal ?). Solution for me: using the project config from the OBS:Server:2.9:Staging project. After this everything did build.
The OBS:Server:2.9 project is just the release target of OBS:Server:2.9:Staging. Once we tested a new release in *:Staging we release the binaries to OBS:Server:2.9. Hence we don't need the project config there.
Another issue was building openSUSE:Tools, the service file of obs-service-generator_pom points to a dead link, so it stays broken, maybe somebody can fix it, I did download the the service result and removed the _service file.
Thanks Karsten
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi, Am 01.06.2018 um 12:33 schrieb Bjoern Geuken:
On 06/01/2018 10:13 AM, Karsten Keil wrote:
Hi,
yesterday I tried to import and build the OBS:Server:2.9 project in my private OBS 2.8 instance and found some issues. Import was done with osc copypac, build was tried for SLE12 SP3.
1.) package build failed to extract some spec/changes files (build-mkbaselibs-sle stuff), seems that was removed some time after the _service was written and last service run. Solution for me, I added <param name="version">20180111</param> <param name="revision">4db855ee8d1b81ac46c4b54a41724de587782bb4</param> to the _service to get the same version as used in the official build.
2.) Lot of ruby gems did stay unresolved because of ruby > 2.2.2 build requirements. Hmm, looked at the project config, but it was empty and indeed SLE12 SP3 prefers ruby2.1. Seems somebody did delete the project config after building the stable release (Is this normal ?). Solution for me: using the project config from the OBS:Server:2.9:Staging project. After this everything did build.
The OBS:Server:2.9 project is just the release target of OBS:Server:2.9:Staging. Once we tested a new release in *:Staging we release the binaries to OBS:Server:2.9. Hence we don't need the project config there.
OK, understand - new concept for me. I looked only in the OBS:Server:2.9 meta for some references to the Staging project, not in the staging project it self. How do you trigger a release ? Do here be any documentation of this concept/feature ?
Another issue was building openSUSE:Tools, the service file of obs-service-generator_pom points to a dead link, so it stays broken, maybe somebody can fix it, I did download the the service result and removed the _service file.
Thanks Karsten
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 06/01/2018 03:57 PM, Karsten Keil wrote:
Hi,
Am 01.06.2018 um 12:33 schrieb Bjoern Geuken:
On 06/01/2018 10:13 AM, Karsten Keil wrote:
Hi,
yesterday I tried to import and build the OBS:Server:2.9 project in my private OBS 2.8 instance and found some issues. Import was done with osc copypac, build was tried for SLE12 SP3.
1.) package build failed to extract some spec/changes files (build-mkbaselibs-sle stuff), seems that was removed some time after the _service was written and last service run. Solution for me, I added <param name="version">20180111</param> <param name="revision">4db855ee8d1b81ac46c4b54a41724de587782bb4</param> to the _service to get the same version as used in the official build.
2.) Lot of ruby gems did stay unresolved because of ruby > 2.2.2 build requirements. Hmm, looked at the project config, but it was empty and indeed SLE12 SP3 prefers ruby2.1. Seems somebody did delete the project config after building the stable release (Is this normal ?). Solution for me: using the project config from the OBS:Server:2.9:Staging project. After this everything did build.
The OBS:Server:2.9 project is just the release target of OBS:Server:2.9:Staging. Once we tested a new release in *:Staging we release the binaries to OBS:Server:2.9. Hence we don't need the project config there.
OK, understand - new concept for me. I looked only in the OBS:Server:2.9 meta for some references to the Staging project, not in the staging project it self. How do you trigger a release ? Do here be any documentation of this concept/feature ?
We have a brief overview of the setup in our development documentation: https://github.com/openSUSE/open-build-service/wiki/Overview-of-OBS:Server:2... Let us know if there is anything missing that you would like to add there. I'll add a link to this page to the OBS:Server:2.9 project.
Another issue was building openSUSE:Tools, the service file of obs-service-generator_pom points to a dead link, so it stays broken, maybe somebody can fix it, I did download the the service result and removed the _service file.
Thanks Karsten
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 06/04/2018 08:59 AM, Bjoern Geuken wrote:
On 06/01/2018 03:57 PM, Karsten Keil wrote:
Hi,
Am 01.06.2018 um 12:33 schrieb Bjoern Geuken:
On 06/01/2018 10:13 AM, Karsten Keil wrote:
Hi,
yesterday I tried to import and build the OBS:Server:2.9 project in my private OBS 2.8 instance and found some issues. Import was done with osc copypac, build was tried for SLE12 SP3.
1.) package build failed to extract some spec/changes files (build-mkbaselibs-sle stuff), seems that was removed some time after the _service was written and last service run. Solution for me, I added <param name="version">20180111</param> <param name="revision">4db855ee8d1b81ac46c4b54a41724de587782bb4</param> to the _service to get the same version as used in the official build.
2.) Lot of ruby gems did stay unresolved because of ruby > 2.2.2 build requirements. Hmm, looked at the project config, but it was empty and indeed SLE12 SP3 prefers ruby2.1. Seems somebody did delete the project config after building the stable release (Is this normal ?). Solution for me: using the project config from the OBS:Server:2.9:Staging project. After this everything did build.
The OBS:Server:2.9 project is just the release target of OBS:Server:2.9:Staging. Once we tested a new release in *:Staging we release the binaries to OBS:Server:2.9. Hence we don't need the project config there.
OK, understand - new concept for me. I looked only in the OBS:Server:2.9 meta for some references to the Staging project, not in the staging project it self. How do you trigger a release ? Do here be any documentation of this concept/feature ?
We have a brief overview of the setup in our development documentation: https://github.com/openSUSE/open-build-service/wiki/Overview-of-OBS:Server:2...
It's https://github.com/openSUSE/open-build-service/wiki/Overview-of-OBS%3AServer... now. I just changed the headline to make the url static. Sorry
Let us know if there is anything missing that you would like to add there. I'll add a link to this page to the OBS:Server:2.9 project.
Another issue was building openSUSE:Tools, the service file of obs-service-generator_pom points to a dead link, so it stays broken, maybe somebody can fix it, I did download the the service result and removed the _service file.
Thanks Karsten
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Montag, 4. Juni 2018, 09:04:28 CEST wrote Bjoern Geuken:
On 06/04/2018 08:59 AM, Bjoern Geuken wrote:
On 06/01/2018 03:57 PM, Karsten Keil wrote:
Hi,
Am 01.06.2018 um 12:33 schrieb Bjoern Geuken:
On 06/01/2018 10:13 AM, Karsten Keil wrote:
Hi,
yesterday I tried to import and build the OBS:Server:2.9 project in my private OBS 2.8 instance and found some issues. Import was done with osc copypac, build was tried for SLE12 SP3.
1.) package build failed to extract some spec/changes files (build-mkbaselibs-sle stuff), seems that was removed some time after the _service was written and last service run. Solution for me, I added <param name="version">20180111</param> <param name="revision">4db855ee8d1b81ac46c4b54a41724de587782bb4</param> to the _service to get the same version as used in the official build.
2.) Lot of ruby gems did stay unresolved because of ruby > 2.2.2 build requirements. Hmm, looked at the project config, but it was empty and indeed SLE12 SP3 prefers ruby2.1. Seems somebody did delete the project config after building the stable release (Is this normal ?). Solution for me: using the project config from the OBS:Server:2.9:Staging project. After this everything did build.
The OBS:Server:2.9 project is just the release target of OBS:Server:2.9:Staging. Once we tested a new release in *:Staging we release the binaries to OBS:Server:2.9. Hence we don't need the project config there.
actually we should have the working prject config there and just test changes in :Staging IMHO. -- 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
Hey, On 01.06.2018 15:57, Karsten Keil wrote:
OK, understand - new concept for me.
This is part of the maintenance workflow. You can find a chapter about it here: https://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.mainte... Henne -- Henne Vogelsang http://www.opensuse.org Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Montag, 4. Juni 2018, 16:45:31 CEST wrote Henne Vogelsang:
Hey,
On 01.06.2018 15:57, Karsten Keil wrote:
OK, understand - new concept for me.
This is part of the maintenance workflow. You can find a chapter about it here:
https://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.mainte...
no, it is not part of the maintenance workflow, that would work with incidents and requests. It is just a manual release via "osc release" command -- 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 (4)
-
Adrian Schröter -
Bjoern Geuken -
Henne Vogelsang -
Karsten Keil