May 2024 - openSUSE Build Service - openSUSE Mailing Lists

Using variables or RPM macros in RemoteAssetUrl?
by Johannes Kastl 31 May '24

31 May '24

Hi all, when building containers, one can use #!RemoteAssetUrl: together with the download_assets service, so OBS downloads the files when uploading a new package version. Very handy, but one thing seems to not work: Can I use variables or RPM macros in the URLs? If so, how? I can use prjconf to set docker build args aka "ARG". Would be great if this worked for the assets, too... Kind Regards Johannes

3 5

Documentation on how to build container images on OBS? BuildTags? Labels?
by Johannes Kastl 29 May '24

29 May '24

Hi all, I wanted to try out building a distrobox image on OBS. I took Richard's repository as a blueprint: > https://build.opensuse.org/project/show/home:RBrownSUSE:containers Is there any documentation on how to use the BuildTags and the labels? Especially if the container images are not supposed to end up in the official repos, but should stay in "my" home namespace? My current state is this, which fails. I am not interested in just solving this error, but would like to know what all of these do and how I should set them for a home-spaced image... > # SPDX-License-Identifier: MIT > #!BuildTag: opensuse/distrobox-johanneskastl:latest > #!BuildTag: opensuse/distrobox-johanneskastl:%%PKG_VERSION%% > #!BuildTag: opensuse/distrobox-johanneskastl:%%PKG_VERSION%%.%RELEASE% > > FROM opensuse/distrobox:latest > LABEL maintainer="Johannes Kastl <opensuse_buildservice(a)ojkastl.de>" > > # labelprefix=org.opensuse.distrobox > PREFIXEDLABEL org.opencontainers.image.title="Distrobox johanneskastl container" > PREFIXEDLABEL org.opencontainers.image.description="Distrobox johanneskastl container" > PREFIXEDLABEL org.opencontainers.image.created="%BUILDTIME%" > PREFIXEDLABEL org.opencontainers.image.version="%%PKG_VERSION%%.%RELEASE%" > PREFIXEDLABEL org.opencontainers.image.vendor="openSUSE Project" > PREFIXEDLABEL org.openbuildservice.disturl="%DISTURL%" > PREFIXEDLABEL org.opensuse.reference="registry.opensuse.org/opensuse/distrobox-johanneskastl:%%PKG_VERSION%%.%REL…" Thanks in advance and have a nice day! Kind Regards, Johannes

4 11

kernel-obs-build: Failed to start
by Matwey V. Kornilov 27 May '24

27 May '24

Hi, I am running a private OBS instance using the Leap 15.5 and following packages: obs-api-2.10.22-150500.118.6.noarch obs-server-2.10.22-150500.118.6.noarch build-20230628-150500.1.4.noarch installed from http://download.opensuse.org/repositories/OBS:/Server:/2.10/15.5/ Some time ago, I've found that all builds for Tumbleweed are broken (while Leap builds work fine) with the following worker error: [ 11s] Detected virtio-serial support [ 11s] QEMU 7.1.0 detected: Skipping iothreads because of bsc#1204082 [ 12s] booting kvm... [ 12s] ### VM INTERACTION START ### [ 12s] Using virtio-serial support [ 12s] /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -cpu host -M pc,accel=kvm,usb=off,dump-guest-core=off,vmport=off -sandbox on -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0 -runas qemu -net none -cpu host,-tsc-deadline -kernel /var/cache/obs/worker/root_1/.mount/boot/kernel -initrd /var/cache/obs/worker/root_1/.mount/boot/initrd -append root=/dev/disk/by-id/virtio-0 rootfstype=ext4 rootflags=noatime kvmclock mitigations=off elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc oops=panic panic=1 quiet console=hvc0 init=/.build/build -m 2048 -drive file=/var/cache/obs/worker/root_1/root,format=raw,if=none,id=disk,cache=unsafe,aio=io_uring -device virtio-blk-pci,drive=disk,serial=0 -drive file=/var/cache/obs/worker/root_1/swap,format=raw,if=none,id=swap,cache=unsafe,aio=io_uring -device virtio-blk-pci,drive=swap,serial=1 -device virtio-serial,max_ports=2 -device virtconsole,chardev=virtiocon0 -chardev stdio,id=virtiocon0 -chardev socket,id=monitor,server=on,wait=off,path=/var/cache/obs/worker/root_1/root.qemu/monitor -mon chardev=monitor,mode=readline -smp 2 [ 16s] [ 2.153215][ T1] systemd[1]: Failed to start Virtual Console Setup. [ 16s] [[0;1;31mFAILED[0m] Failed to start [0;1;39mVirtual Console Setup[0m. [ 17s] [ 2.843774] dracut-pre-udev[294]: sh: line 1: /usr/lib/module-init-tools/unblacklist: No such file or directory [ 19s] [[0;1;31mFAILED[0m] Failed to start [0;1;39mVirtual Console Setup[0m. [ 20s] [[0;1;31mFAILED[0m] Failed to start [0;1;39mSwitch Root[0m. [ 20s] [ 20s] Generating "/run/initramfs/rdsosreport.txt" [ 20s] [ 20s] [ 20s] Entering emergency mode. Exit the shell to continue. [ 20s] Type "journalctl" to view system logs. [ 20s] You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot [ 20s] after mounting them and attach it to a bug report. [ 20s] [ 20s] [ 20s] Press Enter for maintenance This happens both on x86_64 and aarch64 workers. How could I resolve the issue? -- With best regards, Matwey V. Kornilov

2 2

Source validator works on local TW machine, but fails on OBS
by Axel Braun 19 May '24

19 May '24

Hi, I'm having trouble with SR https://build.opensuse.org/request/show/1175051 It claims: Source validator failed. Try "osc service runall source_validator" /usr/lib/obs/service/source_validators/20-files-present-and-referenced: line 98: unzip: command not found zip file bootstrap-4.3.1.zip seems encrypted. This makes source review impossible and hence is forbidden. It works locally: docb@X1E:~/buildservice/home:DocB:Orthanc/orthanc> osc service runall source_validator - package has orthanc-rpmlintrc: (unchanged) docb@X1E:~/buildservice/home:DocB:Orthanc/orthanc> (no error message) and unzip is a build requirement in the spec file. So, everything should be in place. Bug in source_validators? Cheers Axel

1 0

Build failing for container image: no manifest.json file found
by Johannes Kastl 18 May '24

18 May '24

Hi all, I need a second pair of eyes, because I cannot find (or possibly overlook) the reason why this build is failing: > https://build.opensuse.org/package/show/home:ojkastl_buildservice:distrobox… Currently it is blocked (again...), but the last time it built it failed with the very helpful message: "no manifest.json file found" Any hints are highly appreciated... Kind Regards, Johannes

1 0

Delete a published package
by Mathias Radtke 15 May '24

15 May '24

Hi, we have a package that needs to be deleted for specific distros. I already deleted the binaries via API and Web. Publish is also disabled via Web. How can I delete an already published package from the download mirrors? Regards Mathias Mathias Radtke Software Developer uib GmbH Bonifaziusplatz 1B 55118 Mainz E-Mail: m.radtke(a)uib.de <mailto:m.radtke@uib.de> Telefon: +49 6131 27561 0 https://uib.de https://opsi.org Sitz der Gesellschaft: Mainz Handelsregister: Amtsgericht Mainz HRB 6942 Geschäftsführer: Erol Ülükmen USt-IdNr.: DE 203 394 450 Save the Date: opsiConf in Mainz am 09. & 10. Juli 2024! Die Voranmeldung ist bereits eröffnet. opsi.org/opsiconf/

3 2

source service does not work when run server-side
by Dmitry Markov 15 May '24

15 May '24

I have a question that I think is important for you: https://bugzilla.suse.com/show_bug.cgi?id=1218579 in my opinion, this is a question of not only convenience but also the security of the code base. cloning the source code from the original source and vendoring using OBS is an indicator that the source code has not been replaced, which is very important in my opinion. Unfortunately, no one responded to the report for a long time, so I came here. P.S.: forgive me for my low level of English, I hope the translator was able to make my speech more understandable.

2 1

Painfully slow downloads from OBS API leading to Connection broken error
by Atri Bhattacharya 13 May '24

13 May '24

Hi, For the last week or so, perhaps a bit longer, my attempts to branch and work on any OBS package has been hampered by the extremely slow download speeds of files via the API. For example, trying to `osc bco openblas`, I can barely download the patch and spec files (at around 10-20 KiB/s!!!) whereas the downloading of the source tarball itself proceeds at similar snail's pace for a bit and eventually ends with something like: > Connection broken: IncompleteRead(6935464 bytes read, 17469448 more expected) thus making my working dir unusable. I thought this may have been some temporary network issue on my side, but apparently not: I can still `zypper dup` my TW system at ~10 MiB/s consistently, so eventually I came around to the idea that API based downloads when using osc are perhaps hitting a very slow mirror (I have been in India during this time, if that helps). Is there a way to avoid the auto-detection of mirrors for API downloads and specify a particular mirror to use instead? Or, any other workaround to resume branching and working on packages involving large-ish source tarballs — it seems downloading anything beyond a couple of MiB is impossible right now? Thanks in advance. -- Atri

2 1

ERROR: Invalid attribute mode for element service
by Christian 07 May '24

07 May '24

Hi, trying to upload sources to my OBS instance and running into this: Transmitting file data .Server returned an error: HTTP Error 400: Bad Request service validation error: 2:0: ERROR: Invalid attribute mode for element service Uploading same stuff did work here: https://build.opensuse.org/package/show/home:computersalat:devel:scm/gitea So what am I missing on my OBS Instance? The Error message is not really helpful. -- Christian ------------------------------------------------------------ https://join.worldcommunitygrid.org?recruiterId=177038 ------------------------------------------------------------ http://www.sc24.de - Sportbekleidung ------------------------------------------------------------

3 4

Again problems with building RT kernel modules for Leap 15.4
by Florian Pose 07 May '24

07 May '24

Hello, I am referring to https://lists.opensuse.org/archives/list/buildservice@lists.opensuse.org/th… and https://lists.opensuse.org/archives/list/buildservice@lists.opensuse.org/th… A similar problem came up with Leap 15.4 recently in this package: https://build.opensuse.org/package/show/science:EtherLab/ethercat There is a KMP module build against a kernel 5.14.21_150400.15.76: ethercat-kmp-rt-1.5.2.431.g4ad89af_k5.14.21_150400.15.76-lp154.431.1.x86_64.rpm The newest installable kernel on a fresh 15.4 image is 5.14.21-150400.15.62 (thus older) We have added the following repository paths: - SUSE:SLE-15-SP4:Update:Products:SLERT:Update/standard - openSUSE:Leap:15.4/standard If we leave out the first one, it causes packages to be build against a kernel-rt-5.3.18, which is not installable any more. Any ideas? Thanks, Florian

1 0