September 2020 - openSUSE Build Service

[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

[opensuse-buildservice] handling one thousand source tarballs in one package
by Ludwig Nussel 22 Jan '21

22 Jan '21

Hi, I'm trying to build a package from source that uses npm modules. Doing so involves more than one thousand(!) upstream tarballs. In the hope to make that more manageable I wrote a PoC script¹ to produuce a file includable from the spec and to also download the tarballs. Uploading them to OBS as part of the source is rather annoying though as you can't see the forest for all the trees anymore then. So would be convenient if a service like download_files or download_url could do that on server side so the files would be hidden as _service:* AFAICS services do not have access to previously generated results² though so would have to download those files on every source change which seems rather wasteful and also takes time. OTOH there's a hack in OBS to have a cache directory for tar_scm³ only. So would it be possible to either let services access the previous results or have a cache dir for all? Any other ideas how to handle one thousand source tarballs? cu Ludwig [1] https://github.com/lnussel/nodejs-tarballs [2] https://github.com/openSUSE/osc/blob/7b5d10552352295ebdd21193b6dfbf830e7d23… [3] https://github.com/openSUSE/open-build-service/blob/master/src/backend/run-… -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 10

[opensuse-buildservice] Issue with RSA signing in openSUSE:Factory:RISCV
by Andreas Schwab 12 Oct '20

12 Oct '20

At least since 2020-08-09 RSA signing of kernel modules is broken in openSUSE:Factory:RISCV, producing bad signatures that cannot be verified against the included certificate: $ modsign-verify -v -v --cert-dir etc/uefi/certs sunrpc.ko Signature type: pkcs#7 Signed by: cn=openSUSE Secure Boot CA,serial=1 Hash algorithm: sha256 Trying etc/uefi/certs/188EA6FA.crt Found matching certificate etc/uefi/certs/188EA6FA.crt RSA operation error 140060768991040:error:0407008A:rsa routines:RSA_padding_check_PKCS1_type_1:invalid padding:crypto/rsa/rsa_pk1.c:67: 140060768991040:error:04067072:rsa routines:rsa_ossl_public_decrypt:padding check failed:crypto/rsa/rsa_ossl.c:648: sunrpc.ko: signature validation failed for etc/uefi/certs/188EA6FA.crt sunrpc.ko: bad signature IIUC the signature appears to be created with a private key that doesn't match the public key in etc/uefi/certs/188EA6FA.crt. Since the problem does not occur if the same kernel is built in a different project, there is no fundamental problem with signature creation or verification. The last working kernel was built on 2020-08-01 in o:F:RISCV (which verifies properly using the same certificate). I note that the certificate has a serial number of 1. Isn't that serial number supposed to be unique? 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 6

[opensuse-buildservice] CentOS 8 and CentOS 8 Stream unresolvable state with requiring centos-repos(8)
by Neal Gompa 02 Oct '20

02 Oct '20

Hey all, It looks like CentOS 8 builds are broken now with a "have choice" dependency error for providers of "centos-repos(8)". Please add the following to CentOS-8: Ignore: centos-release:centos-repos Ignore: centos-linux-release:centos-repos(8) For CentOS-8:Stream, add the following: Ignore: centos-release:centos-repos Ignore: centos-stream-release:centos-repos(8) Thanks in advance! -- 真実はいつも一つ！/ 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 7

[opensuse-buildservice] Something drags all OBS workers down ATM..
by Hans-Peter Jansen 24 Sep '20

24 Sep '20

Anybody an idea? Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] Re: Creating initrds with no good reason WAS: Questions about osc
by Hans-Peter Jansen 18 Sep '20

18 Sep '20

Am Freitag, 18. September 2020, 13:19:09 CEST schrieb Franck Bui: > On 9/18/20 12:48 PM, Hans-Peter Jansen wrote: > > -export DISABLE_RESTART_ON_UPDATE=yes > > -%service_del_postun vboxautostart.service > > -%service_del_postun vboxdrv.service > > +%service_del_postun_without_restart vboxautostart.service > > +%service_del_postun_without_restart vboxdrv.service > > > > Franck, while this is a pretty important fix, these macros aren't > > available on Leap. Would you add them for Leap builds, please? > > Yes it's underway now, see https://build.suse.de/request/show/226290. Not accessible from here. Does this fix permeated into openSUSE somewhere? > The request has been accepted so it shouldn't take long but if this can't > wait feel free to revert my changes, I'll resubmit them later. Hey, we are here at work and not on the run, aren't we? > Sorry for the inconvenience. To the contrary, thanks for the fix, Franck. Much appreciated. Have a nice weekend guys, Pete -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

Re: [opensuse-buildservice] Re: [opensuse-factory] Questions about osc
by Larry Finger 18 Sep '20

18 Sep '20

On 9/11/20 3:24 AM, Michal Kubecek wrote: >> That's part of the kmp packaging macro magic, not much the kmp packager >> can do about it. >> >> There is the possibility of doing crazy ugly hacks like >> >> %define regenerate_initrd_posttrans /bin/true\ >> %{nil} >> >> but a bug / feature request against kernel-macros package to give kmp >> packagers an easy and documented way to say "this module will not end up >> on initrd" would be better:-) > But can you ever be sure that it definitely cannot end up in initrd? > How do you e.g. prevent user from putting it into INITRD_MODULES > explicitly? I'm afraid the only safe way would be a dracut feature that > would let you check if it would put a module into initrd based on > current configuration and dependencies. In the VB case, the kmp install section had the following statements: export INITRD_IN_POSTTRANS=1 export KMP_NEEDS_MKINITRD=0 My tests show that inclusion in initrd stopped when these were removed. We will see what results Pete gets when the new version reaches TW. Larry -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] Change realname
by Perry Naseck 18 Sep '20

18 Sep '20

Hello, I have attempted to change my realname with "osc meta user -e <username>" but the changes do not persist. I also cannot find a way to change it from the web interface. Is this functionality possible? Thanks, Perry -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 7

[opensuse-buildservice] Introduce top-level project belatedly and force signing key for project?
by Till Dörges 17 Sep '20

17 Sep '20

Hello all, we're running a private OBS 2.10 instance. We currently have a bunch of projects without a top-level project, i.e. we have <group>:<p1> <group>:<p2> <group>:<p3> but we don't have <group>. >From the old days we also have a global GPG signing key which is still used to sign every RPM for all projects that don't have their own key. Now I'd like to do two things: - introduce the project <group> - manually force the signing key for <group> Will a new project <group> automatically be the parent for <group>:<p1> etc.? I.e. will <group>:<p1> inherit permissions and in particular the signing key? I understand that forcing a signing key is not supported via osc or the WWW interface, but would I get away with manually replacing/setting /srv/obs/projects/<group>.pkg/_signkey /srv/obs/projects/<group>.pkg/_pubkey ? And if so, how do I generate the format for _signkey? For _pubkey it looks quite straight forward. In case you're wondering why we're looking into that. ;-) Newer versions of OBS seem to be quite eager to introduce a new signing key for new projects, AFAICT, if there's no key in any of the top-level projects. The global signing key seems to be ignored. So, when I create <group>:<p4> it will a have a new signing key. But I want it to use the global one. Unfortunately 'osc signkey --delete <group>:<p4>' doesn't seem to work for getting rid of the new key. TIA + HAND -- 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 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] Worker out of disk space - BAD worker
by Radoslav Dibarbora 11 Sep '20

11 Sep '20

Hello, Recently one of my private worker servers run out of disk space. I added more space to /var and restarted all obs services on both worker and OBS side but my builds are still stoped with error that those workers are BAD(waiting for 8 compliant workers (4 of them down) (4 of them bad)). Also I don't want to use workers on OBS server itself but have no idea how to remove them from dispatcher config. Any hint how to cleanup this state? Thanks Dibo -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] packages blocked with "downloading 6 dod packages" since couple of days
by Oliver Kurz 10 Sep '20

10 Sep '20

Since some days https://build.opensuse.org/package/show/devel:openQA/os-autoinst against "openSUSE_Tumbleweed" is blocked with "blocked: downloading 6 dod packages", any clues what to do/click/read/understand next? Anyone else observing this for different projects/packages? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

1 0

[opensuse-buildservice] ensuring build order for nightly builds
by Neels Hofmeyr 09 Sep '20

09 Sep '20

Hi opensuse-buildservice, we're building our Osmocom binary releases and nightly packages using the openSUSE build service. https://build.opensuse.org/project/show/network:osmocom:nightly Today, a user has reported a crash using our nightly package build. It turns out that an ABI incompatibility was introduced in our libosmo-mgcp-client package (from osmo-mgw) yesterday. Everything would be in order if the osmo-msc package had been rebuilt after / using the updated libosmo-mgcp-client package, but apparently the osmo-msc package available in the nightly feed was built using the previous day's libosmo-mgcp-client headers. Thus the feed offered packages that were ABI-incompatible, leading to an obscure crash. Looking at the build timestamps, both builds were apparently started at 1:29 AM, which would explain that the osmo-msc build did not have the finished osmo-mgw build available yet. https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-mgw https://build.opensuse.org/package/show/network:osmocom:nightly/osmo-msc The osmo-msc package's control file includes the line Depends: osmocom-nightly, libosmo-mgcp-client6 (= 1.7.0.89.8667d) which I assume should prevent this from happening. Also, https://en.opensuse.org/openSUSE:Build_Service_FAQ says "The OBS guarantees consistent builds of packages, this means it rebuilds all packages if a depended package did change." What are we doing wrong / should we be doing to improve? Can you help us preventing ABI breakage in our nightly builds? Thanks! ~N -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] SCTP support
by Pau Espin Pedrol 09 Sep '20

09 Sep '20

Hi all, I noticed a few minutes ago that buildhosts seem to be unable to create SCTP sockets. For instance, a call to something like this would fail: fd = socket(AF_INET, SOCK_STREAM, IPPROTO_SCTP); So the socket call is returning -1 and strerror(errno) shows: "Protocol not supported" Which to me means the kernel in use doesn't seem to have sctp built-in or the host is somehow configured to prevent loading it. So now the question is, am I correct with my understanding? And if that's the case, is there any good reason to disable support for SCTP? Having no SCTP support in the kernel means I need to disable some unit tests of the package I'm building (libosmocore), which verify that APIs work well on different distributions (versions) and architectures. PS: Please add me in CC to answers. -- - Pau Espin Pedrol <pespin(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] Questions about osc
by Larry Finger 09 Sep '20

09 Sep '20

A few weeks ago, the virtualbox project was split into two parts - one to build the main packages, and the other to build the kernel modules. I then issued a linkpac command to link them. Shortly after this change was published, it was suggested a multibuild approach would be better, and that was done. All is working mostly OK; however, I have two questions: A standard osc build command works fine, but the kernel modules are not built. OBS does what is expected; however, I would like to save some load on OBS by verifying that the modules will build correctly before uploading changes. What osc build options should I use to build that part of the project? The second question is how to remove the now-dead link to a kmp sub-project? That will save roughly 50% of the OBS build time. Thanks, Larry -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

4 4

[opensuse-buildservice] How to build kernel-default src.rpm after kernel 5.8
by Masaru Nomiya 09 Sep '20

09 Sep '20

Hello, I ususally get 3 src.rpm files from http://download.opensuse.org/repositories/Kernel:/stable/standard/ 1. kerner-source src.rpm 2. kernel-syms src.rpm 3. kernel-default src.rpm and compiles with my config file. Since kernel 5.8, I couldn't compile the kernel-default src.rpm. [...] HOSTCC scripts/kconfig/util.o YACC scripts/kconfig/parser.tab.[ch] HOSTCC scripts/kconfig/preprocess.o HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/expr.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/symbol.o HOSTCC scripts/kconfig/lexer.lex.o HOSTCC scripts/kconfig/parser.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --syncconfig Kconfig + /usr/src/packages/SOURCES/check-for-config-changes .config.orig .config Changes after running `make oldconfig': -# CONFIG_CC_CAN_LINK_STATIC is not set -# CONFIG_DEBUG_INFO_COMPRESSED is not set -# CONFIG_DEBUG_INFO_REDUCED is not set -# CONFIG_DEBUG_INFO_SPLIT is not set -# CONFIG_GDB_SCRIPTS is not set +CONFIG_CC_CAN_LINK_STATIC=y -CONFIG_DEBUG_INFO_BTF=y -CONFIG_DEBUG_INFO_DWARF4=y error: Bad exit status from /var/tmp/rpm-tmp.8lDVlE (%prep) [...] And, in the /var/tmp/rpm-tmp.8lDVlE make $syncconfig $MAKE_ARGS $KERN_DIRS < /dev/null /usr/src/packages/SOURCES/check-for-config-changes .config.orig .config rm .config.orig fi make prepare $MAKE_ARGS make scripts $MAKE_ARGS krel=$(make -s kernelrelease $MAKE_ARGS) if [ "$krel" != "5.8.7-2.1-default" ]; then echo "Kernel release mismatch: $krel != 5.8.7-2.1-default" >&2 exit 1 fi make clean $MAKE_ARGS rm -f source find . ! -type d ! -name 'Module.base' ! -name 'Module.*-kmp' -printf '%P\n' \ > /usr/src/packages/BUILD/kernel-default-5.8.7/obj-files exit $? But, I can compile the kernel's source file. I've got no idea about this difference. What's wrong with me? Could someone give me a clue? THanks --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ Think. -- The IBM slogan -- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 1

[opensuse-buildservice] strange OBS failure "base system is broken"
by Stanislav Brabec 07 Sep '20

07 Sep '20

Hi. I am working on a new util-linux.spec that will replace unreadable multi-spec per-partes build by a single spec file with multibuild and three flavors: mini: Without systemd support. For staging purposes only. standard: Full build of util-linux. python: For all python flavors. Everything is already converted, but I have a problem with util-linux-mini: Local build works. Server side build fails with a broken build root: [ 192s] ... creating baselibs [ 192s] chroot: failed to run command 'su': No such file or directory [ 192s] ### VM INTERACTION START ### [ 195s] [ 189.023976] sysrq: Power Off [ 195s] [ 189.038905] reboot: Power down [ 195s] ### VM INTERACTION END ### [ 195s] [ 195s] lamb20 failed "build util-linux.spec" at Thu Sep 3 01:49:11 UTC 2020. [ 195s] My previous attempt failed with a different error: [ 188s] ... saving built packages [ 188s] swapoff: error while loading shared libraries: libmount.so.1: cannot open shared object file: No such file or directory ... [ 189s] Unable to flush stdout: Text file busy [ 189s] ### VM INTERACTION START ### [ 189s] /.build/build-vm: line 304: echo: write error: Text file busy [ 192s] [ 186.631112] sysrq: Power Off [ 192s] [ 186.638388] reboot: Power down [ 192s] ### VM INTERACTION END ### [ 192s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 192s] or the build host has a kernel or hardware problem... See https://build.opensuse.org/package/live_build_log/home:sbrabec:branches:uti… for a full log. I don't know, why it happens, and all my attempt to prevent it by explicit Requires/Conflicts fail. Please note that the new spec file will require changes in the build of the base system: Either the OBS will prevent util-linux-mini (to prevent dependency on systemd), or affected packages will require util-linux-mini (and full build will need to provide util-linux-mini (to allow live build without build root). Additionally, I have a problem with baselibs.conf. The python flavor cannot build requuested base libs. So I added %if "<name>" == "standard" https://build.opensuse.org/package/view_file/home:sbrabec:branches:util-lin… But it apparently does not work: https://build.opensuse.org/package/live_build_log/home:sbrabec:branches:uti… [ 403s] bad line: %endif The whole package: https://build.opensuse.org/package/show/home:sbrabec:branches:util-linux-mu… Thanks. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.com Křižíkova 148/34 (Corso IIa) tel: +420 284 084 060 186 00 Praha 8-Karlín fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 4

[opensuse-buildservice] Running chroot based OBS worker in kubernetes cluster and how?
by TommyLike Hu 07 Sep '20

07 Sep '20

Hey, guys: I am an infrastructure member from openEuler community (openEuler is an open source, free Linux distribution platform. The platform provides an open community for global developers to build an open, diversified, and architecture-inclusive software ecosystem. [1]), we use OBS for our distribution packaging and releasing. since our worker doesn't utilize any virtualization technologies (at least in worker service, only chroot is used). we are wondering whether we could containerize our obs worker into kubernetes clusters. Within several hours of research, I found there is a guide [2] which utilizes the kubernetes device plugin and announces it's alpha implementation. I reckon this might be a correct direction but still have some questions. 1. Are there any known issues or disadvantages running an obs worker in a container? 2. all of the container images are tagged with unstable (registry.opensuse.org/obs/server/unstable/container/leap151/containers/open… for instance), do we have any official docker images? and where can I get the dockerfile of the image? 3. if we only containerize our obs worker that means we need to route requests from backend back to obs worker via nodeport, therefore we need to update the ip address of the worker to node's. Is there a way to achieve this? Thanks TommyLike [1]: https://openeuler.org/en/ [2]: https://openbuildservice.org/files/manuals/obs-admin-guide.pdf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

2 2

[opensuse-buildservice] Patchinfo usage, downgrading via maintenance process
by Morschhäuser, Mark 07 Sep '20

07 Sep '20

Hi, we made a distribution release with our OBS instance where we included a package in a version that has to be downgraded now. Say we included foo 5.0 in the distribution but want to downgrade to 4.9, codefreeze is passed, project is locked, first distributions are shipped. Can the patchinfo checkbox "Block release?" be used for that? Like creating a maintenance release for foo 5.0 with that checkbox enabled and then create a maintenance release for foo 4.9? I had success with repository priorities but that requires that the software is not yet installed to prefer the lower version. And zypper does not support a "ignore foo >= 5.0" syntax as it seems to ignore certain packages. Best regards, Mark -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner(a)opensuse.org

3 2

[opensuse-buildservice] Problems with the aarch64 workers?
by Julio González Gil 01 Sep '20

01 Sep '20

Or at least I see a lot of Uyuni packages for SLE12 clients failing with: [ 326s] ### WATCHDOG TRIGGERED, KILLING VM ### [ 327s] /var/cache/obs/worker/root_18/root: 7386 [ 327s] qemu-system-aarch64: terminating on signal 15 from pid 23059 () [ 327s] ### VM INTERACTION END ### [ 327s] /var/run/obs/worker/18/build/build-vm: line 465: kill: (7379) - No such process [ 327s] No buildstatus set, either the base system is broken (kernel/initrd/ udev/glibc/bash/perl) [ 327s] or the build host has a kernel or hardware problem... At https://build.opensuse.org/project/show/ systemsmanagement:Uyuni:Master:SLE12-Uyuni-Client-Tools and https:// build.opensuse.org/project/show/systemsmanagement:Uyuni:Master:SLE12-Uyuni- Client-Tools:Build-Dependencies The packages that are failing didn't really change lately (most of all at least), but they got a rebuild because of a changes on SLE12 dependencies) (failures are happening at different workers, but always with the same error, so far I saw 1, 18, 22, 30, 38 and 39 failing). Best regards. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

2 3