openSUSE Build Service May 2021

buildservice@lists.opensuse.org

14 participants
11 discussions

by Avindra G

I've been having trouble getting deno to build since v1.9.0 (April 13th, 2021) on x86_64. Tried various _constraints values, but the job is failing with the same error: [ 3311s] LLVM ERROR: IO failure on output stream: No space left on device [ 3311s] /.build/build-vm: line 460: echo: write error: No space left on device [ 3312s] error: could not compile `deno` [ 3312s] https://build.opensuse.org/package/show/devel:languages:javascript/deno#com… Can anyone advise? Thanks, avindra goolcharan

21 hours, 5 minutes

Missing choice

by Martin Koegler

An setting is missing for Fedora_Rawhide: have choice for libusb-1.0.so.0()(64bit) needed by libgusb: libusb1 libusbxh have choice for libusb-1.0.so.0 needed by libgusb: libusb1 libusbx Regards, Martin

1 day, 18 hours

emerging low code app development platforms

by Rosy

there is an increase in usage of low code platforms by many startups, medium-sized and in every business. low code platforms are trending now because even with zero coding knowledge people can develop apps. it saves time and money. For more info click below: https://www.wavemaker.com/low-code-app-development-platform/ to learn more about mobile app development platforms click below https://www.wavemaker.com/mobile-app-development-platform/

6 days, 17 hours

emerging low code app development platforms

by Rosy

6 days, 17 hours

low code

by Rosy

nowadays <a href="https://www.wavemaker.com/low-code-app-development-platform/">low code platforms</a> are becoming prominent,and time saving for the business. even with minimal coding knowledge people can create apps. so many businesses are opting for it.

6 days, 17 hours

Initial setup trouble building .deb package

by Dirk Eddelbuettel

Hi all, First time poster, thanks for having me! I am trying to follow the lead of Detlef Steuer to (eventually) build (a lot of) R language packages from the CRAN network for Debian (and maybe also Ubuntu) by using the excellent Build Service. I am fairly familiar with the Debian package format and tools as well as with R packages but very green with the OpenSuSE Build Service. Following the (generally very nice) documentation plus one external blog post, I set up a first (simple) package (which I already maintain in Debian and am also upstream for). It fails on seeming conflict (driven from the R package) expecting a choice from a "virtual" to a "concrete" jpeg package: edd@rob:~/obs/home/eddelbuettel/r-cran-pkgkitten$ osc build --local-package Building r-cran-pkgkitten.dsc for Debian_Testing/x86_64 Getting buildconfig from server and store to /home/edd/obs/home/eddelbuettel/r-cran-pkgkitten/.osc/_b uildconfig-Debian_Testing-x86_64 Getting buildinfo from server and store to /home/edd/obs/home/eddelbuettel/r-cran-pkgkitten/.osc/_buildinfo-Debian_Testing-x86_64.xml buildinfo is broken... it says: unresolvable: have choice for libjpeg-dev needed by r-base-dev: libjpeg-dev libjpeg62-turbo-dev edd@rob:~/obs/home/eddelbuettel/r-cran-pkgkitten$ Detlef suggested editing 'Project Config' in https://build.opensuse.org/projects/home:eddelbuettel/prjconf which I did, but that lead a 'IncompletRead error. The same error I get with a smaller/simpler package I tried and which only depends on two -dev packages: edd@rob:~/obs/home/eddelbuettel/xrprof$ osc build --local-package Building xrprof.dsc for Debian_Testing/x86_64 Getting buildconfig from server and store to /home/edd/obs/home/eddelbuettel/xrprof/.osc/_buildconfig -Debian_Testing-x86_64 Getting buildinfo from server and store to /home/edd/obs/home/eddelbuettel/xrprof/.osc/_buildinfo-Debian_Testing-x86_64.xml IncompleteRead(0 bytes read) edd@rob:~/obs/home/eddelbuettel/xrprof$ As you can see I am trying to build for Debian testing, and am running under Ubuntu 20.10 with what should be recent-ish tools. The osc and other packages are stock Ubuntu 20.10. I would truly appreciate a pointer or two of help. Happy to hop on online chat, #irc is a little tricker as I seem to be unable to reset my NickServ. Cheers, Dirk -- https://dirk.eddelbuettel.com | @eddelbuettel | edd(a)debian.org

1 week

Leap 15.3 as DoD repo gives "The repository setup is broken, build or publish not possible"

by Till Dörges

Hello all, since the release of 15.3 is near I'd like to test it on our internal OBS (2.10). I created a new project with a download on demand repository like this --- snip --- <project name="openSUSE.org:Leap:15.3"> <title>openSUSE Leap 15.3 OSS (DoD)</title> <description>dod</description> <person userid="x" role="maintainer"/> <repository name="standard"> <download arch="x86_64" url="http://download.opensuse.org/distribution/leap/15.3/repo/oss/" repotype="rpmmd"/> <arch>x86_64</arch> </repository> </project> --- snap --- I also copied the project configuration from api.opensuse.org/openSUSE:Leap:15.3. But when I try to use my new repo all I get in the webgui is a red warning sign and the message The repository setup is broken, build or publish not possible Looking into /srv/obs/log/dodup.log only gives me --- snip --- obs:/srv/obs/log # grep 15.3 dodup.log 2021-05-10 00:37:34: [1622] checking openSUSE.org:Leap:15.3/standard/x86_64... updating metadata for rpmmd repo at http://download.opensuse.org/distribution/leap/15.3/repo/oss/ 2021-05-10 00:44:34: [1622] checking PRESENSE/openSUSE_Leap_15.3/x86_64... updating metadata for rpmmd repo at http://download.opensuse.org/distribution/leap/15.3/repo/oss/ 2021-05-10 00:49:57: [1622] checking openSUSE.org:Leap:15.3/standard/x86_64... updating metadata for rpmmd repo at http://download.opensuse.org/distribution/leap/15.3/repo/oss/ --- snap --- The same worked perfectly for openSUSE Leap 15.*2*. Has anything changed or how do I proceed to pinpoint the error? Thanks and regards -- Till -- Dipl.-Inform. Till Dörges doerges(a)pre-sense.de PRESENSE Technologies GmbH Nagelsweg 41, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024

1 week

devel:tools:compiler/llvm12 not compiling for 15.2 x86_64

by Christoph G

Hi! I cannot install Clang 12 one openSUSE 15.2 because devel:tools:compiler/llvm12 not compile for 15.2 x86_64. The reason is, that dependencies cannot be resolves, which are there (cmake, pkgconfig, gcc-c++ and so on). 1) How can OBS be triggered, to check the existence of dependencies again? I had similar issues in the past for my packages. 2) As I don't have sufficient rights, can someone please do so that the package is build and that I can use the packages? Bye Christoph

1 week, 1 day

error in build "write /usr/src/packages/DOCKER/.docker_temp_229875213: no space left on device", what should I do?

by Oliver Kurz

Hi, just saw a build failure in a Dockerfile based container build within OBS with error "write /usr/src/packages/DOCKER/.docker_temp_229875213: no space left on device", so I wonder, if I receive the email, what should I do about it? Detailed message: ``` Visit https://build.opensuse.org/package/live_build_log/devel:openQA/ openqa_dev/containers15.2/x86_64 Package devel:openQA/openqa_dev failed to build in containers15.2/x86_64 Check out the package for editing: osc checkout devel:openQA openqa_dev Last lines of build log: … [ 168s] Successfully tagged openqa_dev:latest [ 168s] time="2021-05-07T18:27:14.570071010Z" level=warning msg="grpc: addrConn.createTransport failed to connect to { 0 <nil>}. Err :connection error: desc = \"transport: Error while dialing only one connection allowed\". Reconnecting..." module=grpc [ 168s] Saving image openqa_dev to openqa_dev.x86_64-1870.2.tar [ 183s] write /usr/src/packages/DOCKER/.docker_temp_229875213: no space left on device [ 183s] time="2021-05-07T18:27:29.881861290Z" level=error msg="Can't add file /var/lib/docker/tmp/docker-export-744719740/ c393bb26cd48f4f814473a848d88caa4d1379ece40ea92767facfea420c21a93/layer.tar to tar: io: read/write on closed pipe" [ 183s] time="2021-05-07T18:27:29.881931140Z" level=error msg="Can't close tar writer: io: read/write on closed pipe" [ 183s] docker save command failed [ 183s] Stopping local repository server [ 183s] Stopping docker daemon [ 183s] Stopping container daemon [ 183s] time="2021-05-07T18:27:29.902767880Z" level=info msg="Stop CRI service" [ 183s] time="2021-05-07T18:27:29.902869460Z" level=info msg="Stop CRI service" [ 183s] time="2021-05-07T18:27:29.903001170Z" level=error msg="failed to get event" error="rpc error: code = Unavailable desc = transport is closing" module=libcontainerd namespace=plugins.moby [ 183s] time="2021-05-07T18:27:29.903024980Z" level=error msg="failed to get event" error="rpc error: code = Unavailable desc = transport is closing" module=libcontainerd namespace=moby [ 183s] ### VM INTERACTION START ### [ 186s] [ 180.071498] sysrq: Power Off [ 186s] [ 180.074805] reboot: Power down [ 186s] ### VM INTERACTION END ### [ 186s] [ 186s] goat01 failed "build _service:download_url:Dockerfile" at Fri May 7 18:27:33 UTC 2021. [ 186s] ```

1 week, 3 days

unresolvable build on CentOS8

by ronan

Hi, I try to build a package on Centos8 and I got an issue "unresolvable" I create a test project/package: https://build.opensuse.org/package/show/home:ronan22:test_build_centos8stre… with only one "BuildRequires: python3-devel" And I got a status: "unresolvable" nothing provides python3-devel And I don't understand why. Let's dig a little. My target is (from Meta): <path project="CentOS:CentOS-8" repository="standard"/> And the repository is define as: <repository name="standard"> <path project="CentOS:CentOS-8" repository="appstream"/> <path project="CentOS:CentOS-8" repository="devel"/> <path project="CentOS:CentOS-8" repository="extras"/> <path project="CentOS:CentOS-8" repository="powertools"/> <path project="CentOS:CentOS-8" repository="baseos"/> <arch>x86_64</arch> <arch>aarch64</arch> <arch>ppc64le</arch> </repository> ( From https://build.opensuse.org/projects/CentOS:CentOS-8/meta) and repository "appstream" is define as: <repository name="appstream"> <download arch="x86_64" url="http://mirror.centos.org/centos/8/AppStream/x86_64/os/" repotype="rpmmd"> And this repository had the package: http://mirror.centos.org/centos/8/AppStream/x86_64/os/Packages/python36-dev… Providing python3-devel: # wget http://mirror.centos.org/centos/8/AppStream/x86_64/os/Packages/python36-dev… # rpm -qp --provides python36-devel-3.6.8-2.module_el8.3.0+562+e162826a.x86_64.rpm attention : python36-devel-3.6.8-2.module_el8.3.0+562+e162826a.x86_64.rpm: Entête V3 RSA/SHA256 Signature, clé ID 8483c65d: NOKEY python3-devel = 3.6.8-2.module_el8.3.0+562+e162826a python3-devel(x86-64) = 3.6.8-2.module_el8.3.0+562+e162826a python36-devel = 3.6.8-2.module_el8.3.0+562+e162826a python36-devel(x86-64) = 3.6.8-2.module_el8.3.0+562+e162826a And the repo file (primary.xml) provide python3-devel too: wget http://mirror.centos.org/centos/8/AppStream/x86_64/os/repodata/0ef16342a815… gunzip 0ef16342a8153c46513e3549e6287de0bdeb0ef4618ac36044d22b0131675d3c-primary.xml.gz <rpm:sourcerpm>python36-3.6.8-2.module_el8.3.0+562+e162826a.src.rpm</rpm:sourcerpm> <rpm:header-range start="5608" end="12130"/> <rpm:provides> <rpm:entry name="python3-devel" flags="EQ" epoch="0" ver="3.6.8" rel="2.module_el8.3.0+562+e162826a"/> <rpm:entry name="python3-devel(x86-64)" flags="EQ" epoch="0" ver="3.6.8" rel="2.module_el8.3.0+562+e162826a"/> <rpm:entry name="python36-devel" flags="EQ" epoch="0" ver="3.6.8" rel="2.module_el8.3.0+562+e162826a"/> <rpm:entry name="python36-devel(x86-64)" flags="EQ" epoch="0" ver="3.6.8" rel="2.module_el8.3.0+562+e162826a"/> </rpm:provides> Do you have any idea to solve that? I have got same issue with golang (you can try to add (BuildRequires: go >= 1.11). Best Regards, Ronan Le Martret [IoT.bzh]

2 weeks, 1 day

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Build Service May 2021