Ubuntu 21.10 is due out next week; can that be added soon?
Ubuntu 21.10 is now released: https://discourse.ubuntu.com/t/impish-indri-release-notes/21951
My project https://build.opensuse.org/projects/home:alvistack/meta is now temporarily pointing xUbuntu_21.10 with fake Ubuntu 21.04 repo backend, hopefully an official https://build.opensuse.org/project/show/Ubuntu:21.10 could be available soon ;-)
Wow!!! I found that is now activated (https://build.opensuse.org/project/show/Ubuntu:21.10), thank you very much~~~
On Freitag, 15. Oktober 2021, 01:44:58 CEST Wong Hoi Sing Edison wrote:
Ubuntu 21.10 is now released: https://discourse.ubuntu.com/t/impish-indri-release-notes/21951
My project https://build.opensuse.org/projects/home:alvistack/meta is now temporarily pointing xUbuntu_21.10 with fake Ubuntu 21.04 repo backend, hopefully an official https://build.opensuse.org/project/show/Ubuntu:21.10 could be available soon ;-)
it is configured now and also reachable in the default target list.
Dear Adrian,
Thank you for activating Ubuntu:21.10, but the build still looks not such happy (https://build.opensuse.org/project/monitor/home:alvistack?arch_x86_64=1&...):
nothing provides gcc-11 >= 11.2.0-1~ needed by gcc, (got version 11.1.0-2ubuntu1)
From https://packages.ubuntu.com/impish/gcc it is now showing version with 4:11.2.0-1ubuntu1, so I have no idea why this error message come up...
Regards, Edison Wong
On Freitag, 15. Oktober 2021, 09:59:53 CEST Wong Hoi Sing Edison wrote:
Dear Adrian,
Thank you for activating Ubuntu:21.10, but the build still looks not such happy (https://build.opensuse.org/project/monitor/home:alvistack?arch_x86_64=1&...):
nothing provides gcc-11 >= 11.2.0-1~ needed by gcc, (got version 11.1.0-2ubuntu1)From https://packages.ubuntu.com/impish/gcc it is now showing version with 4:11.2.0-1ubuntu1, so I have no idea why this error message come up...
the mirrors are still syncing ubuntu, you need to wait a bit more ...
Seem mirror site already get updated: http://ftp.halifax.rwth-aachen.de/ubuntu/pool/main/g/gcc-11/cpp-11_11.2.0-7u...
So now we need to wait for https://build.opensuse.org/project/show/Ubuntu:21.10 cache get update, too?
On Freitag, 15. Oktober 2021, 13:16:22 CEST Wong Hoi Sing Edison wrote:
Seem mirror site already get updated: http://ftp.halifax.rwth-aachen.de/ubuntu/pool/main/g/gcc-11/cpp-11_11.2.0-7u...
So now we need to wait for https://build.opensuse.org/project/show/Ubuntu:21.10 cache get update, too?
works for me already in openSUSE:Tools project.
Looks also failed for Ubuntu 21.10 and Ubuntu Next?
https://build.opensuse.org/project/monitor/openSUSE:Tools?arch_x86_64=1&...
On Fri, 15 Oct 2021 13:54:49 +0200 Adrian Schröter adrian@suse.de wrote:
On Freitag, 15. Oktober 2021, 13:16:22 CEST Wong Hoi Sing Edison wrote:
Seem mirror site already get updated: http://ftp.halifax.rwth-aachen.de/ubuntu/pool/main/g/gcc-11/cpp-11_11.2.0-7u...
So now we need to wait for https://build.opensuse.org/project/show/Ubuntu:21.10 cache get update, too?
works for me already in openSUSE:Tools project.
--
I'm getting unresolvable: nothing provides sharutils in https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-devel.
On Fri, 15 Oct 2021 07:34:37 -0500 Rosanne DiMesio dimesio@earthlink.net wrote:
On Fri, 15 Oct 2021 13:54:49 +0200 Adrian Schröter adrian@suse.de wrote:
works for me already in openSUSE:Tools project.
--
Ubuntu 21.10 still shows unresolvable for me: nothing provides shareutils, but Ubuntu does provide sharutils for 21.10 in universe. https://packages.ubuntu.com/impish/sharutils. I do have 21.10 universe added to the repository path.
https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-devel
In my home project I tried adding 21.04 universe as a search path to 21.10 to see what would happen, and it changed the status to blocked at downloading 5 DOD packages, but nothing ever downloaded. Is universe/DOD not working?
On Samstag, 16. Oktober 2021, 13:04:41 CEST Rosanne DiMesio wrote:
On Fri, 15 Oct 2021 07:34:37 -0500 Rosanne DiMesio dimesio@earthlink.net wrote:
On Fri, 15 Oct 2021 13:54:49 +0200 Adrian Schröter adrian@suse.de wrote:
works for me already in openSUSE:Tools project.
Ubuntu 21.10 still shows unresolvable for me: nothing provides shareutils, but Ubuntu does provide sharutils for 21.10 in universe. https://packages.ubuntu.com/impish/sharutils. I do have 21.10 universe added to the repository path.
https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-devel
In my home project I tried adding 21.04 universe as a search path to 21.10 to see what would happen, and it changed the status to blocked at downloading 5 DOD packages, but nothing ever downloaded. Is universe/DOD not working?
there was a broken mirror, I switched now to another one for universe.
On Mon, 18 Oct 2021 09:09:46 +0200 Adrian Schröter adrian@suse.de wrote:
there was a broken mirror, I switched now to another one for universe.
The packages downloaded and the build started, but it failed with:
[ 22s] Booting from ROM... [ 28s] c[?7l[2J[[0;1;31m !! [0m] Failed to e[ 5.269122] systemd[1]: Failed to execute /bin/sh, giving up: No such file or directory [ 28s] xecute /sbin/init [ 28s] [[0;1;31m!!!!!![0m] Failed to e[ 5.273619] systemd[1]: Freezing execution. [ 28s] xecute fallback shell. [ 332s] [ 332s] ### WATCHDOG TRIGGERED, KILLING VM ### [ 333s] /var/cache/obs/worker/root_4/root: 30280 [ 333s] qemu-kvm: terminating on signal 15 from pid 20470 () [ 333s] ### VM INTERACTION END ### [ 333s] /var/run/obs/worker/4/build/build-vm: line 498: kill: (30271) - No such process [ 333s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 333s] or the build host has a kernel or hardware problem...
gave up after 9 failed build attempts...
On Montag, 18. Oktober 2021, 14:57:24 CEST Rosanne DiMesio wrote:
On Mon, 18 Oct 2021 09:09:46 +0200 Adrian Schröter adrian@suse.de wrote:
there was a broken mirror, I switched now to another one for universe.
The packages downloaded and the build started, but it failed with:
[ 22s] Booting from ROM... [ 28s] c[?7l[2J[[0;1;31m !! [0m] Failed to e[ 5.269122] systemd[1]: Failed to execute /bin/sh, giving up: No such file or directory [ 28s] xecute /sbin/init [ 28s] [[0;1;31m!!!!!![0m] Failed to e[ 5.273619] systemd[1]: Freezing execution. [ 28s] xecute fallback shell. [ 332s] [ 332s] ### WATCHDOG TRIGGERED, KILLING VM ### [ 333s] /var/cache/obs/worker/root_4/root: 30280 [ 333s] qemu-kvm: terminating on signal 15 from pid 20470 () [ 333s] ### VM INTERACTION END ### [ 333s] /var/run/obs/worker/4/build/build-vm: line 498: kill: (30271) - No such process [ 333s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 333s] or the build host has a kernel or hardware problem...
and where can I access to the full log and the environment?
On Mon, 18 Oct 2021 15:20:51 +0200 Adrian Schröter adrian@suse.de wrote:
and where can I access to the full log and the environment?
https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-devel
On Montag, 18. Oktober 2021, 15:29:21 CEST Rosanne DiMesio wrote:
On Mon, 18 Oct 2021 15:20:51 +0200 Adrian Schröter adrian@suse.de wrote:
and where can I access to the full log and the environment?
https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-devel
hm, that is some problem with universe. Most likely it requires some more scripts to run the alternative links.
Will have a look in next free minute, but may take some days, sorry :/
Dear Adrian,
The build is now starting but keep failing, too.
As your reference (https://build.opensuse.org/package/live_build_log/home:alvistack/containers-...):
[ 18s] ### VM INTERACTION START ### [ 18s] Using UART console [ 18s] /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -cpu host -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0 -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 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 3072 -drive file=/var/cache/obs/worker/root_2/root,format=raw,if=none,id=disk,cache=unsafe -device virtio-blk-pci,drive=disk,serial=0 -drive file=/var/cache/obs/worker/root_2/swap,format=raw,if=none,id=swap,cache=unsafe -device virtio-blk-pci,drive=swap,serial=1 -serial stdio -chardev socket,id=monitor,server,nowait,path=/var/cache/obs/worker/root_2/root.qemu/monitor -mon chardev=monitor,mode=readline -smp 4 [ 19s] c[?7l[2J[0mSeaBIOS (version rel-1.14.0-0-g155821a-rebuilt.opensuse.org) [ 20s] Booting from ROM... [ 26s] c[?7l[2J[[0;1;31m !! [ 5.396992] systemd[1]: Failed to execute /bin/sh, giving up: No such file or directory [ 26s] [0m] Failed to execute /sbin/init [ 26s] [[0;1;31m!!!!!![0m] Failed[ 5.402287] systemd[1]: Freezing execution. [ 26s] to execute fallback shell. [ 328s] [ 328s] ### WATCHDOG TRIGGERED, KILLING VM ### [ 328s] /var/cache/obs/worker/root_2/root: 9662 [ 328s] qemu-kvm: terminating on signal 15 from pid 13657 () [ 328s] ### VM INTERACTION END ### [ 328s] /var/run/obs/worker/2/build/build-vm: line 498: kill: (9653) - No such process [ 328s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 328s] or the build host has a kernel or hardware problem...
Regards,
Same thing here.
On 10/19/21 6:28 AM, Wong Hoi Sing Edison wrote:
Dear Adrian,
The build is now starting but keep failing, too.
As your reference (https://build.opensuse.org/package/live_build_log/home:alvistack/containers-...):
[ 18s] ### VM INTERACTION START ### [ 18s] Using UART console [ 18s] /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -cpu host -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0 -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 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 3072 -drive file=/var/cache/obs/worker/root_2/root,format=raw,if=none,id=disk,cache=unsafe -device virtio-blk-pci,drive=disk,serial=0 -drive file=/var/cache/obs/worker/root_2/swap,format=raw,if=none,id=swap,cache=unsafe -device virtio-blk-pci,drive=swap,serial=1 -serial stdio -chardev socket,id=monitor,server,nowait,path=/var/cache/obs/worker/root_2/root.qemu/monitor -mon chardev=monitor,mode=readline -smp 4 [ 19s] c[?7l[2J[0mSeaBIOS (version rel-1.14.0-0-g155821a-rebuilt.opensuse.org) [ 20s] Booting from ROM... [ 26s] c[?7l[2J[[0;1;31m !! [ 5.396992] systemd[1]: Failed to execute /bin/sh, giving up: No such file or directory [ 26s] [0m] Failed to execute /sbin/init [ 26s] [[0;1;31m!!!!!![0m] Failed[ 5.402287] systemd[1]: Freezing execution. [ 26s] to execute fallback shell. [ 328s] [ 328s] ### WATCHDOG TRIGGERED, KILLING VM ### [ 328s] /var/cache/obs/worker/root_2/root: 9662 [ 328s] qemu-kvm: terminating on signal 15 from pid 13657 () [ 328s] ### VM INTERACTION END ### [ 328s] /var/run/obs/worker/2/build/build-vm: line 498: kill: (9653) - No such process [ 328s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) [ 328s] or the build host has a kernel or hardware problem...
Regards,
On Freitag, 22. Oktober 2021, 23:43:07 CEST Mark Olesen wrote:
It is building! Thank you to whoever fixed it.
yeah, but please not that you will need new osc and build tooling for local builds.
Not yet released...
On Fri, Oct 22, 2021 at 11:27 PM Adrian Schröter adrian@suse.de wrote:
On Freitag, 22. Oktober 2021, 23:43:07 CEST Mark Olesen wrote:
It is building! Thank you to whoever fixed it.
yeah, but please not that you will need new osc and build tooling for local builds.
Not yet released...
My Ubuntu 21.10 packages built, but aren't getting published. They've been stuck at "Build jobs have been processed, new repository is not yet created" for several hours. Packages that already had repositories created were published quickly.
https://build.opensuse.org/package/show/Emulators:Wine:Debian/vkd3d https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-devel https://build.opensuse.org/package/show/Emulators:Wine:Debian/wine-staging
Release also get stuck for following repo: - https://build.opensuse.org/package/show/openSUSE:Tools/osc - https://build.opensuse.org/project/show/home:alvistack
With the same error message: - Build jobs have been processed, new repository is not yet created
P.S. As a temporarily solution I am now pointing my xUbuntu_21.10 backend as 21.04 and build is working: - https://build.opensuse.org/projects/home:alvistack/meta
On Sonntag, 24. Oktober 2021, 03:03:36 CEST Wong Hoi Sing Edison wrote:
Release also get stuck for following repo:
- https://build.opensuse.org/package/show/openSUSE:Tools/osc
- https://build.opensuse.org/project/show/home:alvistack
With the same error message:
- Build jobs have been processed, new repository is not yet created
P.S. As a temporarily solution I am now pointing my xUbuntu_21.10 backend as 21.04 and build is working:
the debian dpkg tooling is not supporting ubuntu zstd packages yet.
I backported some patch for our package to support it ...
Adrian thank you very much, its all working for xUbuntu_21.10 now ;-)
How about xUbuntu_Next? Could that currently failed due to the same reason for zstd + dpkg?
On Dienstag, 26. Oktober 2021, 00:43:45 CEST Wong Hoi Sing Edison wrote:
Adrian thank you very much, its all working for xUbuntu_21.10 now ;-)
How about xUbuntu_Next? Could that currently failed due to the same reason for zstd + dpkg?
it is not failing for me...
# osc r openSUSE:Tools build -r xUbuntu_Next xUbuntu_Next i586 succeeded xUbuntu_Next x86_64 succeeded
Dear Adrian,
For https://build.opensuse.org/package/show/openSUSE:Tools/osc, Ubuntu 21.10 still show as:
unresolvable: nothing provides dh-python
Regards, Edison Wong
buildservice@lists.opensuse.org
-
Adrian Schröter -
Mark Olesen -
Rosanne DiMesio -
Rosanne DiMesio -
Wong Hoi Sing Edison