openSUSE Build Service August 2018

buildservice@lists.opensuse.org

27 participants
30 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] Container rebuild trigger on included packages and registry multiple tags

by Jimmy Berry

Two questions: - Is it possible to have a container rebuild whenever the underlying packages are updated (ie. any package included in the container) even if the packages are in underlying repo path elements and not the project with the container? - Is it possible to publish multiple tags to the opensues registry? Using additionaltags on containerconfig element in kiwi file they are supposedly set, but only tag ends up in the registry. - Related is it possible to keep older revisions (a couple) or "pin" certain tags and keep those until unpinned? Having only a single version of a container is not ideal as it makes it impossible to roll-back to previous version. Project in question: home:jberry:container/osrt-worker-obs. As a note the prjconf necessary to build containers is not terribly visible, intuitive, or documented. -- Jimmy -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 7 months

[opensuse-buildservice] Ubuntu 18.04 packages under OBS 2.8.2 fail

by Ralf Becker

I try building packages for Ubuntu 18.04 on our (private) OBS 2.8.2 instance: [ 0s] Using BUILD_ROOT=/var/cache/obs/worker/root_4/.mount [ 0s] Using BUILD_ARCH=x86_64:i686:i586:i486:i386 [ 0s] Doing kvm build in /var/cache/obs/worker/root_4/root [ 0s] [ 0s] [ 0s] linux started "build egroupware-epl-archive.dsc" at Fri Aug 31 08:04:54 UTC 2018. [ 0s] [ 0s] Building egroupware-epl-archive-17.1 for project 'stylite-epl' repository 'xUbuntu_18.04' arch 'x86_64' srcmd5 'a2b3574b64329975a304462648e95eb5' [ 0s] [ 0s] processing recipe /var/cache/obs/worker/root_4/.build-srcdir/egroupware-epl-archive.dsc ... [ 0s] running changelog2spec --target debian --file /var/cache/obs/worker/root_4/.build-srcdir/egroupware-epl-archive.dsc [ 0s] init_buildsystem --configdir /var/run/obs/worker/4/build/configs --cachedir /var/cache/build --prepare --clean --rpmlist /var/cache/obs/worker/root_4/.build.rpmlist /var/cache/obs/worker/root_4/.build-srcdir/egroupware-epl-archive.dsc build rpmlint-Factory ... [ 1s] /var/cache/obs/worker/root_4/.mount/.init_b_cache/rpms/bash.deb: control.tar.gz is not second ar entry [ 1s] bad binary: bash.deb [ 1s] [ 1s] /var/cache/obs/worker/root_4/.mount/.init_b_cache/rpms/binutils.deb: control.tar.gz is not second ar entry [ 1s] bad binary: binutils.deb [ 1s] exit ... [ 1s] [ 1s] linux failed "build egroupware-epl-archive.dsc" at Fri Aug 31 08:04:55 UTC 2018. [ 1s] Other targets like Ubuntu 16.04 work as expected and have identical configuration: <repository name="xUbuntu_18.04"> <path project="openSUSE.org:Ubuntu:18.04" repository="standard"/> <path project="openSUSE.org:Ubuntu:18.04" repository="universe"/> <arch>i586</arch> <arch>x86_64</arch> </repository> <repository name="xUbuntu_16.04"> <path project="openSUSE.org:Ubuntu:16.04" repository="standard"/> <path project="openSUSE.org:Ubuntu:16.04" repository="universe"/> <arch>i586</arch> <arch>x86_64</arch> </repository> Any ideas? Do I need to update OBS 2.8.2 to build Ubuntu 18.04 packages? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

2 years, 8 months

[opensuse-buildservice] Is it possible to build from src.rpm instead of tar-ball?

by Andreas Vetter

Hi, is there a way to use a src.rpm instead of a tar-ball for building a package? If yes: Is there a way to use the spec-file from within the src.rpm? TIA, Andreas -- Mit freundlichen Gruessen, Andreas Vetter Stellv. IT-Bereichsmanager Fakultaet fuer Physik und Astronomie Tel.: +49 (0)931 31-82264 Informations- und Kommunikationstechnik Tel: +49 (0)931 31-85890 iuk(a)physik.uni-wuerzburg.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 8 months

[opensuse-buildservice] Mageia Cauldron (i586): libicu59 not found

by BJH2017

Hi, My Mageia Cauldron i586 builds are in the 'unresolvable' status due to: nothing provides libicu59 Is this an upstream issue, or something the maintainers of the OBS can do something about? Thanks for your time, Brenton -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 8 months

[opensuse-buildservice] Unable to BR gcc7 from SLE_12_SP3?

by Neal Gompa

Hey, I'm trying to build a package in my private OBS instance using gcc7 on SLE 12 SP3 and openSUSE Leap 42.3. It is able to resolve the dependency for openSUSE Leap 42.3, but fails with SLE 12 SP3. I get the following error from OBS: nothing provides gcc7 nothing provides gcc7-c++ However, I see it listed in SLE 12 SP3: https://build.opensuse.org/package/show/SUSE:SLE-12-SP3:GA/gcc7 My meta snippet is set to the following: <repository name="SLE_12_SP3"> <path project="openSUSE.org:SUSE:SLE-12-SP3:GA" repository="standard"/> <arch>x86_64</arch> </repository> What am I doing wrong? -- 真実はいつも一つ！/ 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 years, 8 months

[opensuse-buildservice] Search settings GUI issue

by Jeroen Ooms

The "Download package" link on my project OBS project page links to: https://software.opensuse.org//download.html?project=home%3Ajeroenooms%3Aop… This is the link that I share with users on my website. However when a user visits this page for the first time, they get presented an broken empty dialog box with no options named "search settings": https://i.imgur.com/nNZcekr.png This is pretty confusing because there is nothing to select and some users think that it is not working and leave the page instead of clicking "OK". -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 8 months

[opensuse-buildservice] yum update before building?

by Jeroen Ooms

My OBS is repo contains broken Fedora 27/28 builds because OBS Fedora repo seems to contain older versions of some critical dependencies. In particular, OBS seems to have R-core-3.4.4 whereas Fedora currently ships R-core-3.5.0. Because these versions are binary incompatible, the OBS build of my application does not work on the user machine. Log file: https://build.opensuse.org/build/home:jeroenooms:opencpu-2.0/Fedora_28/x86_… Is there some way to "yum update" before starting the build? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 years, 8 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service August 2018