[01:07] <bryceh> thanks
=== arraybolt3[m] is now known as arraybolt3[old]
[10:26] <danilogondolfo> may I ask someone to re-trigger this test for me, please? https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=rich&trigger=migration-reference/0
[10:26] <danilogondolfo> just want to confirm the autopkgtests will run this time
[10:28] <ginggs> danilogondolfo: .
[10:28] <danilogondolfo> thanks ginggs
[10:34] <danilogondolfo> I also have a merge request for libcap2, if someone has a minute to review it... for context: there is a single test failing on armhf due to the test environment, it requires a newer kernel version. The test passes on armhf on jammy and newer versions. Once we update the test runners for armhf this change can be dropped.
[10:34] <danilogondolfo> https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libcap2/+git/libcap2/+merge/436832
[11:24] <LocutusOfBorg> danilogondolfo, .
[11:25] <LocutusOfBorg> thanks
[11:27] <danilogondolfo> LocutusOfBorg, thanks!
=== esembee_ is now known as esembee
[15:58] <bdmurray> bluca: Has something changed with the systemd upstream tests? They seem to be hanging / failing at `dpkg-buildpackage: info: binary-only upload (no source included)`
[17:06] <bluca> not that I know of
[17:06] <bluca> things were running today
[17:06] <bluca> yesterday azure apt was borked so lots of stuff failed
[17:06] <bluca> do you have a link?
[17:16] <bdmurray> bluca: the tests never finish but if you look at some of the logs here you can see where they hang https://autopkgtest.ubuntu.com/running#pkg-systemd-upstream
[17:17] <bdmurray> Or here if it got cleared out https://pastebin.ubuntu.com/p/kRc9GPnM8W/
[18:03] <bluca> so after that output, autopkgtest starts
[18:03] <bluca> that's independent of the upstream repo
[18:03] <bluca> it depends on the upstream-ci branch on salsa
[18:04] <bluca> which has not changed since december
[18:04] <bluca> ie, in a working test run you see
[18:04] <bluca> dpkg-buildpackage: info: binary-only upload (no source included)
[18:04] <bluca> autopkgtest [17:53:57]: test timedated: preparing testbed
[18:05] <bluca> while in the output you pasted, it stops after the first line here
[18:05] <bluca> but yes I see that runs are all getting stuck
[18:14] <bdmurray> I've temporarily added systemd-upstream to a list of packages for which tests will not run to help with the backlog of Ubuntu package tests but it looks like the problem is more wide spread.
[18:15] <bdmurray> I'm continuing to investigate and will let you know the end result.
=== JanC is now known as Guest2803
=== JanC_ is now known as JanC
[18:29] <bluca> got it, thanks for looking into this
[23:36] <arraybolt3> Would like to request help with testing this bug fix: https://bugs.launchpad.net/ubuntu/jammy/+source/ubiquity/+bug/1993318
[23:37] -ubottu:#ubuntu-devel- Launchpad bug 1993318 in zfs-linux (Ubuntu) "ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes" [Undecided, Confirmed]
[23:37] <arraybolt3> TL;DR: Boot an Ubuntu Desktop 22.04.1 LTS ISO, enable -proposed, install Ubiquity from -proposed, then do a ZFS+encryption installation and make sure the system works normally when you're done.
[23:37] <arraybolt3> I just verified that the fix worked, but I'm uneasy about saying "OK, the fix is good, ship it!" when I'm the only person who has tested it and logged my findings so far.
[23:38] <arraybolt3> I did mark it as verification-done, but if others can test, that would be great.
[23:39] <arraybolt3> Maybe also test using the Ubuntu Desktop Jammy daily?