[06:53] <vorlon> Laney: should I open an RT about getting nusakan shut down?  I'm speculating, but given that RT #127318 had to be reopened about http://old-releases.ubuntu.com/releases/18.04.4 being absent, I think some machines are still incorrectly syncing from it under some circumstances
[08:09] <Laney> vorlon: I thought it was going to be shortly after we cut over to be honest, so fine by me. But does that RT indicate that one of the frontends has stale config, then? It would be good to confirm, because shutting nusakan down would then just prevent it from being able to rsync from *anywhere*.
[08:12] <Laney> https://paste.ubuntu.com/p/6p266zKyZT/
[08:12] <Laney> It looks like none of the frontends have 18.04.4
[08:50] <vorlon> Laney: yeah, I checked that already, they're all missing it, and this is a regression
[08:51] <vorlon> syncing from nusakan is worse than syncing from nowhere
[08:51] <Laney> vorlon: OK, I think that needs investigating by an IS person who can trace from a frontend
[08:51] <Laney> It's fine to make it error, if that is what's happening
[08:51]  * vorlon nods
[08:51] <Laney> But it'll still need fixing anyway
[09:13] <vorlon> cjwatson: do you see any reason to continue producing https://people.canonical.com/~ubuntu-archive/testing/groovy_probs.html (et al)? the rptprobs.py doesn't handle versioned provides so has a ton of false-positives, and I don't think there's anything on there not addressed by a combination of https://people.canonical.com/~ubuntu-archive/proposed-migration/groovy_uninst.txt and component-mismatches
[09:14] <vorlon> cjwatson: and I think https://people.canonical.com/~ubuntu-archive/testing/groovy_outdate.html is broken, because I've not seen it be non-zero in a while and I think that's false
[09:14] <vorlon> (I just picked up at least one arch-specific out-of-date binary from groovy release this evening)
[09:39] <cjwatson> vorlon: I have no very great attachment to it if you don't
[09:39] <Laney> why are we starting to see "/tmp/autopkgtest-run-wrapper: command not found" now?
[09:57] -queuebot:#ubuntu-release- Unapproved: accepted cifs-utils [source] (focal-proposed) [2:6.9-1ubuntu0.1]
[10:20] -queuebot:#ubuntu-release- Unapproved: accepted cifs-utils [source] (bionic-proposed) [2:6.8-1ubuntu1.1]
[10:27] <rbalint> sil2100, could you please merge https://code.launchpad.net/~rbalint/britney/hints-ubuntu/+merge/390633 for systemd?
[10:55] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (xenial-proposed) [1.361.6]
[12:09] -queuebot:#ubuntu-release- New source: pibootctl (groovy-proposed/primary) [0.5.2-0ubuntu1]
[12:46] -queuebot:#ubuntu-release- New source: sup-mail (focal-proposed/primary) [1.0-3~0ubuntu20.04.1]
[12:46] <ahasenack> hi release team, just a ping for two adcli FFes when you have a moment: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1868703 (the adcli task in lp is "buggy"), and https://bugs.launchpad.net/ubuntu/+source/adcli/+bug/1893784
[13:08] <ahasenack> hi, can we edit https://discourse.ubuntu.com/t/groovy-gorilla-release-notes/15533/1 ? I'm logged in, but don't see an edit button, might not have permission
[13:08] <ahasenack> or is this not the right place, and I should look for the upcoming release notes in the ubuntu wiki?
[13:38] <Laney> ahasenack: perhaps popey can help add you, we are waiting on IS to help us add everyone automatically, but that ticket hasn't seen action :(
[13:38] <popey> hello!
[13:39] <popey> ahasenack do you not see an edit button at the bottom?
[13:40] <popey> ahasenack refresh, it should now be there?
[13:47] -queuebot:#ubuntu-release- Unapproved: accepted gdb [sync] (focal-proposed) [9.2-0ubuntu1~20.04]
[13:48] <dosaboy> rbasak: hi, ive updated the regression potentional in https://bugs.launchpad.net/cloud-archive/+bug/1891673, is there anything else needed from me?
[13:59] -queuebot:#ubuntu-release- Unapproved: accepted python3.8 [sync] (focal-proposed) [3.8.5-1~20.04]
[14:00] <ahasenack> popey: sorry, was otp, trying now
[14:00] <ahasenack> popey: I see the edit now, thanks!
[14:24] -queuebot:#ubuntu-release- Unapproved: accepted python3-stdlib-extensions [sync] (focal-proposed) [3.8.5-1~20.04.1]
[14:26] -queuebot:#ubuntu-release- Unapproved: rejected mutter [source] (focal-proposed) [3.36.6-1ubuntu0.20.04.1]
[14:40] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (focal-proposed/main) [5.4.0-49.53] (core, kernel)
[14:40] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (focal-proposed/main) [5.4.0-49.53] (core, kernel)
[14:41] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (focal-proposed/main) [5.4.0-49.53] (core, kernel)
[14:41] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (focal-proposed/main) [5.4.0-49.53] (core, kernel)
[15:25] -queuebot:#ubuntu-release- Unapproved: thermald (focal-proposed/main) [1.9.1-1ubuntu0.2 => 1.9.1-1ubuntu0.3] (core)
[15:38] -queuebot:#ubuntu-release- Unapproved: accepted gcc-10-cross [sync] (focal-proposed) [6ubuntu3]
[15:38] <seb128> could anyone remind me if there is a log somewhere of the proposed-by-team report?
[15:39] <seb128> the page failed to update since this morning
[15:46] <Laney> seb128: it's generated after the main run, so you can see the log in the same place e.g. https://people.canonical.com/~ubuntu-archive/proposed-migration/log/groovy/2020-09-21/13:37:04.log
[15:46] <Laney> this might be related to what vorlon was asking cjwats_n about this morning?
[15:52] -queuebot:#ubuntu-release- Unapproved: yaru-theme (focal-proposed/main) [20.04.8 => 20.04.9] (desktop-core)
[15:54] -queuebot:#ubuntu-release- Unapproved: accepted gcc-10-cross-ports [sync] (focal-proposed) [5ubuntu2]
[15:56] <seb128> Laney, could be I guess, I don't understand the problem enough to say but I will wait to see if things sort out
[15:57] <seb128> also unsure what the ood report is and if we should continue to the next reports when that one is failing maybe? (I see no mention of 'team' in the log so I assume it errored out before that part of the update)
[15:59] <Laney> maybe, but I think "don't crash" is also a defensible position
[16:05] <Laney> I'll do the simple fix
[16:05] <Laney> but I'm not sure that it is actually correct
[16:10] <Laney> "it" meaning the contents of the report
[16:19] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9-cross [sync] (focal-proposed) [21ubuntu4]
[16:20] <rbalint> Laney, sshguard should be switched to use nftables dropping the Ubuntu delta to complete the nftables migration, should i file a formal ffe or i can just upload it?
[16:21] -queuebot:#ubuntu-release- Unapproved: accepted gcc-9-cross-ports [sync] (focal-proposed) [18ubuntu4]
[16:23] <Laney> rbalint: If you file an FFe I'll ask you "how have you tested this?", so if you want to answer that here instead then no bug required :-)
[16:27] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (focal-proposed) [5.4.0-49.53]
[16:27] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (focal-proposed) [5.4.0-49.53]
[16:27] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (focal-proposed) [5.4.0-49.53]
[16:27] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (focal-proposed) [5.4.0-49.53]
[16:33] <rbalint> Laney, it was just rebuilt with switched iptables and since this is dropping the Ubuntu delta only i'm confident that it works and also fixes LP: #1877615
[16:33] <rbalint> Laney, but given that it became late i give it a round of testing, too
[16:46] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-119.120] (core, kernel)
[16:46] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-119.120] (core, kernel)
[16:50] <Laney> rbalint: OK, I'm not given confidence by the first statement (building only), but the second one I am - so go ahead
[16:54] <bdmurray> sil2100: With regards to upgrades to 20.04.1 bug 1894919 was the one we were trying to fix before turning them on. However, the fix doesn't completely resolve the issue - there are still autoremovable packages after the upgrade.
[16:55] <bdmurray> sil2100: So I'm looking for a 2nd opinion on how to proceed.
[17:08] <rbalint> bdmurray, can we please add LP: #1871240 as a blocker ? glibc in focal-proposed fixes it and it is ready for release afact
[17:09] <rbalint> bdmurray, the original but i pasted is all upgrades to focal are broken on wsl1
[17:11] <bdmurray> rbalint: from bionic and eoan?
[17:11] <rbalint> bdmurray, yes
[17:13] <bdmurray> rbalint: okay, I'll make sure that's fixed
[17:13] <rbalint> bdmurray, thanks!
[17:17] <rbasak> dosaboy: what about the status of the fix for Groovy?
[19:40] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-119.120]
[19:40] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-119.120]
[20:35] -queuebot:#ubuntu-release- Unapproved: base-files (focal-proposed/main) [11ubuntu5.2 => 11ubuntu5.3] (core, i386-whitelist)
[20:37] -queuebot:#ubuntu-release- Unapproved: base-files (bionic-proposed/main) [10.1ubuntu2.10 => 10.1ubuntu2.11] (core)
[20:42] -queuebot:#ubuntu-release- Unapproved: base-files (xenial-proposed/main) [9.4ubuntu4.13 => 9.4ubuntu4.14] (core)
[21:04] <vorlon> Laney: yep sorry, looks like I broke britney by trying to turn on the ood_report, should be fixed now
[21:06] <vorlon> Laney: (per your commit)
[21:25] <vorlon> Laney: I'm very confused by meta-gnome3 having just (afair) shown up on https://people.canonical.com/~ubuntu-archive/proposed-migration/groovy_uninst.txt for s390x; or how the package even got into such a state since the gdm3 binary package was consistently unavailable on s390x since before focal
[22:39] <xnox> i thought sometime else provided that on s390x before
[22:39] <xnox> *something
[22:39] <xnox> vorlon:  also, please vacation =)
[22:40] -queuebot:#ubuntu-release- New binary: gst-plugins-bad1.0 [s390x] (groovy-proposed/universe) [1.18.0-2ubuntu1] (i386-whitelist, kubuntu)
[22:41] -queuebot:#ubuntu-release- New binary: gst-plugins-bad1.0 [i386] (groovy-proposed/universe) [1.18.0-2ubuntu1] (i386-whitelist, kubuntu)
[22:41] -queuebot:#ubuntu-release- New binary: gst-plugins-bad1.0 [ppc64el] (groovy-proposed/universe) [1.18.0-2ubuntu1] (i386-whitelist, kubuntu)
[22:46] -queuebot:#ubuntu-release- Unapproved: torbrowser-launcher (focal-proposed/universe) [0.3.2-9 => 0.3.2-9ubuntu1] (no packageset)
[22:58] -queuebot:#ubuntu-release- New binary: gst-plugins-bad1.0 [amd64] (groovy-proposed/universe) [1.18.0-2ubuntu1] (i386-whitelist, kubuntu)
[23:06] -queuebot:#ubuntu-release- New binary: gst-plugins-bad1.0 [armhf] (groovy-proposed/universe) [1.18.0-2ubuntu1] (i386-whitelist, kubuntu)