[06:24] <zhsj> please retry https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=s390x&package=arno-iptables-firewall&trigger=arno-iptables-firewall%2F2.1.1-7 (linux-generic : Depends: linux-image-generic (= 6.1.0.16.16) but 5.19.0.21.21 is to be installed)
[06:26] <ginggs> zhsj: .
[06:39] <zhsj> and https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=lxc&trigger=libselinux%2F3.4-1build4 (FAIL timed out, the log is ended at compiling)
[06:47] <zhsj> dpkg: error processing archive /tmp/apt-dpkg-install-9IkDRS/098-linux-libc-dev_6.1.0-16.16_i386.deb (--unpack):
[06:47] <zhsj>  trying to overwrite shared '/arch/x86/include/generated/asm/.syscalls_32.h.cmd', which is different from other instances of package linux-libc-dev:i386
[06:47] <zhsj> is it bug in linux-libc-dev?
[06:57] <zhsj> so compare to old version linux-libc-dev_5.19.0-21.21, 6.1.0-16.16 is not multi-arch safe. i'm lost why it has files in /arch /install  /scripts
[07:04] <zhsj> anyway, move it bug 2009355
[07:04] -ubottu:#ubuntu-devel- Bug 2009355 in linux (Ubuntu) "linux-libc-dev is no longer multi-arch safe" [Undecided, New] https://launchpad.net/bugs/2009355
[12:11] <ahasenack> morning
[12:11] <ahasenack> checking in for my +1 week shift
[16:05] <rbasak> !dmb-ping
[16:06] <ahasenack> stgraber: fyi, a vm launched with `lxc launch ubuntu-daily:lunar l1 --vm` gets stuck on a grub error about "bad shim signature"
[16:06] <ahasenack> probably a lunar bug
[16:08] <danilogondolfo> May I ask someone to retry this test for me, please? https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=amd64&package=netplan.io&trigger=netplan.io/0.105-0ubuntu2~22.04.3
[16:09] <ginggs> danilogondolfo: .
[16:09] <danilogondolfo> thank you ginggs
[16:13] <coreycb> schopin: are you planning to backport new versions of rust to jammy through the next LTS? I ask because the jammy-based cloud archives need python-cryptography which uses rust and there are several rust libraries that we'll need to backport from the next few releases of ubuntu to jammy.
[16:14] <stgraber> ahasenack: yeah, we had another report of that earlier
[16:14] <stgraber> ahasenack: sounds like a shim/kernel signature mismatch of some kind
[16:14] <stgraber> ahasenack: LXD itself just ships with the MS key loaded, no Ubuntu specific stuff in there
[16:14] <stgraber> ahasenack: you can force it with security.secureboot=false
[16:15] <stgraber> ahasenack: but obviously this needs fixing by CPC or foundations/kernel
[16:19] <ahasenack> stgraber: thanks, I'll try that
[16:31] <vorlon> stgraber, ahasenack: shim-signed was wrongly promoted to the lunar release pocket before corresponding kernels were ready.  It's been rolled back *and* new kernels have been promoted (so this won't be an issue going forward with any of the common images but if it mispromoted again it would still be an issue right now for the public cloud images due to separate kernel builds), so once there's a new
[16:31] <vorlon> image build the problem goes away.  CPC team knows
[16:43] <stgraber> thanks
[16:49] <jchittum> hm, we've started seeing issues with testing since the kernel update. getting the fun "go check livecd-rootfs if there are kernel capability mismatches with snapd"
[16:50] <jchittum> which is delaying publishing new lunar images. lemme dig a bti
[18:19] <ahasenack> I'm troubleshooting the `crash` DEP8 failures. I have never used that app before.
[18:19] <ahasenack> the lunar VM doesn't have /proc/kcore, that seems relevant
[18:19] <ahasenack> when this is run: crash -st /usr/lib/debug/boot/vmlinux-$(uname -r)
[18:19] <ahasenack> it outputs "crash: /proc/kcore: No such file or directory"
[18:19] <ahasenack> is that a change in the running kernel, or something else is going on?
[18:20] <ahasenack> # grep KCORE /boot/config-5.19.0-1008-kvm
[18:20] <ahasenack> # CONFIG_PROC_KCORE is not set
[18:20] <ahasenack> hm
[19:51] <vpa1977> Hi, would it be possible to review 'sparse' FTBS fix: https://code.launchpad.net/~vpa1977/ubuntu/+source/sparse/+git/sparse/+merge/438408
[19:51] <vpa1977> We have migrated to LLVM 15 but never updated this package to be compatible
[20:38] <sergiodj> hi, I'm trying to find out why Ubuntu chose to use -O3 when compiling stuff on ppc64el
[20:40] <sergiodj> is there any mailing list thread or something where a discussion happened regarding this change?
[20:42] <sergiodj> I found the changelog for this on dpkg, written by cjwatson.  I wonder if the rationale still applies
[20:45] <sergiodj> something to play with on a rainy afternoon, I guess...
[20:57] <vpa1977> Hi I am wondering if it is possible to retry some of the openjdk migrations:
[20:57] <vpa1977> OpenJDK -8
[20:57] <vpa1977> Infrastructure issues:
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=openjdk-8&trigger=ca-certificates-java%2F20230103ubuntu1
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=libreoffice&trigger=openjdk-8%2F8u362-ga-0ubuntu2
[20:57] <vpa1977> Known flaky tests:
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=jsurf-alggeo&trigger=openjdk-8%2F8u362-ga-0ubuntu2
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=openjdk-8&trigger=openjdk-8%2F8u362-ga-0ubuntu2
[20:57] <vpa1977> OpenJDK -11
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=openjdk-lts&trigger=ca-certificates-java%2F20230103ubuntu1
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=libsis-jhdf5-java&trigger=openjdk-lts%2F11.0.18%2B10-0ubuntu3
[20:57] <vpa1977> OpenJDK -17
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=jsurf-alggeo&trigger=openjdk-17%2F17.0.6%2B10-1ubuntu1
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=libreoffice&trigger=openjdk-17%2F17.0.6%2B10-1ubuntu1
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=libsis-jhdf5-java&trigger=openjdk-17%2F17.0.6%2B10-1ubuntu1
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=s390x&package=natbraille&trigger=openjdk-17%2F17.0.6%2B10-1ubuntu1
[20:57] <vpa1977> OpenJDK 18:
[20:57] <vpa1977> Known flaky test, patch sent to debian
[20:57] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=jsurf-alggeo&trigger=openjdk-18%2F18.0.2%2B9-2ubuntu1
[20:57] <vpa1977> Kernel was not found
[20:58] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=libreoffice&trigger=openjdk-18%2F18.0.2%2B9-2ubuntu1
[20:58] <vpa1977> Test bed did not boot
[20:58] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=libreoffice&trigger=openjdk-18%2F18.0.2%2B9-2ubuntu1
[20:58] <vpa1977> OpenJDK-20
[20:58] <vpa1977> test bed did not boot:
[20:58] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=fdroidserver&trigger=openjdk-20%2F20%7E36ea%7Eus1-0ubuntu1
[20:58] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=fdroidserver&trigger=openjdk-20%2F20%7E36ea%7Eus1-0ubuntu1
[20:58] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=libsis-jhdf5-java&trigger=openjdk-20%2F20%7E36ea%7Eus1-0ubuntu1
[20:58] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=libsis-jhdf5-java&trigger=openjdk-20%2F20%7E36ea%7Eus1-0ubuntu1
[20:58] <vpa1977> OpenJDK 21
[20:58] <vpa1977> Kernel was not found
[20:58] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=libreoffice&trigger=openjdk-21%2F21%7E7ea-1ubuntu1
[20:58] <vpa1977> And OpenJDK -19 needs all s390x retried due to missing kernel image
[21:11] <enr0n> Can a core dev please retry this test? https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=zfs-linux&trigger=systemd%2F252.5-2ubuntu1
[21:14] <mwhudson> vpa1977: clicked but not sure irc is the best place for a list like that
[21:14] <mwhudson> enr0n: done
[21:14] <vpa1977> mwhudson: apologies. realised it halfway through the list
[21:14] <vpa1977> Should I use pastebin for massive retries like this ?
[21:15] <enr0n> mwhudson: thanks
[21:15] <mwhudson> vpa1977: not sure, links in pastebin aren't clickable usually?
[21:16] <mwhudson> probably still a decent option
[21:17] <vorlon> sergiodj: it's by agreement with the partner (IBM).
[21:20] <vorlon> vpa1977, mwhudson: fwiw I generally won't click any retry links but instead expect to work out a translation to a retry-autopkgtest-regressions command, because I find those easier to read/comprehend
[21:21] <vorlon> (also, retry-autopkgtest-regressions does duplicate detection)
[21:22] <vorlon> dbungert: https://people.canonical.com/~ubuntu-archive/proposed-migration/lunar_uninst.txt very nice
[21:22] <dbungert> vorlon: :)
[21:29] <sergiodj> vorlon: thanks