September 2022 - openSUSE Build Service

Run obs-worker inside Docker
by Kyle Edwards 15 Sep '22

15 Sep '22

Hello, I'm trying to run obs-worker inside a Docker container, but am having some difficulty due to its use of screen. Screen says "Clear screen capability required." This happens even if I enable TTY and stdin on the container. The only way to get it to work is to start the container in attached mode - running in detached mode triggers the error. Anyone had any luck getting a worker to work inside a Docker container? Kyle

1 0

Ubuntu 22.04 Build Failing
by Kyle Edwards 15 Sep '22

15 Sep '22

Hello, I'm currently attempting to build a package on Ubuntu 22.04, but am seeing the following error in the log: [ 1s] /srv/obs/worker/root_15/.init_b_cache/rpms/base-files.deb: control.tar is not second ar entry [ 1s] bad binary: base-files.deb Any idea what this is about? Kyle

4 7

News regarding the request workflow redesign in OBS
by Lukas Krause 14 Sep '22

14 Sep '22

Hey there, We recently introduced the redesign of the request workflow through the beta program in OBS. After receiving a lot of feedback from you we've continued working on it, this time adding support for multi-action submit requests and improving the way we visualize the comments in the conversation area. Checkout the new blog post https://openbuildservice.org/2022/09/14/request-workflow-redesign-round-two/ for more details and give us your feedback :) Kind regards, Your OBS Team -- Lukas Krause, Build Solutions SUSE Software Solutions Germany GmbH Maxfeldstrasse 5 90409 Nürnberg (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev

1 0

Ubuntu 20.04 - llvm and mono-devel
by Sveinar Søpler 12 Sep '22

12 Sep '22

For some reason it seems installing llvm(10) and mono-devel together when building a package for Ubuntu 20.04 it fails. [ 78s] [221/390] installing mono-runtime-common-6.8.0.105+dfsg-2 [ 79s] dpkg: mono-runtime-common: dependency problems, but configuring anyway as you requested: [ 79s] mono-runtime-common depends on mono-gac (= 6.8.0.105+dfsg-2); however: [ 79s] Package mono-gac is not installed. [ 79s] update-binfmts: warning: unable to open /usr/share/binfmts/cli: No such file or directory [ 79s] update-binfmts: warning: couldn't find information about 'cli' to import [ 79s] update-binfmts: exiting due to previous errors [ 79s] dpkg: error processing package mono-runtime-common (--install): [ 79s] installed mono-runtime-common package post-installation script subprocess returned error exit status 2 [ 79s] Errors were encountered while processing: [ 79s] mono-runtime-common [ 79s] exit ... Complete log from a minimal test here: https://build.opensuse.org/build/home:SveSop/xUbuntu_20.04/x86_64/testdummy… test-xUbuntu_20.04.dsc: Build-Depends: libtinfo-dev <!nocheck>, llvm-dev <!nocheck>, mono-devel <!nocheck>, I used the same .dsc for 22.04 and it did not have the same issues. Installing this on a live 20.04 system does not have this issue. Difference between 20.04 and 22.04 seems to be llvm-10 and llvm-14, and the fact that seemingly llvm-10 for 20.04 installs the package binfmt-support. This package was not listed as installed in the log for 22.04. There is also the strangeness with mono-gac dependency for mono-runtime-common that does not happen for 22.04. This works fine in a local docker image (and live system) for 20.04 and does not seem to have the same issues, as mono-gac is automatically installed and the scripts are run without problems. Thoughts? Sveinar

1 0

Build environment for openSUSE_Leap_15.3 has more recent kernel-rt than distribution
by Florian Pose 12 Sep '22

12 Sep '22

Hello, I am building a package ethercat [1] that has a dependency on kernel-rt. The following repositories are enabled: openSUSE:Leap:15.3:Update/standard openSUSE:Leap:15.3/standard The version of the kernel-rt packege found in the build environment is 5.3.18-8.13.1 (see build log [2]), while the distribution (update repositories [4] and [5] enabled) provides an older version (5.3.18-8.3.1). So when installing the kmp module, the modules can't be loaded and the package is unusable. Where does the build system find the kernel-rt-5.3.18-8.13.1 package? Are there other repositories enabled, that are not part of the distribution? Thanks a lot, Florian [1] https://build.opensuse.org/package/show/science:EtherLab/ethercat [2] https://build.opensuse.org/package/live_build_log/science:EtherLab/ethercat… [3] http://download.opensuse.org/distribution/leap/15.3/repo/oss/x86_64/kernel-… [4] http://download.opensuse.org/update/leap/15.3/sle/ [5] http://download.opensuse.org/update/leap/15.3/oss/

3 5

CentOS 9 Stream
by Cyrus 09 Sep '22

09 Sep '22

Hello!, I see CentOS 9 Stream is not a distribution target per se today, but I do see a CentOS:CentOS-9:Stream/Standard repository available. Should I be able to build packages today for that distribution?. I tried adding a package but failed miserably with unresolvable errors. Regards, CI.-

1 0

add a new key signed by an old one to an OBS repo?
by Stefan Seyfried 09 Sep '22

09 Sep '22

Hi OBS community, today when running "zypper ref" on one of my raspberry pies, I saw the following: ------8<-----snip----8<------ Retrieving: repomd.xml ..........................................[done] Repository: openSUSE-Tumbleweed-Oss Key Fingerprint: 22C0 7BA5 3417 8CD0 2EFE 22AA B88B 2FD4 3DBD C284 Key Name: openSUSE Project Signing Key <opensuse(a)opensuse.org> Key Algorithm: RSA 2048 Key Created: Mon May 5 08:37:40 2014 Key Expires: Thu May 2 08:37:40 2024 Rpm Name: gpg-pubkey-3dbdc284-53674dd4 Note: Received 1 new package signing key from repository "openSUSE-Tumbleweed-Oss": Those additional keys are usually used to sign packages shipped by the repository. In order to validate those packages upon download and installation the new keys will be imported into the rpm database. New: Key Fingerprint: AD48 5664 E901 B867 051A B15F 35A2 F86E 29B7 00A4 Key Name: openSUSE Project Signing Key <opensuse(a)opensuse.org> Key Algorithm: RSA 4096 Key Created: Mon Jun 20 14:03:14 2022 Key Expires: Fri Jun 19 14:03:14 2026 Rpm Name: gpg-pubkey-29b700a4-62b07e22 The repository metadata introducing the new keys have been signed and validated by the trusted key: Repository: openSUSE-Tumbleweed-Oss Key Fingerprint: 22C0 7BA5 3417 8CD0 2EFE 22AA B88B 2FD4 3DBD C284 Key Name: openSUSE Project Signing Key <opensuse(a)opensuse.org> Key Algorithm: RSA 2048 Key Created: Mon May 5 08:37:40 2014 Key Expires: Thu May 2 08:37:40 2024 Rpm Name: gpg-pubkey-3dbdc284-53674dd4 ------8<-----snip----8<------ I would be *very* interested in doing something like that on my private OBS installation (replacing an old RSA1024 key with a current one without having all installations manually accept that key). Is there documentation available on how to achieve this? Best regards, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

3 4

add a new key signed by an old one to an OBS repo?
by Stefan Seyfried 09 Sep '22

09 Sep '22

Hi OBS community, today when running "zypper ref" on one of my raspberry pies, I saw the following: ------8<-----snip----8<------ Retrieving: repomd.xml ..........................................[done] Repository: openSUSE-Tumbleweed-Oss Key Fingerprint: 22C0 7BA5 3417 8CD0 2EFE 22AA B88B 2FD4 3DBD C284 Key Name: openSUSE Project Signing Key <opensuse(a)opensuse.org> Key Algorithm: RSA 2048 Key Created: Mon May 5 08:37:40 2014 Key Expires: Thu May 2 08:37:40 2024 Rpm Name: gpg-pubkey-3dbdc284-53674dd4 Note: Received 1 new package signing key from repository "openSUSE-Tumbleweed-Oss": Those additional keys are usually used to sign packages shipped by the repository. In order to validate those packages upon download and installation the new keys will be imported into the rpm database. New: Key Fingerprint: AD48 5664 E901 B867 051A B15F 35A2 F86E 29B7 00A4 Key Name: openSUSE Project Signing Key <opensuse(a)opensuse.org> Key Algorithm: RSA 4096 Key Created: Mon Jun 20 14:03:14 2022 Key Expires: Fri Jun 19 14:03:14 2026 Rpm Name: gpg-pubkey-29b700a4-62b07e22 The repository metadata introducing the new keys have been signed and validated by the trusted key: Repository: openSUSE-Tumbleweed-Oss Key Fingerprint: 22C0 7BA5 3417 8CD0 2EFE 22AA B88B 2FD4 3DBD C284 Key Name: openSUSE Project Signing Key <opensuse(a)opensuse.org> Key Algorithm: RSA 2048 Key Created: Mon May 5 08:37:40 2014 Key Expires: Thu May 2 08:37:40 2024 Rpm Name: gpg-pubkey-3dbdc284-53674dd4 ------8<-----snip----8<------ I would be *very* interested in doing something like that on my private OBS installation (replacing an old RSA1024 key with a current one without having all installations manually accept that key). Is there documentation available on how to achieve this? Best regards, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

1 0

AlmaLinux:9 prjconf missing FileProvides for alternatives
by Neal Gompa 07 Sep '22

07 Sep '22

Hey, I was trying to build a package targeting AlmaLinux:9, but it failed to work because the compiler was broken. The compiler was broken because the alternatives symlinks for ld weren't made, which caused the compiler to not be able to produce working executables. In order to fix this, the following needs to be added to the AlmaLinux:9 prjconf: FileProvides: /usr/sbin/alternatives alternatives FileProvides: /usr/sbin/update-alternatives alternatives It might also be worth checking for any discrepancies between AlmaLinux:9 and CentOS:CentOS-9:Stream project configs, since they're effectively the same distribution. Stuff in CS9 but not AL9 should be added to the AL9 config. Thanks in advance! -- 真実はいつも一つ！/ Always, there's only one truth!

2 1

obs aarch64 worker
by Jakob Lorenz 04 Sep '22

04 Sep '22

Hello, I use a private OBS instance to build my programs. So far everything is running on x86 hardware and today I wanted to add an aarch64 worker. Unfortunately I could not find an obs-worker package for aarch64, except for the one in unstable Is there a recommended way to create an aarch64 worker without using the unstable package? Jakob

3 2