September 2019 - openSUSE Build Service

[opensuse-buildservice] SLE sources do not appear to generate events on message bus
by James Berry 26 Sep '19

26 Sep '19

No opensuse.obs.package.update messages appear for updates to SUSE:SLE-15- SP2:GA. Presumably this is not so much an OBS issue as much as the way the sync is going outside the normal usage bounds, hence the email instead of issue. Improving the syncing mechanism to generate events would be much appreciated. Tracking issue from our end: https://github.com/openSUSE/openSUSE-release-tools/issues/2239 -- Jimmy -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] Cannot build RHEL packages anymore (package "epel-rpm-macros" suddenly not resolvable)...
by Olsson, Dennis 26 Sep '19

26 Sep '19

Hi There, I have been working on a package for RHEL 7 the last couple of days without any issues. My last successful build was on 24-Sep-2019 18:56. Yesterday, I made some reorganization of my local file system, which meant I had to recheck out my project as well as the package, I was working on, from OBS (using "osc checkout"). Having done that, I was able to make a few local builds without any issues, but when I wanted to make my final build of my package, I suddenly received this error message: $ osc build --local-package Building xscreensaver.spec for Fedora_EPEL_7_RHEL/x86_64 Getting buildinfo from server and store to /data/home/olsde000/devel/ATS/lp3/misc/sources/home:DOlsson/xscreensaver/.osc/_buildinfo-Fedora_EPEL_7_RHEL-x86_64.xml Getting buildconfig from server and store to /data/home/olsde000/devel/ATS/lp3/misc/sources/home:DOlsson/xscreensaver/.osc/_buildconfig-Fedora_EPEL_7_RHEL-x86_64 buildinfo is broken... it says: unresolvable: nothing provides epel-rpm-macros $ I simply do not understand, why I am getting this. When following the repository chain in OBS, I end up with Fedora:EPEL:7/RHEL x86_64 => Fedora:EPEL:7/standard x86_64 => x86_64 https://download.fedoraproject.org/pub/epel/7/x86_64 (rpmmd) where the package "epel-rpm-macros" definitively can be found: https://download.fedoraproject.org/pub/epel/7/x86_64/Packages/e/epel-rpm-ma… So why, all of a sudden, is not OBS capable of resolving this package. As written above, everything had working very nicely up till around 16:00 - 18:00 yesterday 25-Sep-2019, where this error message out of no where turned up. And, no, it does help to try to build the package on OBS either, the same error turns up here. Has any one gotten an idea as to what is going on here and how to solve this problem? Best regards & thanks for your help, Dennis Olsson-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 3

[opensuse-buildservice] Issue with revision in git services
by Dominig ar Foll (Intel Open Source) 25 Sep '19

25 Sep '19

Hello, I try to extract a given review from gerrit with a service file and I get an error that I do not understand My _service points to a pending review. - If I run the service locally with "osc service localrun" it works. - if I run "git clone https://review.opendev.org/starlingx/fault refs/changes/95/684395/5" I get the code * if I run "osc service rr" I get an error "No such revision" Could some one explains me what is wrong ? My test project is at https://build.opensuse.org/package/show/home:dominig:starlingx-sandbox/fm-c… ------------------- _service ------------------------------ <services> <service name="obs_scm"> <param name="scm">git</param> <param name="url">https://review.opendev.org/starlingx/fault</param> <param name="revision">refs/changes/95/684395/5</param> <param name="version">1.0</param> <param name="subdir">fm-common</param> <param name="filename">fm-common</param> <param name="changesgenerate">disable</param> <param name="extract">opensuse/fm-common.spec</param> <param name="extract">opensuse/fm-common.changes</param> </service> <service mode="buildtime" name="tar" /> <service mode="buildtime" name="recompress"> <param name="compression">gz</param> <param name="file">*.tar</param> </service> <service name="set_version" mode="disabled"/> </services> ------------ OBS log --------------- service obs_scm failed: /srv/obs/service/12167 /srv/obs/service/12167/src /srv/obs/service/12167/src/_service /srv/obs/service/12167/src/.old /srv/obs/service/12167/out /srv/obs/service/12167/var /srv/obs/service/12167/var/cache /srv/obs/service/12167/var/cache/obs /srv/obs/service/12167/var/cache/obs/h9UaxI3JJ6e1 /srv/obs/service/12167/var/cache/obs/h9UaxI3JJ6e1/scripts /srv/obs/service/12167/var/cache/obs/h9UaxI3JJ6e1/scripts/inner.sh /srv/obs/service/12167/var/cache/obs/h9UaxI3JJ6e1/scripts/inner.sh.command /srv/obs/service/12167/home + echo Running /usr/lib/obs/service//obs_scm --scm git --url https://review.opendev.org/starlingx/fault --revision refs/changes/95/684395/5 --version 1.0 --subdir fm-common --filename fm-common --changesgenerate disable --extract opensuse/fm-common.spec --extract opensuse/fm-common.changes --outdir /var/cache/obs/h9UaxI3JJ6e1/out + export CACHEDIRECTORY=/var/cache/obs/h9UaxI3JJ6e1/scm-cache + CACHEDIRECTORY=/var/cache/obs/h9UaxI3JJ6e1/scm-cache + export HOME=/var/cache/obs/h9UaxI3JJ6e1/home + HOME=/var/cache/obs/h9UaxI3JJ6e1/home + /usr/lib/obs/service//obs_scm --scm git --url https://review.opendev.org/starlingx/fault --revision refs/changes/95/684395/5 --version 1.0 --subdir fm-common --filename fm-common --changesgenerate disable --extract opensuse/fm-common.spec --extract opensuse/fm-common.changes --outdir /var/cache/obs/h9UaxI3JJ6e1/out Running /usr/lib/obs/service//obs_scm --scm git --url https://review.opendev.org/starlingx/fault --revision refs/changes/95/684395/5 --version 1.0 --subdir fm-common --filename fm-common --changesgenerate disable --extract opensuse/fm-common.spec --extract opensuse/fm-common.changes --outdir /var/cache/obs/h9UaxI3JJ6e1/out refs/changes/95/684395/5: No such revision -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 6

[opensuse-buildservice] Repositories returning 403 - Access Forbidden
by Frederik Carlier 25 Sep '19

25 Sep '19

Hello, In the last hour or so, my home project (at https://download.opensuse.org/repositories/home:/qmfrederik/CentOS_7) started returning 403 - Access Forbidden. I've noticed there was some maintenance on OBS. Are there any steps I need to take to re-enable or refresh my repository, or is this a transient problem? Thanks! Frederik. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] product creation
by Morschhäuser, Mark 25 Sep '19

25 Sep '19

Hi, which way (tool, workflow) is currently recommended to create a product in OBS? The webinterface does not have the editor anymore (which was barely functional anyways), SuSE Studio does not exist anymore, the yast module does not exist anymore, ... and I think it is quite impossible to create something like this https://build.opensuse.org/package/show/openSUSE:Leap:15.1/000product manually... Best regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Publisher not publishing to stageserver on private instance 2.10
by Stefan Botter 20 Sep '19

20 Sep '19

Hi all, I have trouble with my private OBS instance: I have configured a stageserver in BSConfig.pm, as ==== our $stageserver = 'rsync://192.168.22.23/repos'; ==== The target is available and running, but the publisher fails to send the data there. In /srv/obs/log/publisher.log the following error messages are logged: ==== 2019-09-18 15:07:17: [14920] publishing userweb/openSUSE_Leap_15.1 fetched 0 patterns running createrepo running rsync to rsync://192.168.22.23/repos at Wed Sep 18 15:07:18 2019 Use of uninitialized value $args[2] in exec at /usr/lib/obs/server/ bs_publish line 134. rsync version 3.1.3 protocol version 31 Copyright (C) 1996-2018 by Andrew Tridgell, Wayne Davison, and others. [... all the rest of a plain call of "rsync" ...] See http://rsync.samba.org/ for updates, bug reports, and answers rsync error: syntax or usage error (code 1) at options.c(2356) [client=3.1.3] publish failed for userweb/openSUSE_Leap_15.1 : rsync failed at Wed Sep 18 15:09:58 2019: 256 syncing database (6 ops) ==== I am pretty sure, that I did not change the setting for the stageserver in BSConfig.pm for several years now, and, according to logs, it worked until mid-July, when I updated the machine to OBS 2.10. Here my question for help: Did something change in the way staging is configured, and I missed a required configuration change, or is this a bug in the publisher of 2.10? Thank you for your help, Stefan PS: Even scarier question: Am I the only user using a stageserver? -- Stefan Botter zu Hause Bremen

2 2

[opensuse-buildservice] _service <revision> position important ?
by Dominig ar Foll (Intel Open Source) 17 Sep '19

17 Sep '19

Hello, I have lost a bit of time puzzled by my _service refusing to download a given git revision. I finally discover that if the revision if before the version, it does not work but when position after it does. Look like back magic to me. Any explanation of that strange behaviour ? Regards -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Best option to integrate StartlingX CI with OBS
by Dominig ar Foll (Intel Open Source) 16 Sep '19

16 Sep '19

Hello, I have spent a few hours at looking at various options on how best integrate StartlingX CI with OBS for our multiOS subproject. For info, StarlingX is a pilot project of OpenStack. https://www.starlingx.io/ I notice when looking at information on OBS and CI integration published by projects like OpenStack or obs-server that that prefer process seems to be, first build in a branch, followed by a second build in staging. It leads me to a few questions: 1) Why 2 builds ------------------------ What s the value of building of a package in Staging if that was already validated in a Branch ? Is there something that I missed that is possible in Staging but not in a branch ? 2) Managing builds ------------------------------ I do not have the knowledge of a build ID concept on OBS and that make a few things more difficult. I would be interested to understand the best way to work around. After creating my branch and changing the required files, my build can be tracked by osc. osc results -w --xml home:dominig:branches:....... The -w option might not be a good idea as I can see that SSL Error: (104, 'Connection reset by peer') are quite frequent. Is there a better asynchronous way to track the package build success/failure? If multiple changes are triggered in parallel on the same package, I would have a mess with my branches (naming conflict). What would be the best method to avoid serialisation on the test builds in that case ? 3) Cancelling build ------------------------------ It is not uncommon in a CI, that a new patch set is added before that the build result is known. What would be the best way to manage such situation ? Would an "osc restartbuild" on the same branch after source update the right solution ? Any other hints for CI integration would be welcome. -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 6

[opensuse-buildservice] Errors were encountered while processing: raspbian-archive-keyring
by Mark Grant 16 Sep '19

16 Sep '19

I have a simple project which wraps a few apt commands. On my development machine a single set of files; control, rules, dsc, orig and source tar are used to build packages for Debian 9 and 10 and Raspbian 9 and 10 using pbuilder. All packages build successfully. Launchpad also builds from source using the same control and rules files and successfully creates packages. I transfer these file to OBS and packages for Debian and Ubuntu build succesfully, Raspbian 9 and 10 both fail with the same error. The key lines in the OBS build log are:- [ 187s] [201/204] installing raspbian-archive-keyring-20120528.2 [ 187s] /var/lib/dpkg/info/raspbian-archive-keyring.postinst: 8: /var/lib/dpkg/info/raspbian-archive-keyring.postinst: apt-key: not found [ 187s] dpkg: error processing package raspbian-archive-keyring (--install): [ 187s] installed raspbian-archive-keyring package post-installation script subprocess returned error exit status 127 [ 187s] Errors were encountered while processing: [ 187s] raspbian-archive-keyring [ 187s] exit ... Could there be a problem with the raspbian-archive-keyring package at OBS? Any help would be appreciated. Regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Workflow for tuning release field using "obs_admin --set-relsync"
by Srinidhi B 16 Sep '19

16 Sep '19

Hello Everyone, Could someone please explain the exact workflow on how to tune the version-release field of a package using obs_admin --set-relsync? When I change the version-release value for a package in the :relsync file and rebuild the package, my changes are ignored. I know that I can modify build/$prpa/$packid/history and projects/$projid.pkg/$packid.rev file to get the desired affect, but I feel --set-relsync is much easier and script-able way. What do I need to do after running "obs-admin --set-relsync /bs/$prpa/:relsync $packid 'vers-rel'" for the next rebuild of the package to pick up the new 'ver-rel' values? Regards, Srinidhi. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0