June 2018 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] obs service github_tarballs
by Christian 28 Jun '18

28 Jun '18

Hello, I need your help with this _Service cause I want to get an automatic rebuild after creating a new 'tag' in github. On my research I stumbled over 'github_tarballs' Service which seems the one to be used for this. sadly there is not much documentation on how to use it ... ... used info from here: https://openbuildservice.org/2013/11/22/source-update-via_token ... so I took the sample from 'github code' ... <services> <service name="obs_scm"> <param name="url">git://github.com/openSUSE/obs-build.git</param> <param name="scm">git</param> </service> <service mode="buildtime" name="tar" /> <service mode="buildtime" name="recompress"> <param name="file">*.tar</param> <param name="compression">xz</param> </service> <service mode="buildtime" name="set_version" /> <service name="github_tarballs"> <summary>Download tarballs and update package data</summary> <description>This service downloads tarballs and updates the spec file version and changes file</description> <param name="url"> <description>https://github.x.y.z/user/mpremoval/archive/1.0.tar.gz</description> <required/> </param> <param name="package"> <description>mpremoval</description> </param> <param name="filename"> <description>mpremoval</description> </param> <param name="email"> <description>user(a)internal.mail</description> <required/> </param> <param name="repo_owner"> <description>user</description> <required/> </param> <param name="repo_name"> <description>mpremoval</description> <required/> </param> <param name="target"> <description>tokencode(removed)</description> <required/> </param> </service> </services> ...but then I am running into the following Error when trying to do a local build ... Server returned an error: HTTP Error 400: Bad Request remote error: unknown element summary seems that the 'service' section for 'github_tarballs' is not correct. Or I am doing something completely wrong. So any help on how to get this work would be really appreciated. Thank you for your help ... Kind Regards Chris P.S.: the package 'obs-service-github_tarballs' is installed is installed on the OBS instance. both, github and obs are own instances ....

5 17

[opensuse-buildservice] Release tagging
by Mitya Ivanov 27 Jun '18

27 Jun '18

Hi friends! I have a couple of packages in a project to build and i want to set their release tags according to those specified in .spec files. Is it possible to do this instead of define common "Release:" tag in prjconf? -- 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] spurious builds from source change, that didn't happen
by Hans-Peter Jansen 26 Jun '18

26 Jun '18

Hi *, today, I observed a spurious build of a package because of a source change, that didn't happen (at least not consciously): https://build.opensuse.org/packages/gcc/build_reason/home:frispete:gcc/open… Timestamp of gcc.spec is changed today, but I did something completely different at that time. Last time, I touched it was 17 days ago (revision 7): https://build.opensuse.org/package/revisions/home:frispete:gcc/gcc Package links to https://build.opensuse.org/package/show/openSUSE:Factory/gcc, but that gcc.spec also hasn't changed since the last 7 days. osc diff with a local copy doesn't show any changes as well. Question is, what triggered the timestamp change of gcc.spec? Needless to say, a spurious build of such a package is snowballing builds in all depending projects for no good reason. I feel the need to say sorry for the wasted resources. Sorry, Pete -- 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] Package groups
by Morschhäuser, Mark 26 Jun '18

26 Jun '18

Hi, currently I need to simplify the installation of about 100 packages with many inter-dependencies. As rpm and rpm-based installers sometimes install in a very disadvantageous order and I was unable to cover that via package requirements*), I created meta packages which are to be installed in a certain order to setup the software. A disadvantage is that I cannot uninstall all these packages easily that are installed by meta-packages. Now I saw that RHEL based systems have the option to make use of package groups which are defined in comps.xml files in the repository metadata [1] and I know that SuSE based systems allow to use patterns (and both are my target platforms) I would like to read a comparison between meta packages, package groups, patterns and distribution compatibility and if/how it is possible to create package groups/patterns with OBS. Does someone have more information about that topic or can show me examples on build.opensuse? It seems I am googling the wrong questions :-) Best regards, Mark [1] https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_gr… *) Example: Some packages have an absolute requirement that another package was installed completely before, including all pre, post and other phases; if zypper/yum/rpm install the packages together, anything could happen - e.g. alphabetical order or whatever; a simple Requires does not help and Requires(pre) does not help either. -- 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] Keys missing for Fedora 25/26/27 and Rawhide
by Johannes Kastl 24 Jun '18

24 Jun '18

Hi guys, can it be that the public keys for Fedora 25/26/27 and Rawhide are not setup correctly on the OBS? I get "public key not available" errors when building locally. Not sure if this is a local issue or to be fixed on the OBS, because I find mails stating both... Kind Regards, Johannes

6 10

[opensuse-buildservice] Unresolvable build status of package
by Vladimir Voinovich 22 Jun '18

22 Jun '18

Hello. I have private instance of OBS v2.9 for building some CentOS packages for testing. I use CentOS repo from build.opensuse.org as build target: .. <path project="openSUSE.org:CentOS:CentOS-7" repository="standard"/> .. I also copied prjconf from that project. The problem is that im not able to build some packages that i import from srpm's. Srpm's are from http://vault.centos.org/7.5.1804/os/Source/SPackages/ Some builds fine, some not. For example shim-signed-12-1.el7.centos.src.rpm. It's status is unresolvable(nothing provides shim-unsigned-x64 = 12-1.el7, nothing provides shim-unsigned-ia32 = 12-1.el7) But target repo clearly has this packages. Also i was trying to setup local DoD repo, but result was the same. What i'm doing wrong? Any help would be appreciated! Thanks! -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 4

[opensuse-buildservice] mangling shebang in fedora 28
by Petr Vanek 21 Jun '18

21 Jun '18

hi, is there any way how to disable 'shebang mangling' in Fedora 28, please? An example: [ 128s] mangling shebang in /opt/qorus/bin/qldapdelete from /usr/bin/env qore to #!/usr/bin/qore I know it's ugly etc. But I'm preparing some app which needs to use env for selecting the proper interpret. Or should I patch all scripts to use hardcoded shebangs paths in the package itself? thanks, Petr -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] Problems after update to 2.9.2
by Keil, Karsten 21 Jun '18

21 Jun '18

Hi, begin of this week I updated our private instance of OBS from 2.8.4 to 2.9.2. First tests did not show any issues, builds were running just fine. But after adding a new worker (no package cache !) we get build errors, in the build log we see that getbinaries did fail for the basic system packages (but the files are available and the packages do not have any unresolved state. In the repo server log I see the GET /getbinaries request and then a POST with failed status, nothing more. With Wireshark I saw that the answer for the /getbinaries request do contain info with "file is a symlink". Our base OS repositories are created from loop mounted Product DVDs or a local SMT copy, all packages are sym linked to the :full/ directory of the project, since we are in a fully isolated network. This setup did work without any issues for some years until now and I know some other private installations which use a similar bootstrapping method for the basic repositories. Digging a little bit deeper in the repo server backend code, I found that some special handling for symlinks was introduced In the BSHTTP::cpio_sender function and that the function has some support do follow symlinks, but this was not enabled in the calling function BSServer::reply_cpio, adding 'follow' => 1 as parameter to the call of BSHTTP::cpio_sender seems to fix this problem for me. Questions: Is this valid as fix for now ? Is this a bug or is here some reason to forbid following symlinks ? Thanks Karsten The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] bs_srcserver seems stuck at a specific lastnotification number
by Stefan Seyfried 20 Jun '18

20 Jun '18

Hi, I was investigating why my OBS server has a considerable amount of CPU load all the time. It's bs_srcserver that occupies one CPU almost entirely. Investigating, it looks like it is processing the /srv/obs/events/lastnotifications over and over again. obs:~ # grep lastnotifications /srv/obs/log/src_server.log|tail 2018-06-19 15:21:17: [2007] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-06-19 15:21:20: [2011] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-06-19 15:21:23: [2014] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-06-19 15:21:27: [2018] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-06-19 15:21:30: [2022] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-06-19 15:21:33: [2024] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-06-19 15:21:36: [2030] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-06-19 15:21:39: [2040] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-06-19 15:21:43: [2048] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-06-19 15:21:46: [2052] GET (127.0.0.1) /lastnotifications?start=297709&block=1 Actually, the oldest copy I have of this logfile is from 2018-05-01, and it has the same start= number: obs:~ # xzgrep lastnotifications /srv/obs/log/src_server.log-20180501.xz|head -5 2018-04-30 08:45:09: [30828] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-04-30 08:45:11: [30833] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-04-30 08:45:14: [30837] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-04-30 08:45:17: [30841] GET (127.0.0.1) /lastnotifications?start=297709&block=1 2018-04-30 08:45:19: [30843] GET (127.0.0.1) /lastnotifications?start=297709&block=1 obs:~ # l /srv/obs/events/ total 26832 drwxr-xr-x 9 obsrun obsrun 4096 Jun 4 12:37 ./ drwxr-xr-x 23 obsrun obsrun 4096 Sep 28 2017 ../ drwxr-xr-x 2 obsrun obsrun 4096 Jun 12 08:21 deltastore/ drwxr-xr-x 2 obsrun obsrun 4096 Jun 19 11:07 dispatch/ drwxr-xr-x 2 obsrun obsrun 905216 Jun 19 11:16 i586/ -rw-r--r-- 1 obsrun obsrun 520080 Jun 19 15:11 lastevents -rw-r--r-- 1 obsrun obsrun 25804967 Jun 19 14:22 lastnotifications drwxr-xr-x 2 obsrun obsrun 4096 Jun 19 14:22 publish/ drwxr-xr-x 2 obsrun obsrun 4096 Jun 19 15:11 repository/ drwxr-xr-x 2 obsrun obsrun 8192 Jun 19 14:21 signer/ drwxr-xr-x 2 obsrun obsrun 90112 Jun 19 14:22 x86_64/ note that I have no i586 scheduler anymore (had it before, but finally got rid of it maybe a year ago). The i586 events directory is full of files named after projects obs:~ # l /srv/obs/events/i586/|wc 1557 14006 141552 Most of these are old (older than 2017-08-24, maybe the date I got rid of the i586 scheduler), but two were updated today: vsa1001:~ # ls -l /srv/obs/events/i586/ -rt|tail -2 -rw-r--r-- 1 obsrun obsrun 122 Jun 19 10:46 relsync:Images:SaaS:BM::images::i586 -rw-r--r-- 1 obsrun obsrun 122 Jun 19 11:16 relsync:Images:SaaS:HV::images::i586 I have no real idea how this all plays together, and what I have to do to get this into a sane state again. Any hints? Best regards, and thanks in advance, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 3

[opensuse-buildservice] result of Substitute is ignored
by Olaf Hering 19 Jun '18

19 Jun '18

At which point during building is a Substitute supposed to be used? I have a 'Substitute: pkgconfig(pkg) pkg-devel=' in prjconf. The trailing '=' is supposed to carry the version during substitution. The buildlog shows that BuildRequires is properly updated, but the result is apparently not used when preparing the build. In my case I expect state 'unresolvable' because the expected version is not available in the target repository. As a result the pkg starts to build, then rpmbuild fails: ... [ 39s] [112/251] installing python-devel-2.6.9-6.SLE_11.1 ... [ 83s] < BuildRequires: pkgconfig(python2) >= 2.7 [ 83s] > BuildRequires: python-devel >= 2.7 ... [ 83s] error: Failed build dependencies: [ 83s] python-devel >= 2.7 is needed by ${pkg} ... I think such "Substitute" used to bring a pkg in state 'unresolvalbe' in the past. Olaf

1 0