[13:38] <juliank> eek E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/lunar/universe/i18n/Translation-en.xz  File has unexpected size (5843040 != 5842848). Mirror sync in progress? [IP: 91.189.91.38 80]
[14:22] <ahasenack> hi SRU team, I sponsored the lunar upload of https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1989100, and somebody else sponsored the kinetic (SRU) upload. Should I refrain from doing the SRU review of that kinetic upload, since I sponsored the lunar one (supposedly the same change)?
[14:22] -ubottu:#ubuntu-devel- Launchpad bug 1989100 in swtpm (Ubuntu Kinetic) "AppArmor DENIES swtpm pid file access" [Undecided, In Progress]
[14:23] <rbasak> ahasenack: I think the principle is that one uploader (of that package) and one SRU team member has reviewed it. I think that'll still hold if you do the SRU review, so IMHO it's fine and would meet the spirit of the rule.
[14:24] <rbasak> one...and one> who are not the same person I mean, of course.
[14:25] <ahasenack> ok
[14:25] <rbasak> Or at least, that's what I try to follow. So there's never a single SRUer landing an SRU on their own without the review of one other qualified person.
[17:52] <bdmurray> I'm with rbasak regarding the libvirt upload
[18:45] <nteodosio> Can I please have this autopkgtest triggered?
[18:45] <nteodosio> https://autopkgtest.ubuntu.com/request.cgi?release=bionic&arch=amd64&package=chromium-browser&ppa=canonical-chromium-builds/stage&trigger=chromium-browser/108.0.5359.71-0ubuntu0.18.04.5
[18:56] <bdmurray> nteodosio: done
[18:57] <nteodosio> thanks
[19:02] <ahasenack> utkarsh2102: hi, did you see the ftbfs on ppc64el in this sru of yours? https://launchpad.net/ubuntu/+source/google-osconfig-agent/20220824.00-0ubuntu1~20.04.1/
[20:25] <mwhudson> cross-toolchain-base: x86_64-linux-gnu-g++-12: fatal error: Killed signal terminated program cc1plus
[20:25] <mwhudson> i guess that's probably oom?
[20:34] <enr0n> Can a core dev please trigger these PPA autopkgtests?
[20:34] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=systemd&ppa=enr0n/systemd&trigger=systemd/252.1-1ubuntu1~ppa20&trigger=policykit-1/122-1
[20:34] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=ppc64el&package=systemd&ppa=enr0n/systemd&trigger=systemd/252.1-1ubuntu1~ppa20&trigger=policykit-1/122-1
[20:40] <bdmurray> mwhudson: I agree
[20:40] <bdmurray> enr0n: doing so
[20:42] <enr0n> bdmurray: thanks!
[22:14] <bdmurray> I've seen a couple of autopkgtest log files with failures to connect to ports.ubuntu.com - I'll be retrying those en masse
[22:24] <mwhudson> bdmurray: https://code.launchpad.net/~mwhudson/autopkgtest-cloud/+git/autopkgtest-package-configs/+merge/433964 if you're around still
[22:30] <bdmurray> mwhudson: its a bit early for me to wander off ;-)
[22:30] <sarnold> but the weather is nice for it..
[22:31] <bdmurray> ha
[22:31] <mwhudson> bdmurray: timezones are hard
[22:33] <bdmurray> merged
[22:41] <mwhudson> bdmurray: thanks. is there a separate deployment step or should i bounce on retry asap?
[22:42] <bdmurray> "This repository contains three files which control how tests for specific
[22:42] <bdmurray> packages are run. It is consumed by autopkgtest-cloud automatically."
[22:42] <mwhudson> thanks