September 2024 - openSUSE Build Service

Publishing mingw64 RPMs
by Roger Oberholtzer 16 Sep '24

16 Sep '24

I have always used the build service to make the Windows versions of software that I generally use in openSUSE. It has worked well. But I now see that RPMs that are building okay are not getting published. I cannot see the reason. At first I thought it was because the BuildArch is noarch, which is what it seems one does for such RPMs. Setting it to x86_64 made no difference. For example: https://build.opensuse.org/package/show/home:rogeroberholtzer:mingw64/mingw… It is only things in this sub-project that are acting this way. I cannot see the difference from other sub-projects that I have. -- Roger Oberholtzer

3 3

Re: Publishing mingw64 RPMs
by Roger Oberholtzer 16 Sep '24

16 Sep '24

On Mon, Sep 16, 2024 at 1:24 PM Jan Engelhardt <ej(a)inai.de> wrote: > > On Monday 2024-09-16 12:07, Roger Oberholtzer wrote: > > >On Mon, Sep 16, 2024 at 11:47 AM Brett Roberson <zalllyn812(a)gmail.com> wrote: > >> > >> I try click link https://build.opensuse.org/package/show/home:rogeroberholtzer:mingw64/mingw6 https://solarsmash.co and it was just as i expected > > > >The build environment is there. But nothing is getting published > >anymore. When accessing the repository via zypper, I now get this: > > solarsmash? Gotta see the spam for the trees. Yeah, I saw that. But my reply about what I see (or more accurately do not see) from OBS for this repository is nonetheless accurate. -- Roger Oberholtzer

1 0

Arch builds broken
by Albert Graef 16 Sep '24

16 Sep '24

These still worked fine until some hours ago. Now I'm suddenly getting this on all my Arch builds: ~~~ [ 12s] booting kvm... [ 12s] ### VM INTERACTION START ### [ 12s] Enabling console input [ 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 -bios /usr/share/qemu/qboot.rom -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0 -object iothread,id=io0 -runas qemu -net none -kernel /boot/kernel.obs.guest -initrd /boot/initrd.obs.guest -append root=/dev/disk/by-id/virtio-0 rootfstype=ext3 rootflags=data=writeback,nobarrier,commit=150,noatime kvmclock mitigations=off elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc oops=panic panic=1 quiet console=ttyS0 init=/.build/build -m 16384 -drive file=/var/cache/obs/worker/root_26/root,format=raw,if=none,id=disk,cache=unsafe,aio=io_uring -device virtio-blk-pci,iothread=io0,drive=disk,serial=0 -drive file=/var/cache/obs/worker/root_26/swap,format=raw,if=none,id=swap,cache=unsafe,aio=io_uring -device virtio-blk-pci,iothread=io0,drive=swap,serial=1 -serial mon:stdio -chardev socket,id=monitor,server=on,wait=off,path=/var/cache/obs/worker/root_26/root.qemu/monitor -mon chardev=monitor,mode=readline -smp 4 [ 13s] [ 0.509328][ T1] systemd[1]: Failed to start Virtual Console Setup. [ 13s] [FAILED] Failed to start Virtual Console Setup. [ 14s] [FAILED] Failed to start Virtual Console Setup. [ 14s] ### VM INTERACTION END ### [ 14s] 2nd stage started in virtual machine ~~~ Looks like the Arch runners are suddenly broken, maybe a bad Arch update? Sample buildlog here: https://build.opensuse.org/package/live_build_log/home:aggraef:test/purr-da… Would be nice if someone could look into this some time. Thanks!

2 1

Same issue, conflict in different file.
by Dmitrii Puzikov 11 Sep '24

11 Sep '24

Hello, Adrian, Year later and here we go again :) Same issue but this time conflict is in _multibuild file. Could you please look at that? Regards, Dmitrii

2 1