November 2018 - openSUSE Build Service

[opensuse-buildservice] Public Key not available SLE_12_SP3 s390x
by Usman Haider 27 Nov '19

27 Nov '19

Hi, I am new and trying local build on s390x with SLE_12_SP3 using the following command sudo osc build but I get the public key not available for many packages. You can see the output by clicking the following link https://pastebin.com/YBQk3vGe I know that I can use --noverify option to bypass this and builds complete successfully when I use --noverify option but how can I fix this? What will happen if I don't fix it? -- Usman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 9

[opensuse-buildservice] OBS Appliance - Unable to Update
by Khalil Graves 15 Apr '19

15 Apr '19

I am running OBS Appliance 2.8.2 on VMware ESX. When the appliance boots I get an error "Failed to start LSB: Finds the storage device to be used for OBS server and/or worker." I have included a dump of systemctl status obsstoagesetup.service below. I Just want to confirm if this is normal or should be addressed. I also attempted and update of a clone of my appliance via zypper but 2 GB root drive is not sufficient for upgrades. Update begins but end with "Error Code: Write Error". I checked root drive and it was up to 100% utilization from 93% prior to update. I decided to install latest version of OBS appliance over existing install. New appliance adopts my old setting but now I am getting and error on boot "Failed to start LSB: open build service source service server." In addition I am unable to build rpms in this current state. Not sure what to do next to get the cloned appliance to build a package. SYSTEMCTL status obsstoragesetup.service obsstoragesetup.service - LSB: Finds the storage device to be used for OBS server and/or worker Loaded: loaded (/etc/init.d/obsstoragesetup; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2018-03-06 18:44:59 UTC; 16min ago Docs: man:systemd-sysv-generator(8) Process: 1365 ExecStart=/etc/init.d/obsstoragesetup start (code=exited, status=1/FAILURE) Mar 06 18:44:59 linux obsstoragesetup[1365]: OBS_SERVER_SIZE=38912 Mar 06 18:44:59 linux obsstoragesetup[1365]: TOTAL_SWAP_SIZE=1024 Mar 06 18:44:59 linux obsstoragesetup[1365]: FINAL_VG_SIZE = 12284 - 38912 - 25600 - 1024 Mar 06 18:44:59 linux obsstoragesetup[1365]: FINAL_VG_SIZE=-53252 Mar 06 18:44:59 linux obsstoragesetup[1365]: OBS_WORKER_ROOT_SIZE=-26626 Mar 06 18:44:59 linux obsstoragesetup[1365]: MIN_WORKER_ROOT_SIZE=4096 Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Control process exited, code=exited status=1 Mar 06 18:44:59 linux systemd[1]: Failed to start LSB: Finds the storage device to be used for OBS server and/or worker. Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Unit entered failed state. Mar 06 18:44:59 linux systemd[1]: obsstoragesetup.service: Failed with result 'exit-code'. SYSTEMCTL status obsservice.service obsservice.service - LSB: open build service source service server Loaded: loaded (/etc/init.d/obsservice; bad; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2018-03-09 11:59:39 UTC; 3min 34s ago Docs: man:systemd-sysv-generator(8) Process: 1761 ExecStart=/etc/init.d/obsservice start (code=exited, status=7) Mar 09 11:59:38 linux systemd[1]: Starting LSB: open build service source service server... Mar 09 11:59:39 linux startproc[1788]: startproc: exit status of parent of /usr/lib/obs/server/bs_service: 13 Mar 09 11:59:39 linux obsservice[1761]: Initializing obsservice..failed Mar 09 11:59:39 linux systemd[1]: obsservice.service: Control process exited, code=exited status=7 Mar 09 11:59:39 linux systemd[1]: Failed to start LSB: open build service source service server. Mar 09 11:59:39 linux systemd[1]: obsservice.service: Unit entered failed state. Mar 09 11:59:39 linux systemd[1]: obsservice.service: Failed with result 'exit-code'. '. -- 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] OBS + GitHub - deprecation of GitHub Services
by Linux Kamarada 19 Mar '19

19 Mar '19

Hello, guys! I searched how to integrate OBS with GitHub so that a git push would cause OBS to fetch the source code and build. I followed directions on these pages: https://openbuildservice.org/2013/11/22/source-update-via_token/ https://github.com/seccubus/obs_autobuild_test (CC their authors, thank you for the great material!) But when I opened GitHub's Integration & services to add the Obs service, I read this: "Note: [GitHub Services are being deprecated][1]. Please contact your integrator for more information on how to migrate or replace a service with [webhooks][2] or [GitHub Apps][3]." [1]: https://developer.github.com/changes/2018-04-25-github-services-deprecation/ [2]: https://developer.github.com/webhooks/ [3]: https://developer.github.com/apps/differences-between-apps/#about-github-ap… The news is from April 25, 2018. The first paragraph summarizes it: "GitHub plans on shutting down GitHub Services so we can shift focus to other areas of the API, such as strengthening GitHub Apps and GraphQL, and improving webhooks. The intention of GitHub Services was to allow third-party developers to submit code for integrating with their services, but this functionality has been superseded by GitHub Apps and webhooks. GitHub Services has not supported new features since April 25, 2016, and we plan to officially deprecate it on October 1st, 2018." Although I successfully integrated OBS with GitHub using a GitHub Service, is it already possible to do that same integration using GitHub Apps or webhooks? Thank you! Antonio The Linux Kamarada Project http://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

7 12

[opensuse-buildservice] "release management chapter in the OBS book"
by Stefan Seyfried 20 Dec '18

20 Dec '18

Good morning. Quote: ------------------------------------------------------------------------------ seife@vbox-seife:~> osc help release release: Release sources and binaries This command is used to transfer sources and binaries without rebuilding them. It requires defined release targets set to trigger="manual". Please refer the release management chapter in the OBS book for details. ------------------------------------------------------------------------------ I'm desperately seeking for the "OBS book" which contains a "release management chapter". Can anyone help me find it? Have fun, seife -- 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

4 4

[opensuse-buildservice] Phantom binaries in openSUSE:Factory:PowerPC/standard/ppc/_repository
by Andreas Schwab 13 Dec '18

13 Dec '18

The repository in openSUSE:Factory:PowerPC/standard/ppc contains a lot of binaries that are not originating from any package build. Especially the python{2,3}-pluggy.rpm binaries are obnoxious because they are overriding the ones built from the python-pluggy package. $ osc api build/openSUSE:Factory:PowerPC/standard/ppc/_repository | grep python.-pluggy <binary filename="python2-pluggy.rpm" size="31706" mtime="1513504048" /> <binary filename="python3-pluggy.rpm" size="31974" mtime="1513504048" /> $ osc api build/openSUSE:Factory:PowerPC/standard/ppc/python-pluggy | grep python.-pluggy <binary filename="python2-pluggy-0.7.1-1.1.noarch.rpm" size="38904" mtime="1538147591" /> <binary filename="python3-pluggy-0.7.1-1.1.noarch.rpm" size="39604" mtime="1538147591" /> When I disable useforbuild in the python-pluggy package the phantom binaries disapper, and reenabling useforbuild brings the correct binaries into the repository. But after some time the phantom binaries reappear. Other than that there are about 150 phantom binaries in the repository. Andreas. -- Andreas Schwab, SUSE Labs, schwab(a)suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 1

[opensuse-buildservice] python UnicodeDecodeError errors in _service files
by Olaf Hering 29 Nov '18

29 Nov '18

What is causing this error? home:olh:xen-4.5/libvirt $ osc r -v openSUSE_Tumbleweed x86_64 broken: home:olh:xen-buildrequires/libvirt-4.1.0: service error: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 44: ordinal not in range(128) I could not spot a byte '0xe2' in the sources. Olaf

3 4

[opensuse-buildservice] change of docker image filenames
by Olaf Hering 28 Nov '18

28 Nov '18

In the past days, or perhaps weeks, the name of docker images changed. It used to be 'foo.tar' in the 'osc ls -lbv' output, now it is 'foo.x86_64.<release>.tar' How can I restore old behavior which provided predictable filenames? I think it was controlled via '#!BuildTag:' in the Dockerfile. Olaf

2 6

[opensuse-buildservice] Qactus 1.0 is out!
by Javier Llorente 26 Nov '18

26 Nov '18

Hello everyone, Qactus 1.0 has been released! This version comes with an OBS browser for exploring/maintaining projects and packages B-) Changes in a nutshell: - New: build log viewer - Improved request state editor - Split GUI code; libqobs is born - Bugs fixed, several small enhancements http://www.javierllorente.com/2018/11/25/qactus-1-0-is-out/ Greetings, Javier -- Javier Llorente

2 3

[opensuse-buildservice] Publishing delays
by Roger Oberholtzer 26 Nov '18

26 Nov '18

I see that publishing to openSUSE_Leap_15.0 is working fine. However, publishing to openSUSE_Leap_42.3 and openSUSE_Tumbleweed seems stuck for a couple of days now. At least of the builds I am doing. Like https://build.opensuse.org/package/show/home:rogeroberholtzer/laszip Anyone else see this? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] lmms in multimedia:apps
by Edgar Aichinger 22 Nov '18

22 Nov '18

Hello, around two weeks ago i submitted an update of lmms (latest release 1.2.0-rc7) to mm:apps, which after some more tweaks got accepted. Now I see from the OBS webui that lmms in mm:apps successfully built and published for Leap 15.0 and Tumbleweed, but my TW laptop using the new official snapshot system, with mm:apps as additional package source, doesn't provide it, for some reason lmms doesn't have arrived in the download area. Can someone have a look please? Thanks, Edgar -- 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] unreliable gwdg.de mirror
by Olaf Hering 21 Nov '18

21 Nov '18

Since about a week gwdg.de is unreliable as a mirror. At least for me it always aborts a zypper dup with ssl errors. Can we disable this mirror please until it is properly fixed? * Issue another request to this URL: 'https://ftp.gwdg.de/pub/opensuse/repositories/home:/olh:/xen-buildrequires/…' * Hostname was NOT found in DNS cache * Trying 2001:638:60f:110::1:2... * Connected to ftp.gwdg.de (2001:638:60f:110::1:2) port 443 (#1) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs/ * SSLv3, TLS unknown, Certificate Status (22): } [data not shown] * SSLv3, TLS handshake, Client hello (1): } [data not shown] * SSLv3, TLS handshake, Server hello (2): { [data not shown] * SSLv3, TLS handshake, Certificate (11): { [data not shown] * SSLv3, TLS alert, Server hello (2): } [data not shown] * SSL certificate problem: unable to get local issuer certificate 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 * Closing connection 1 curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. Olaf

4 5

[opensuse-buildservice] Question related to testcases for an MySQL based software
by Johannes Weberhofer 19 Nov '18

19 Nov '18

Dear all! Is there a possibility to start an (empty) mysql server within a build instance to run several test cases while building a package? Best regards -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- 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] Error 400 during "osc submitrequest" with a revision for the source package
by Johannes Kastl 17 Nov '18

17 Nov '18

Hi all, maybe I am misunderstanding the help for "osc submitrequest", but I thought one could create a submitrequest for an older revision of the source package, so I can submit a state older than what is currently the latest version (of the package that is to be submitted). But regardless of how I specify the revision (r7, 7, the md5sum from "osc log", ...), I always get the following error: Server returned an error: HTTP Error 400: Bad Request The source of package home:ojkastl_buildservice:Branch_Virtualization_vagrant/vagrant for revision r7 is broken Submitting without the "-r" option works fine. I also issued several "osc up" commands, checked out the different revisions via "osc up -r 7", all worked flawlessly). Known issues? PEBKAC? Misunderstanding? Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl(a)b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

2 2

[opensuse-buildservice] cmake and MS Windows builds
by Roger Oberholtzer 16 Nov '18

16 Nov '18

Curious that there is no cmake for the Mingw build system on OBS. Is this because building cmake requires a pre-installed binary of cmake. A chicken and egg thing? How might one best accomplish that on OBS? -- Roger Oberholtzer -- 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] Simple mail notification in OBS
by Christof Hanke 14 Nov '18

14 Nov '18

Hi, I wanted to ask what's the simplest way to implement an email-only notifcation from a private OBS-instance. (for faild builds etc.) Up to now, I've used a self-written plugin, which stopped working a while ago. So I'm wondering if it's worth fixing or if this can be done differently without install hermes. Many thanks, Christof -- 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] no progress since yesterday evening (CET)
by Hans-Peter Jansen 11 Nov '18

11 Nov '18

Hi, it looks, like OBS doesn't make any progress since yesterday evening. The plots at https://build.opensuse.org/monitor end at 23:00, but https://status.opensuse.org doesn't indicate any issues. I see packages, that keep in finished state since 16 hours, although they didn't produce a different result, hence no further processing should be required, e.g.: https://build.opensuse.org/package/live_build_log/home:frispete:telephony:a… That isn't usual OBS behavior. Any ideas, what's up with OBS ATM? Thanks, 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] Re: ghostscript + gv / epstopdf problems after recent update
by Masaru Nomiya 10 Nov '18

10 Nov '18

Hello, In the Message; Subject : [opensuse] Re: ghostscript + gv / epstopdf problems after recent update Message-ID : <87in193b08.wl-nomiya(a)galaxy.dti.ne.jp> Date & Time: Wed, 07 Nov 2018 10:57:27 +0900 Masaru Nomiya <nomiya(a)galaxy.dti.ne.jp> has written: [...] DCR> It would be nice if you posted a link to the bugzilla bug so DCR> those interested could follow the progress and add any DCR> additional information they may have. > Here, it is. > https://bugzilla.novell.com/show_bug.cgi?id=1108027 I've got no response from maintainer, so I convinced misposting my bug report. I reposted it again 3 day ago; https://bugzilla.novell.com/show_bug.cgi?id=1115126&GoAheadAndLogIn=1 BTW, I received the ghostscript-9.26 rc1's release announce mail last night. I got it, and checked source files. I confirmed the important security fixes were applied. So, I made ghostscript-9.26rc1-1.1.arc.rpm & bult & installed. As expected, It works fine. But, no response until now. So, I checked my bug report's status. I found the response; Johannes Meixner 2018-11-09 13:18:23 UTC Cf. https://ghostscript.com/pipermail/gs-devel/2018-November/010126.html and https://ghostscript.com/pipermail/gs-devel/2018-November/010127.html This reply means, in short, 'Wait or Use ghostscript 9.26rc1'. Which on? > Johannes Meinxner In fact, the ghostscript-9.26rc1 is not places within the update repository, now. That is, he won't release the bug fixed ghostscript 9.25! Od cource, I DID claim. Thanks, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computers. Not with Me!" "No..., with money." -- 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] Caching interconnect requests for when interconnect is down?
by Neal Gompa 07 Nov '18

07 Nov '18

Hey, Is there a way to make it so that build service instances that interconnect to api.opensuse.org cache the configurations so that in the event the server is down, builds can keep going, using cached configurations and binary packages that cached locally on the build service? I'd like to avoid issues similar to what happened earlier in the year and last year when the API was down and caused `osc build` runs to fail, as well as builds on the build service instance itself to fail due to inability to get configurations from the API, while still maintaining the interconnect because I don't want to fork all the build configurations and content and import them into my instance. If that's not possible for OBS 2.9, what can we do to make this work for OBS 2.10? -- 真実はいつも一つ！/ Always, there's only one truth! -- 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] Login timeout OBS
by Eric Schirra 02 Nov '18

02 Nov '18

Hello, since some days, weeks, again and again the login brings timeout. Currently too. What is the problem since some days? Regards Eric -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1