March 2021 - openSUSE Build Service - openSUSE Mailing Lists

[opensuse-buildservice] Add external source to a package?
by Carsten Ziepke 12 Sep '23

12 Sep '23

Hello, I want to update the package ja2-stracciatella in the games repository to version 0.17.0. https://build.opensuse.org/package/show/home:Kieltux:branches:games/ja2-str… The new version needs the library string_theory which is not available for openSUSE. The build process wants to download string_theory from github, because it is not found. [ 36s] Scanning dependencies of target string_theory [ 36s] [ 12%] Creating directories for 'string_theory' [ 37s] [ 25%] Performing download step (download, verify and extract) for 'string_theory' [ 37s] -- Downloading... [ 37s] dst='/home/abuild/rpmbuild/BUILD/ja2-stracciatella-0.17.0/build/dependencies/lib-string_theory/builder/string_theory-prefix/src/3.1.tar.gz' [ 37s] timeout='none' [ 37s] -- Using src='https://github.com/zrax/string_theory/archive/3.1.tar.gz' [ 37s] -- Retrying... Can I add string_theory (string_theory-3.1.tar.gz) manually to the package and patch the build process? Thank you, Carsten -- Well, since MS cant be sure of the username of someone downloading things, they are going to play it safe and have everything dowloaded and executed by Explorer as suid root. That way, it will run on ANY system anywhere. :) -- George Bonser <grep(a)cris.com>

3 4

[opensuse-buildservice] Compiler Cache (Ccache) support in Open Build Service
by Sumit Jamgade 20 Apr '21

20 Apr '21

Hello, Long running compilation can now leverage ccache[1] to speed up the build process. This feature can be enabled per package in the project config: BuildFlags: useccahe:<packagename> example: https://build.opensuse.org/projects/home:sjamgade:branches:science:machinel… Once enabled per package, it will be enabled for all architectures and repositories. https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.prjconfig.… (grep ccache) --- The ccache tar file is collected only on *successful builds with changed result*. It is extracted for every build at /.ccache/ if enabled. This build artifact is not versioned and only the latest tar is stored. It can be downloaded from the webui or osc. https://build.opensuse.org/package/binaries/home:sjamgade:branches:science:… osc getbinaries --ccache -M standard home:sjamgade:branches:science:machinelearning tensorflow openSUSE_Tumbleweed x86_64 _ccache.tar osc getbinaries --ccache $prj $pkg $repo $arch _ccache.tar This archive can be further used for local builds too. osc build --pkg-ccache /full/path/to/_ccache. (please use the latest osc) --- Ccache config file is stored in /.ccache/ccache.conf and is writable by the build user. So, it could also be disabled (or configured as per package requirements) echo "disable = true" >> /.ccache/ccache.conf For possible build time comparisons: https://build.opensuse.org/packages/tensorflow:standard/job_history/home:sj… https://w3.nue.suse.com/~sjamgade/ccachereport.html Thank you, Sumit Jamgade and OBS Team [1] - https://ccache.dev/ PS: Some packages (eg: tensorflow) need extra plumbing in spec file to enable access to /.ccache and use of ccache cmd: export CC_PREFIX=ccache; ln -s /.ccache/ ~/.ccache -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

6 14

[opensuse-buildservice] Short OBS downtime this Saturday
by Michael Schroeder 20 Apr '21

20 Apr '21

Hi OBS users, we need to do a little database maintenance on Saturday at 21:00 UTC. The buildservice will not be available for about 30 minutes. The build service will still schedule and finish builds in that time, but the API and the Web UI will not be available. Thanks for your understanding and have a nice weekend, Michael. -- Michael Schroeder SUSE Software Solutions Germany GmbH mls(a)suse.de GF: Felix Imendoerffer HRB 36809, AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

Package builds for SLE_12_SP5 (only on x86_64) stop working because of multiple choices for sub-dependency
by Frank Scheiner 01 Apr '21

01 Apr '21

Hi all, since about mid March 2021 some of my [GCT] package builds for SLE_12_SP5 on x86_64 ([1]) stop(ped) working with: ``` have choice for pkgconfig(zlib) needed by libopenssl-1_0_0-devel: zlib-devel zlib-devel-32bit ``` [GCT]: https://github.com/gridcf/gct [1]: https://build.opensuse.org/project/monitor/home:frank_scheiner:gct?arch_x86… Trying a build locally with `osc` gives: ``` johndoe@host:~/osc/home:frank_scheiner:gct/globus-authz> time osc build SLE_12_SP5 x86_64 globus-authz.spec Building globus-authz.spec for SLE_12_SP5/x86_64 Run source service: /usr/lib/obs/service/download_url --host repo.gridcf.org --protocol https --path /gct6/sources/globus_authz-4.4.tar.gz --outdir /home/johndoe/osc/home:frank_scheiner:gct/globus-authz/tmp1jccm9xf.download_url.service Getting buildconfig from server and store to /home/johndoe/osc/home:frank_scheiner:gct/globus-authz/.osc/_buildconfig-SLE_12_SP5-x86_64 Getting buildinfo from server and store to /home/johndoe/osc/home:frank_scheiner:gct/globus-authz/.osc/_buildinfo-SLE_12_SP5-x86_64.xml buildinfo is broken... it says: unresolvable: have choice for pkgconfig(zlib) needed by libopenssl-1_0_0-devel: zlib-devel zlib-devel-32bit real 0m11.201s user 0m1.321s sys 0m0.175s ``` Because of "buildinfo is broken" I'd tend to assume that something broke in the SLE_12_SP5 repos used by me (SUSE:SLE-12-SP5:GA/standard, SUSE:SLE-12-SP5:Update/standard) but such a message can also be created by an error in the build requirments IIUC, so I'm not sure about that. What could lead to such a situation - both 32 bit and 64 bit package available for dependency solution - for a build on x86_64? Cheers, Frank

4 9

account recovery (email inaccessible)
by Roman Neuhauser 31 Mar '21

31 Mar '21

hello there, i haven't used build.opensuse.org for quite some time, forgot my password, and i no longer have access to the email associated with my account. or at least the password reset token doesn't arrive, and i suspect i have an old work email configured in the o.o.o account. the user name is "roman-neuhauser" and home:roman-neuhauser has quite a few packages for software written by myself mentioning my other email addresses such as neuhauser(a)sigpipe.cz, roman(a)sigpipe.cz or variations thereof. see eg. [1]. is this a good-enough proof that these two (o.o.o roman-neuhauser and {roman,neuhauser}(a)sigpipe.cz) are the same person so an admin would set one of these on my o.o.o account? failing that, what are my options? [1] https://build.opensuse.org/package/view_file/home:roman-neuhauser/basexy/PK… thanks, -- roman

2 1

How to investigate/fix "The repository setup is broken, build or publish not possible"
by Sebix 30 Mar '21

30 Mar '21

Dear list, I need your advice and help to fix a "The repository setup is broken, build or publish not possible" problem as I haven't able to find any documentation on this error so far. In https://build.opensuse.org/project/show/home:sebix:intelmq I get the error for CentOS 8. It appeared today after a change in the projconf: I added "Substitute: python3-falcon python36-falcon" in a "%if 0%{?centos_version} == 700" block. I have no idea how this could have caused the broken repository for CentOS 8? Local builds work fine. I have the same error in https://build.opensuse.org/project/show/home:sebix:intelmq:unstable for CentOS 7 and CenOS 8, whereas the latter is probably a result of the error in the home:sebix:intelmq repository. For the CentOS 7 error, I don't know when it appeared first and what caused it. Can anyone help me on this matter? Thank you in advance Sebastian

1 2

Broken services?
by Erico Mendonca 26 Mar '21

26 Mar '21

The pw3270 development package is getting tar_scm errors since yesterday. Already tried triggering services, but all I get is this error: Files could not be expanded: service error: DEBUG:root:Cleaning: /var/cache/obs/w8nn1L4JYFhE/out/tmpqy8l2xl8 less info service tar_scm failed: time="2021-03-23T12:45:36Z" level=warning msg="Path \"/etc/SUSEConnect\" from \"/etc/containers/mounts.conf\" doesn't exist, skipping" time="2021-03-23T12:45:36Z" level=warning msg="Path \"/etc/zypp/credentials.d/SCCcredentials\" from \"/etc/containers/mounts.conf\" doesn't exist, skipping" Running /usr/lib/obs/service//tar_scm --scm git --url https://github.com/PerryWerneck/pw3270.git --changesgenerate enable --filename pw3270-unstable --revision develop --versionformat @PARENT_TAG@+git%cd --outdir /var/cache/obs/w8nn1L4JYFhE/out DEBUG:root:Checking .... en_US.utf8 The package builds locally just fine. Something broken at the worker? The package URL: https://build.opensuse.org/package/show/home:PerryWerneck:pw3270/pw3270-uns…

4 8

goat* build hosts broken?
by Manfred Hollstein 25 Mar '21

25 Mar '21

Hi there, since two days I was trying to get firefox87 built for the usual distribution versions. It succeeded for Leap 15.1, 15.2, and Tumbleweed x86_64, but failed for 15.3 and Tumbleweed i586. After some time it appeared to me that the succeeding build hosts are "lamb*", while the failing ones are "goat*". For details please just look at <https://build.opensuse.org/packages/firefox87/job_history/home:manfred-h:mo…> Is it possible that something is inconsistent/wrong/broken on any of these machines? Cheers. l8er manfred

2 2

aarch64 Server Not Recognized As Supporting aarch32
by Kyle Edwards 23 Mar '21

23 Mar '21

Hello, I recently obtained an aarch64 server which runs aarch32 code just fine. However, OBS does not recognize that it can run aarch32 code and reports it as "nativeonly" to the dispatcher. Looking through the dispatcher code shows that it's examining a set of flags from /proc/cpuinfo to determine if aarch32 is supported, and my particular flags: processor : 0 BogoMIPS : 80.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x50 CPU architecture: 8 CPU variant : 0x3 CPU part : 0x000 CPU revision : 2 are not recognized as supporting aarch32. For reference, we have another server which is recognized: processor : 0 BogoMIPS : 500.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x1 CPU part : 0xd07 CPU revision : 2 Is the code simply out of date, or is there a reason why my server's CPU is not included? Kyle

2 4

Random build error
by Axel Braun 23 Mar '21

23 Mar '21

Hi, I get every now and then a build error, even without changing anything on the sources: hardlink-across-partition It happened suddenly for all Leap builds, while TW is fine. I have worked around it with a rpmlint file, but would like to know the reason for this error if possible... Thanks Axel

3 4

Unconditional rebuild of project - or re-signing every package in a project
by Stefan Botter 21 Mar '21

21 Mar '21

Hi everyone, I need help on a private instance of OBS: Packman (PMBS). Due to oversight/lazyness the standard GPG key expired a while ago. Once I extended the key, one of the projects could not be signed anymore. Most probably while fixing the expired-key-problem I removed a very old standard key from the keyring, which in turn signed the project key of the now failing project. I could get the project working and signing by issuing a new project key using 'osc signkey ...'. So far everything is ok, but with Packman we have an external publishing mechanism (through publishing_hooks), which stages published repos to an external server, where the packages are re-signed with the Packman RPM key. Part of the re-signing is a check for the original key used by PMBS. If they used key on PMBS is not in the keyring of the re-signer, the packages are not re-signed and hence not published. Totally our problem. The way out for me is either a) allow the new key on the re-signer, or b) change the project key on PMBS for said project. Option "a" is easy, but I am not allowed to do that, and our fellow with access is not available at the moment. I chose option "b" using a modified already known key and injected it to the project using 'obs_admin -update-project-signing-key ...'. This is working perfectly. Now the problem at hand: New packages are signed, re-signed and published through our workflow as expected. All other packages built since the issue with the renewed project signing key started and before I set the actual working project key are still signed with the "unknown" key and are not re-singed and published. I see three possible ways out of this situation: 1. wait for a occasional rebuild of the respective package, 2. rebuild the whole project unconditionally, or 3. re-sign all packages form the project with the new project key, and republish through PMBS. Solution 1 is of course the "natural" way, but it is unclear, when rebuild and publishing happens, and it is sort of random - lame :) Solution 2 is acceptable, but is costlier than 3. Solution 3 seems the fastest, but I am unsure, if this can be triggered from PMBS. TL;DR: How can I trigger an unconditional rebuild of all packages inside a project? Can I trigger only a re-signing of packages in a project, and trigger a fresh publishing from PMSB? Any help is greatly appreciated! TIA, Stefan PS: The project in question is "Multimedia", which seems to be quite popular :) -- Stefan Botter zu Hause Bremen

2 2

How to remove decommissioned workers from OBS monitoring page
by Morschhäuser, Mark 18 Mar '21

18 Mar '21

Hello, we created some test workers for our private OBS instance and wonder how to remove them from the monitoring page. Is there a command to do that? Thank you in advance, Mark

2 1

Re: How can I add in a spec file the build version and distribution version in a spec file?
by Erico Mendonca 17 Mar '21

17 Mar '21

Have you tried using something like "-DANTIMICROX_PKG_VERSION=\"'%{version}-%{release} (openSUSE Leap/x86_64)'\"" in your SPEC? [cid:dd6920b0-e198-4ad7-ac2d-fba2ac510d7d] Erico Mendonca Premium Services SUSE ________________________________ From: Carsten Ziepke Sent: Wednesday, March 17, 2021 2:45 PM To: opensuse-buildservice(a)opensuse.org Subject: How can I add in a spec file the build version and distribution version in a spec file? Hello, a package I maintain in OBS added a new feature to enable reproducible builds: https://github.com/AntiMicroX/antimicrox/pull/143 "By default, the date and time of the build are embedded into the binary as sort of origin/version/etc. marker. This is not, however, reproducible. This patch makes it so that packagers can define a præprocessor macro, ANTIMICROX_PKG_VERSION, to a C string which is then used instead; if this macro is not defined nothing changes." For example: "-DANTIMICROX_PKG_VERSION=\"'3.1.4-1 (Debian sid/amd64)'\"" How can I do this in the same way in OBS (add buildversion and distribution version) via spec file? Thank you, Carsten -- Anyone who thinks UNIX is intuitive should be forced to write 5000 lines of code using nothing but vi or emacs. AAAAACK! -- Discussion on the intuitiveness of commands, especially Emacs

1 0

How can I add in a spec file the build version and distribution version in a spec file?
by Carsten Ziepke 17 Mar '21

17 Mar '21

Hello, a package I maintain in OBS added a new feature to enable reproducible builds: https://github.com/AntiMicroX/antimicrox/pull/143 "By default, the date and time of the build are embedded into the binary as sort of origin/version/etc. marker. This is not, however, reproducible. This patch makes it so that packagers can define a præprocessor macro, ANTIMICROX_PKG_VERSION, to a C string which is then used instead; if this macro is not defined nothing changes." For example: "-DANTIMICROX_PKG_VERSION=\"'3.1.4-1 (Debian sid/amd64)'\"" How can I do this in the same way in OBS (add buildversion and distribution version) via spec file? Thank you, Carsten -- Anyone who thinks UNIX is intuitive should be forced to write 5000 lines of code using nothing but vi or emacs. AAAAACK! -- Discussion on the intuitiveness of commands, especially Emacs

1 0

Repository Signing Key Expiry
by Mark Grant 16 Mar '21

16 Mar '21

This email is specific to Debian / Raspbian repos. 1) This is the first problem. Over the weekend the repo signing key downloaded during initial set-up expired. (This sort of set-up https://software.opensuse.org//download.html?project=home%3Am-grant-prg&pac…) This led to all attempts to use the repsitory to error out, (eg apt-get update, apt-get install....). The errors appeared as below:- sudo apt-get update Hit:1 http://archive.raspberrypi.org/debian buster InRelease Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB] Get:3 http://download.opensuse.org/repositories/home:/m-grant-prg/Raspbian_10 InRelease [1,531 B] Hit:4 https://apt.syncthing.net syncthing InRelease Err:3 http://download.opensuse.org/repositories/home:/m-grant-prg/Raspbian_10 InRelease The following signatures were invalid: EXPKEYSIG 3FD1CDB63E00F70B home:m-grant-prg OBS Project <home:m-grant-prg@build.opensuse.org> This happened to me and to an unknown size user community. 2) This is the second problem. I established that the key had been refreshed on opensuse.org and now had a mid-2023 expiry date so I thought re-downloading it using the curl command in the instructions should do the trick. The command worked OK but the curl command had changed from using a target keyring of "home:m-grant-prg.gpg" to "home_m-grant-prg.gpg". So the curl command did not overwrite the old keyring. The end result was that the old expired key was still found and repository actions still errored out. The solution I have suggested to the user community is to remove the offending keyring. It seems obvious that this exact same problem will occur in 2023 (at least problem 1). I am sure that OBS has a transparent solution for this and I just have never seen it. I would be most grateful if someone could point me in the direction of the relevant documentation. Thanks, Mark

2 2

No live log available" when a separate worker build job finished
by ynliu＠linx-info.com 16 Mar '21

16 Mar '21

I had installed a private OBS server (2.9.6 appliance)on x86_64 machine and disable obs worker component, Meanwhile, I also installed a separate x86_64 worker on another machine and a arm64 obs worker on raspberry pi4, I configure obs server and these two separate obs worker(x86_64 and arm64 pi4) according to manual "https://openbuildservice.org/help/manuals/obs-admin-guide/" and "https://openbuildservice.org/help/manuals/obs-user-guide/" Meanwhile, the following content was gotten on dispatcher.log file on obs server "badhost event: home:<username>:<projectname>/hello/x86_64/x86_64:obs-worker-x86:1 Use of uninitialized value in concatenation (.) or string at /usr/lib/obs/server/bs_dispatch line 628. Use of uninitialized value in concatenation (.) or string at /usr/lib/obs/server/bs_dispatch line 629. " on obs worker machine, look up /var/cache/obs/worker/root_x, all debs(debian packages) may be made successufully. why does I alway get the ERRROR? Could you give me any help or advices ? I can registered two separate obs workers to obs server (2.9.6) and build jobs may be started (both arm64 and x86_64), but alway get the following hint on WebUI/API after I start debian package "hello" building "No live log available: package 'hello' has no logfile" Additionally,I also test 2.10.10, But I can confirm that it is problem about bs_worker, because I found a "Logfile is not that big" output from function 'stream_logfile()' in /usr/lib/obs/server/worker/bs_worker through looking up rep_server.log or capturing network packet by wireshark tools

1 0

Server Status - back-home i586/x86_64 dead - back-other i586 dead
by munix9 14 Mar '21

14 Mar '21

Server Status back-home i586/x86_64 dead back-other i586 dead https://build.opensuse.org/monitor

2 1

Kindly unsubscribe me from mailing list
by Nitesh Konkar 12 Mar '21

12 Mar '21

1 0

new devel project plus some spring cleanup
by Paolo Stivanin 11 Mar '21

11 Mar '21

Hello all, I'd like to start promoting openSUSE in the astro world, but in order to do that I'd like to first do some OBS cleanup/reorg. What I'd like to do is: * Push graphics/CImg to openSUSE:Factory * Push science/ccfits to openSUSE:Factory * Create devel project "Application:Astrophotography" * Move from KDE:Extra to Application:Astrophotography (the maintainer wrote in an old SR I made that they put libindi there because no one else wanted to maintain it) - libindi * Move from Application:Geo to Application:Astrophotography (I'm the current maintainer for this, so no issue here I guess) - phd2 * Delete from Science (I'm the one pushing to Science/ASTAP*, but because of the fast release cycle I stopped doing that and kept only the one in my home) - ASTAP{,-dbs,-g17data} * Move from home:polslinux:astrophotography to Application:Astrophotography - libindi-3rdparty (this is a must, having only libindi is of very little to no use. But I don't think this can be pushed to Factory. There are way too many firmware :)) - Skychart{,-data} - sirilic - lin_guider - ASTAP{,-dbs,-h17data} (the guys in Science told me that due to licensing issue -dbs can't go to factory, and without dbs it's of no use this program) - ser_player - astrometetry.net What are your thoughts on this? Thanks a lot, Best regards, Paolo

4 6

Please switch to an updated Fedora:Rawhide mirror
by Neal Gompa 10 Mar '21

10 Mar '21

Hey all, The mirror being used for most Fedora:Rawhide targets (ftp.fau.de) is no longer an official mirror and has been out of sync for over a month now. Can someone please switch it to another mirror that is kept up to date, such as ftp-stud.hs-esslingen.de (used already for some of them). Thanks in advance! -- 真実はいつも一つ！/ Always, there's only one truth!

2 1

Create a SR to add a linked package to a project?
by Johannes Kastl 05 Mar '21

05 Mar '21

Hi all, sorry if this is an old hat, but my google-foo left me: Can I create a SR to add a linkpac'ed package to a project? The end result (after someone accepts the SR) should be that the package in the project should be a link to some other package. 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

1 0

Re: Retention policy of container images from registry.opensuse.org
by Frank Schreiner 03 Mar '21

03 Mar '21

Am Mittwoch, dem 03.03.2021 um 09:48 +0100 schrieb Richard Brown: > > > Hi Frank, > > Robert isn't asking for the retention of containers when they are > removed from > https://build.opensuse.org/project/show/openSUSE:Containers:Tumbleweed > > Robert is asking for a longer retention of containers with old tags > from > https://build.opensuse.org/project/show/openSUSE:Containers:Tumbleweed > when they are superseded with new containers with new tags > > Currently registry.opensuse.org has a period where both 'old tag' > containers and 'current tag' containers coexist. As I already tried to point out - there is no such period. If you delete e.g. the "package" kubic-kube-proxy-minus1-image.20210114151709 at least tag kubic/kube-proxy:v1.19.6-2.1000 will be gone. If you delete kubic-kube-proxy-minus1-image.20210108134717 kubic-kube-proxy-minus1-image.20210114151709 kubic-kube-proxy-minus1-image.20210126101702 the tag kubic/kube-proxy:v1.19.6 will be gone - because it occurs in all this packages.

1 0

Retention policy of container images from registry.opensuse.org
by Robert Munteanu 03 Mar '21

03 Mar '21

Hi, After some trouble with one of my kubic clusters [1] I was told to ask here regarding the retention policy for registry.opensuse.org container images. My cluster went down because I was still running an 'old' set of images, e.g. registry.opensuse.org/kubic/kube-proxy:v1.19.4 and, for some reason, the image was no longer available on the node after a restart. At the time of the discusison, v1.19.4 was gone and v1.19.7 was available on registry.o.o . Can this retention policy be tweaked? I would imagine it would be beneficial for users of kubic to have the images available for a longer time. I don't dare say forever as I'm not aware of the impact that has, but it would definitely be the nicest. For the record, these are the images that are stored on registry.o.o for my cluster: $ kubectl get pod -A -o jsonpath='{range .items[*].spec.containers[*]} {.image}{"\n"} {end}' | grep registry.opensuse | sort -u registry.opensuse.org/kubic/coredns:1.7.0 registry.opensuse.org/kubic/etcd:3.4.13-0 registry.opensuse.org/kubic/kube-apiserver:v1.20.2 registry.opensuse.org/kubic/kube-controller-manager:v1.20.2 registry.opensuse.org/kubic/kube-proxy:v1.20.2 registry.opensuse.org/kubic/kube-scheduler:v1.20.2 registry.opensuse.org/kubic/weave-kube:2.8.1 registry.opensuse.org/kubic/weave-npc:2.8.1 Thanks, Robert [1]: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org/thread/RJ…

2 1