osc build fails locally
Hi, I'm struggling with an issue on osc build for which I have no idea what's going on. There is a debian package created from orig.tar.gz, debian.tar.xz and .dsc, the build on the backend works, a local build like this: osc build xUbuntu_22.04 x86_64 fails with fetching packages for 'ubuntu:22.04': | Elapsed Time: 0:00:18 /tmp/osc_build_filedxongqro: missing control.tar What does this error message mean ? The distribution (jammy) was imported as DoD to obs and as I said the build works on the backend. Any pointer would be helpful, thanks Regards, Marcus -- Public Key available via: https://keybase.io/marcus_schaefer/key.asc keybase search marcus_schaefer ------------------------------------------------------- Marcus Schäfer Am Unterösch 9 Tel: +49 7562 905437 D-88316 Isny / Rohrdorf Germany -------------------------------------------------------
On Mon, Feb 21, 2022 at 2:16 PM Marcus Schäfer
Hi,
I'm struggling with an issue on osc build for which I have no idea what's going on. There is a debian package created from orig.tar.gz, debian.tar.xz and .dsc, the build on the backend works, a local build like this:
osc build xUbuntu_22.04 x86_64
fails with
fetching packages for 'ubuntu:22.04': | Elapsed Time: 0:00:18 /tmp/osc_build_filedxongqro: missing control.tar
What does this error message mean ?
The distribution (jammy) was imported as DoD to obs and as I said the build works on the backend.
Any pointer would be helpful, thanks
It means that the deb archive format changed again and OBS can't handle it. I believe Ubuntu switched to zstd tarballs inside of the deb ar archive, rather than xz as they were previously using. We probably don't support deb+zstd yet. I hit this problem in the past when developing the Ubuntu build environment configurations for OBS, so I'm pretty sure this is the case again. :) -- 真実はいつも一つ!/ Always, there's only one truth!
Hi,
It means that the deb archive format changed again and OBS can't handle it. I believe Ubuntu switched to zstd tarballs inside of the deb ar archive, rather than xz as they were previously using. We probably don't support deb+zstd yet.
Yes you are probably right. In 22.04 the compression format is zstd and dpkg (without patching) is not able to read it. I added Ubuntu 21.04 as a repository to circumvent this issue and now I get a bit further: osc build --vm-type=kvm xUbuntu_21.04 x86_64 ends with: ---------- [ 3s] Using UART console [ 3s] /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -cpu host -object rng-random,filename=/dev/hwrng,id=rng0 -device virtio-rng-pci,rng=rng0 -runas qemu -net none -kernel /boot/vmlinuz -initrd /boot/initrd -append root=/dev/sda rootfstype=ext3 rootflags=data=writeback,nobarrier,commit=150,noatime ext4.allow_unsupported=1 mitigations=off panic=1 quiet no-kvmclock elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc console=ttyS0 init=/.build/build -m 512 -drive file=/var/tmp/build-root/img,format=raw,if=none,id=disk,cache=unsafe -device ide-hd,drive=disk,serial=0 -drive file=/var/tmp/build-root/swap,format=raw,if=none,id=swap,cache=unsafe -device ide-hd,drive=swap,serial=1 -serial stdio -chardev socket,id=monitor,server,nowait,path=/var/tmp/build-root/img.qemu/monitor -mon chardev=monitor,mode=readline -smp 8 [ 3s] qemu: could not open kernel file '/boot/vmlinuz': No such file or directory [ 3s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 3s] or the build host has a kernel or hardware problem... -------- ok no kernel I thought, let's add one osc build -x linux-generic --vm-type=kvm xUbuntu_21.04 x86_64 this ends with the same error last I tried osc build -x kernel-obs-build --vm-type=kvm xUbuntu_21.04 x86_64 and that ends with ---- buildinfo is broken... it says: unresolvable: nothing provides kernel-obs-build ---- yeah expected, nobody ever build kernel-obs-build for Debian btw, why ? obs offers support for building packages and images and somehow works on the backend I spent the entire day to find some method to let obs do what it can do on the backend just locally but no luck at all Any idea how to make this work ? Thanks much Regards, Marcus -- Public Key available via: https://keybase.io/marcus_schaefer/key.asc keybase search marcus_schaefer ------------------------------------------------------- Marcus Schäfer Am Unterösch 9 Tel: +49 7562 905437 D-88316 Isny / Rohrdorf Germany -------------------------------------------------------
On Montag, 21. Februar 2022, 23:00:00 CET Marcus Schäfer wrote:
Hi,
It means that the deb archive format changed again and OBS can't handle it. I believe Ubuntu switched to zstd tarballs inside of the deb ar archive, rather than xz as they were previously using. We probably don't support deb+zstd yet.
Yes you are probably right. In 22.04 the compression format is zstd and dpkg (without patching) is not able to read it.
I added Ubuntu 21.04 as a repository to circumvent this issue and now I get a bit further:
osc build --vm-type=kvm xUbuntu_21.04 x86_64
ends with:
---------- [ 3s] Using UART console [ 3s] /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -cpu host -object rng-random,filename=/dev/hwrng,id=rng0 -device virtio-rng-pci,rng=rng0 -runas qemu -net none -kernel /boot/vmlinuz -initrd /boot/initrd -append root=/dev/sda rootfstype=ext3 rootflags=data=writeback,nobarrier,commit=150,noatime ext4.allow_unsupported=1 mitigations=off panic=1 quiet no-kvmclock elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc console=ttyS0 init=/.build/build -m 512 -drive file=/var/tmp/build-root/img,format=raw,if=none,id=disk,cache=unsafe -device ide-hd,drive=disk,serial=0 -drive file=/var/tmp/build-root/swap,format=raw,if=none,id=swap,cache=unsafe -device ide-hd,drive=swap,serial=1 -serial stdio -chardev socket,id=monitor,server,nowait,path=/var/tmp/build-root/img.qemu/monitor -mon chardev=monitor,mode=readline -smp 8 [ 3s] qemu: could not open kernel file '/boot/vmlinuz': No such file or directory [ 3s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 3s] or the build host has a kernel or hardware problem... --------
ok no kernel I thought, let's add one
osc build -x linux-generic --vm-type=kvm xUbuntu_21.04 x86_64
this ends with the same error
last I tried
osc build -x kernel-obs-build --vm-type=kvm xUbuntu_21.04 x86_64
and that ends with
---- buildinfo is broken... it says: unresolvable: nothing provides kernel-obs-build ----
yeah expected, nobody ever build kernel-obs-build for Debian btw, why ? obs offers support for building packages and images and somehow works on the backend
I spent the entire day to find some method to let obs do what it can do on the backend just locally but no luck at all
Any idea how to make this work ?
As you wrote, best would be to fix the build of
OBS:DefaultKernel kernel-obs-build
as debian package.
--
Adrian Schroeter
participants (3)
-
Adrian Schröter
-
Marcus Schäfer
-
Neal Gompa