openSUSE Build Service November 2018

buildservice@lists.opensuse.org

22 participants
19 discussions

[opensuse-buildservice] Public Key not available SLE_12_SP3 s390x

by Usman Haider

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

1 year, 5 months

[opensuse-buildservice] OBS Appliance - Unable to Update

by Khalil Graves

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 years

[opensuse-buildservice] OBS + GitHub - deprecation of GitHub Services

by Linux Kamarada

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

2 years, 1 month

[opensuse-buildservice] "release management chapter in the OBS book"

by Stefan Seyfried

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

2 years, 4 months

[opensuse-buildservice] Phantom binaries in openSUSE:Factory:PowerPC/standard/ppc/_repository

by Andreas Schwab

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

2 years, 5 months

[opensuse-buildservice] python UnicodeDecodeError errors in _service files

by Olaf Hering

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

2 years, 5 months

[opensuse-buildservice] change of docker image filenames

by Olaf Hering

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 years, 5 months

[opensuse-buildservice] Qactus 1.0 is out!

by Javier Llorente

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 years, 5 months

[opensuse-buildservice] Publishing delays

by Roger Oberholtzer

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

2 years, 5 months

[opensuse-buildservice] lmms in multimedia:apps

by Edgar Aichinger

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 years, 5 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service November 2018