[00:11] -queuebot:#ubuntu-release- Packageset: Removed accountsservice from i386-whitelist in hirsute
[00:11] -queuebot:#ubuntu-release- Packageset: Removed appstream from i386-whitelist in hirsute
[00:11] -queuebot:#ubuntu-release- Packageset: Removed gdm3 from i386-whitelist in hirsute
[00:11] -queuebot:#ubuntu-release- Packageset: Removed gnome-desktop3 from i386-whitelist in hirsute
[00:11] -queuebot:#ubuntu-release- Packageset: Removed gnome-settings-daemon from i386-whitelist in hirsute
[00:11] -queuebot:#ubuntu-release- Packageset: Removed libnfsidmap from i386-whitelist in hirsute
[00:11] -queuebot:#ubuntu-release- Packageset: Removed mutter from i386-whitelist in hirsute
[00:11] -queuebot:#ubuntu-release- Packageset: Removed packagekit from i386-whitelist in hirsute
[00:11] -queuebot:#ubuntu-release- Packageset: Removed plymouth from i386-whitelist in hirsute
[00:11] -queuebot:#ubuntu-release- Packageset: Removed xf86-input-wacom from i386-whitelist in hirsute
[00:13] -queuebot:#ubuntu-release- Unapproved: whoopsie (groovy-proposed/main) [0.2.72 => 0.2.72.1] (desktop-core)
[01:11] -queuebot:#ubuntu-release- Packageset: Added libnfsidmap to i386-whitelist in hirsute
[09:50] <xnox> doko:  so i see both autopkgtest & hirsute archive builds are all caught up now......
[09:51] <xnox> doko:  are there things you want to retry? there is a few in arm* columns on http://qa.ubuntuwire.com/ftbfs/
[09:56] <doko> xnox: why? these were given back on Monday
[09:59] <juliank> ppc64el autopkgtests are still playing catchup
[09:59] <juliank> :(
[10:01] <cjwatson> doko: I don't think we need to disable syncs at this point; we got through half the queue yesterday and it's into downgraded PPAs now, so latency should be minimal.
[10:02] <cjwatson> And https://portal.admin.canonical.com/C128394/ is making progress
[10:02] <doko> ok
[10:04] <doko> cjwatson: for the failed builds without build logs, like https://launchpad.net/ubuntu/+source/klayout/0.26.2-3build1 what's the best way to investigate? you had the assumption these were OOM killers?
[10:05] <juliank> Reverse Depends:
[10:05] <juliank>   debomatic,ubuntu-archive-keyring
[10:05] <juliank>   xen-tools,ubuntu-archive-keyring
[10:05] <juliank>   ubuntu-dev-tools,ubuntu-archive-keyring
[10:05] <juliank>   mkosi,ubuntu-archive-keyring
[10:05] <juliank> What's up there? The package name is ubuntu-keyring, should it provide ubuntu-archive-keyring?
[10:06] <juliank> certainly apt-clone fails tests due to using the wrong name, and mkosi's recommends is wrong
[10:07] <juliank> So Debian has ubuntu-archive-keyring, and we don't
[10:08] <juliank> causing extra work
[10:11] <cjwatson> doko: I don't have a meaningful way to investigate: all I can see is that the builder VM stopped responding so LP gave up on it.  Maybe just retry once load is down?
[10:13] <cjwatson> doko: OOM is normally a good guess for that sort of thing, but could also be the build putting the VM under so much load that the launchpad-buildd daemon stops getting any timeslices - that sort of thing
[10:13] <doko> yes, will do. same for gcc-10, llvm-*, libreoffice, zeroc-ice
[10:14] <juliank> Is Xubuntu still alive?
[10:14] <juliank> I've asked them a few cycles ago to fix xubuntu-docs, but nothing happened
[10:15] <juliank> It still build-depends on gnome-doc-utils which hasn't been around sicne bionic, and hence can't be rebuilt
[10:15] <juliank> It really ought to be removed, but it's obviously seeded
[10:21] <seb128> juliank, yes, xubuntu is still active, see discussions yesterday about the ongoing transitions in xfce packages
[10:22] <juliank> how can I get them to fix their docs?
[10:22] <juliank> i want to get this report down to empty: https://magenta.jak-linux.org/ubuntu-archive/distcheck/hirsute/release.txt
[10:22] <juliank> Which is all unsatisfiable build dependencies in release pocket
[10:23] <seb128> you have upload rights, you can fix the package maybe yourself?
[10:23] <seb128> or send a patch
[10:23] <juliank> I think it needs rewriting to get rid of gnome-doc-utils
[10:24] <juliank> notify-osd-icons can't be built either, but notify-osd recommends it :/
[10:25] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (hirsute-proposed) [1.5.1-5]
[10:25] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (hirsute-proposed) [1.5.1-5]
[10:25] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (hirsute-proposed) [1.5.1-5]
[10:32] <seb128> juliank, fix uploaded, it was just a s/python-scour/python3-scour/ to do
[10:33] <juliank> seb128: Same for unity-asset-pool I suppose
[10:33] <seb128> let me check
[10:33] <juliank> seb128: I put unity-lens-photos up for removal in https://bugs.launchpad.net/1905545 as that doesn't have any rdeps
[10:33] -queuebot:#ubuntu-release- Unapproved: fwupd (hirsute-proposed/main) [1.5.1-5build1 => 1.5.1-5build1] (core)
[10:33] <seb128> ack
[10:34] <juliank> edubuntu-menueditor, is edubuntu still around?
[10:34] <juliank> Nothing depends on it, so, meh?
[10:38] -queuebot:#ubuntu-release- Unapproved: fwupd (hirsute-proposed/main) [1.5.1-5build1 => 1.5.1-5build1] (core)
[10:38] <doko> ogra: ^^^
[10:39] <juliank> I collected all removable stuff in https://bugs.launchpad.net/ubuntu/+source/edubuntu-menueditor/+bug/1905545
[10:39] <juliank> I did not add tasks for all the kodi packages, as they're too many
[10:39] <ogra> doko, no idea, if anyone still cares for it, stgraber and highvoltag took over from me ages ago
[10:39] -queuebot:#ubuntu-release- Unapproved: fwupd (hirsute-proposed/main) [1.5.1-5build1 => 1.5.1-5build1] (core)
[10:39] <ogra> doko, but i guess it's rather dead
[10:40] <juliank> hasn't been updated since 2012
[10:40] <juliank> no rdepends, no reverse recommends
[10:40] <juliank> bit of a shame, but yeah
[10:40] <ogra> right and the last release of images for edubuntu was in 2014
[10:41] <ogra> but i'm not sure if they planned to still keep the packages alive and installable
[10:41] <juliank> so I thought britney now dealt with build-depends too
[10:41] <juliank> but arguably we see a lot of stuff in release pocket build-depending on stuff only in proposed
[10:41] <juliank>   * diffoscope                               build-depends on missing libhivex0:amd64 (>= 1.3.14)
[10:42] <juliank>   * libguestfs                               build-depends on missing supermin:amd64 (>= 5)
[10:43] <juliank> I need to talk to La_ney about that once he's back from holidays
[10:43] <doko> I demoted supermin and hivex
[10:43] <juliank> oh
[10:44] <doko> they will migrate again with perl
[10:46] <juliank> doko: Now we get into real trouble, libdts-dev is 0.0.7-1 and libdca-dev is 0.0.7-2, but both are built by src:libdca
[10:46] <juliank> Oh I see libdts-dev was dropped
[10:46] <doko> juliank: what's the problem?
[10:47] <juliank> libdts-dev is NBS
[10:47] <juliank> and
[10:47] <juliank> mythtv build-depends on it
[10:48] <juliank> I thought it was weird archive state, but that makes sense
[11:09] <juliank> Hmm
[11:10] <juliank> I wonder if I should build reports out of the "missing build-depends" that are limited to packages that have no reverse-depends and can hence be removed from the archive
[11:10] <juliank> heck, I feel there should be code to autoremove/demote them
[11:31] -queuebot:#ubuntu-release- New binary: faiss [amd64] (hirsute-proposed/universe) [1.6.5-1] (no packageset)
[11:31] -queuebot:#ubuntu-release- New binary: supysonic [amd64] (hirsute-proposed/universe) [0.6.1+ds-1] (no packageset)
[11:32] -queuebot:#ubuntu-release- New binary: faiss [s390x] (hirsute-proposed/universe) [1.6.5-1] (no packageset)
[11:33] -queuebot:#ubuntu-release- New binary: faiss [ppc64el] (hirsute-proposed/universe) [1.6.5-1] (no packageset)
[12:25] -queuebot:#ubuntu-release- New binary: faiss [arm64] (hirsute-proposed/universe) [1.6.5-1] (no packageset)
[12:27] -queuebot:#ubuntu-release- New binary: faiss [riscv64] (hirsute-proposed/universe) [1.6.5-1] (no packageset)
[12:32] -queuebot:#ubuntu-release- New: accepted faiss [amd64] (hirsute-proposed) [1.6.5-1]
[12:32] -queuebot:#ubuntu-release- New: accepted faiss [ppc64el] (hirsute-proposed) [1.6.5-1]
[12:32] -queuebot:#ubuntu-release- New: accepted faiss [s390x] (hirsute-proposed) [1.6.5-1]
[12:32] -queuebot:#ubuntu-release- New: accepted faiss [arm64] (hirsute-proposed) [1.6.5-1]
[12:32] -queuebot:#ubuntu-release- New: accepted supysonic [amd64] (hirsute-proposed) [0.6.1+ds-1]
[12:32] -queuebot:#ubuntu-release- New: accepted faiss [riscv64] (hirsute-proposed) [1.6.5-1]
[12:48] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (hirsute-proposed) [1.5.1-5build1]
[12:48] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (hirsute-proposed) [1.5.1-5build1]
[12:48] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (hirsute-proposed) [1.5.1-5build1]
[13:14] <seb128> hum, is anyone having an idea why is gloo not autosyncing from Debian?
[13:14] <seb128> it's not mentionned in the autosync log nor in the sync blacklist
[13:15] <seb128> it had existed with a version that is newer than the current Debian one, is that enough to prevent it to come back to the archive?
[15:24]  * juliank is in the process of turning bos01 ppc64el autopkgtest workers back on
[15:34] <juliank> I lied
[15:34] <juliank> We got confused for a bit
[15:50] <bdmurray> vorlon: I ran apport's autopkgtest yesterday for hirsute amd64 w/ all-proposed and the results haven't posted and I wonder where they went.
[15:56] <juliank> bdmurray: Do you have more details?
[15:56] <juliank> bdmurray: Ah, it just started the test 8 minutes ago
[15:56] <juliank> bdmurray: Nov 25 15:47:58 juju-prod-ues-proposed-migration-machine-11 /home/ubuntu/autopkgtest-cloud/worker/worker[30921]: INFO: Received request for package apport on hirsute/amd64; params: {'submit-time': '2020-11-24 20:05:10', 'requester': 'brian-murray', 'all-proposed': '1', 'triggers': ['
[15:57] <bdmurray> juliank: I thought I saw it running yesterday afternoon.
[15:57] <juliank> Nov 24 20:05:10 juju-prod-ues-proposed-migration-machine-11 /home/ubuntu/autopkgtest-cloud/worker/worker[14065]: INFO: Received request for package apport on hirsute/amd64; params: {'triggers': ['gdb/10.1-0ubuntu2'], 'all-proposed': '1', 'requester': 'brian-murray', 'submit-time': '2
[15:57] <juliank> yeah
[15:58] <juliank> WARNING: Saw Temporary failure resolving in log, which is a sign of a temporary failure
[15:58] <juliank> it's been retrying all the time
[15:58] <bdmurray> that sounds less than temporary then
[15:58] <juliank> the tests actually failed, though
[15:58] <juliank> Yeah, like, the tests ran until the end and failed
[15:59] <bdmurray> How could I run apport and gdb both from -proposed? That should pass.
[15:59] <juliank> bdmurray: Here's a log https://paste.ubuntu.com/p/RDS2wGKJh2/
[16:01] <juliank> hmm not sure if that's with apport or just gdb
[16:02] <juliank> bdmurray: FWIW, other runs failed with test_coredump_from_socket failure only
[16:05] <bdmurray> Okay, I'll test it again locally.
[16:06] <juliank> bdmurray: That was the all-proposed one, btw; I scheduled a rerun with just gdb and apport triggers
[16:06] <bdmurray> juliank: thanks
[16:14] <vorlon> juliank: distcheck> edubuntu-menueditor has a potential removal bug filed against it because it's also blocking removal of another package dropped from unstable, if you want to bump that along
[16:14] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-126.129~16.04.1] (kernel)
[16:15] <vorlon> juliank: oh, you already found that bug ;)
[16:15] <juliank> vorlon: I filed a mass removal request today as well that included various packagees like that
[16:15] <juliank> that's bug 1905545
[16:15] <juliank> I did not check for individual package bug duplicates
[16:15] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-126.129] (core, kernel)
[16:15] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-126.129~16.04.1] (kernel)
[16:15] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-126.129] (core, kernel)
[16:16] <juliank> I just need some ubuntu-archive person to remove the packages listed in that bug (the 5 with tasks, and all the kodi addons)
[16:16] <vorlon> eh so now there are three removal bugs open on edubuntu-menueditor. :P
[16:17] <vorlon> juliank: I'd rather you didn't file tasks for unrelated packages on the same bug
[16:17] <juliank> vorlon: I was processing the log of uninstallable build-depends and filed them all as one mass removal bug essentially
[16:17] <juliank> vorlon: Because it's just a lot of packages
[16:18] <juliank> FWIW, I initally only intended to add those that build-depend on python-* to that bug
[16:18] <juliank> I could have split it like that too
[16:19] <juliank> Arguably I can automate the report of packages that can be removed as well
[16:19] <juliank> because it's really just checking if any of the packages in my report have reverse depends in release or proposed
[16:20] <juliank> I can file individual removal bugs, but I figured a mass one would be less noisy
[16:21] <juliank> But I don't want to tear that up now, or file 10 bugs for kodi addons
[16:21] <vorlon> on the contrary, it's more likely to result in jumbled bug history if there are any questions about individual removals
[16:21] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-126.129]
[16:21] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-126.129~16.04.1]
[16:22] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-126.129]
[16:22] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-126.129~16.04.1]
[16:22] <juliank> vorlon: I think writing automated report of uninstallable packages with no rdeps for archive admins to look at is probably more effective than filing individual bug reports mid term
[16:23] <juliank> bdmurray: I think it failed too, but I need to check more closely
[16:23] <juliank> and autopkgtest is broken somewhat
[16:24] <juliank> it's stuck constantly retrying the apport tests
[16:24] <vorlon> 'mp3splt' should be removed just because of the terrible naming
[16:24] <juliank> lol
[16:28] <cjwatson> Vowels are expensive, you know
[16:29] <juliank> vorlon: I'm trying to figure out how to delete the apport autopkgtests from the queue, they continue rerunning, but they're like not on the queue
[16:30] <juliank> because the queues are empty and they get retried immediately and disappear from the queue while I try to get rid of them?
[16:33] <juliank> It's not clear to me why it continues retrying since 20 hours
[16:33] <juliank> it should retry twice
[16:35] -queuebot:#ubuntu-release- Unapproved: cinnamon (focal-proposed/universe) [4.4.8-4 => 4.4.8-4ubuntu0.1] (no packageset)
[16:35] <juliank> does it get put back on the queue after failing the 2nd? time, hence it retries every 20 minutes?
[16:35] <juliank> I'm confused
[16:35] <juliank> I turned off temporary retries for apport for now to get this madness to stop
[16:41] <juliank> doko: ugh I just messed up a bit and deleted a few hundred or so ppc64el tests from the queue
[16:41] <doko> :-/
[16:42] <juliank> from the huge queue
[16:42] <juliank> I thought I had passed -n to filter-amqp, but apparently not :/
[16:43] <juliank> ah no
[16:43] <juliank> not the huge queue the other one
[16:43] <juliank> that one only has 91 requests now
[16:44] <juliank> how do we recover those deleted tests now?
[16:46] <juliank> I found a list: https://paste.ubuntu.com/p/THkD92BXKJ/
[16:47] <doko> I could restore the ones marked as running, triggered by python3-defaults
[16:47] <doko> that list looks more complete
[16:47] <juliank> Yeah it's the backlog grepped for what it deleted
[16:48] <juliank> thanks tmux
[16:48] <juliank> Now just gotta figure out how to inject them back
[17:02] <juliank> doko: All items are back
[17:02] <juliank> I wrote a tool to inject them in the queue, dumped the lines to a file, had the tool parse the file and inject them back in
[17:02] <juliank> phew
[17:11] <juliank> bdmurray: We got a pass
[17:11] <juliank> for apport
[17:12] <doko> juliank: I don't see any gdc-11 dependencies in gcc-snapshot
[17:13] <juliank> doko: no gdc-11 in debian/tests/control?
[17:13] <juliank> debian/tests/control
[17:13] <juliank> 24:Depends: gdc-11
[17:13] <juliank> I see it
[17:13] <doko> ahh, in the tests ...
[17:14] <juliank> Broken autopkgtest-satdep:amd64 Depends on gdc-11:amd64 < none @un H >
[17:14] <juliank> yeah
[17:14] <doko> I should disable all the tests for gcc-snapshot, they don't make any sense
[17:14] <juliank> Or you run them but force-badtest them?
[17:15] <juliank> but that wastes time
[17:17] <juliank> I've also cleaned up all duplicates in the queues
[17:19] <bdmurray> juliank: great!
[17:24] <Odd_Bloke> vorlon: empee3splt?
[17:25] <juliank> If I refer to having split something in the past, that's splat, right? :D
[17:26] -queuebot:#ubuntu-release- New binary: numba [s390x] (hirsute-proposed/universe) [0.51.2-3] (no packageset)
[17:26] <juliank> splat would be a better past participle for split than split
[17:27] <juliank> or well
[17:27] <juliank> split, splat, splut
[17:27] <juliank> I get my pasts confused
[17:28] <juliank> or splitten
[17:29] <juliank> I have splut this string
[17:29] <juliank> I have splitten this string
[17:29] <juliank> I splat this string
[17:29] <juliank> that makes all sense! I demand that change!
[17:30] -queuebot:#ubuntu-release- New binary: paraview [s390x] (hirsute-proposed/universe) [5.9.0~rc1-1] (no packageset)
[17:31] <cjwatson> Heh.  Archaic form "splitted", rare example of a verb apparently getting less regular over time?
[17:32] <cjwatson> Maybe because it's slightly awkward to say
[17:32] <juliank> past participle of sit used to be sitten
[17:33] <juliank> splitted is archaic simple past?
[17:34] <juliank> both?
[17:34] <juliank> World is confusing
[17:34] <juliank> I prefer splat and splut
[17:34] <juliank> those are easy, and inline with swim, swam, swum
[17:50] <cjwatson> both, according to wiktionary anyway
[18:08] -queuebot:#ubuntu-release- New binary: numba [amd64] (hirsute-proposed/universe) [0.51.2-3] (no packageset)
[18:08] -queuebot:#ubuntu-release- Unapproved: cloud-init (groovy-proposed/main) [20.3-15-g6d332e5c-0ubuntu1 => 20.4-3-g6ee01078-0ubuntu1~20.10.1] (core, ubuntu-cloud)
[18:17] -queuebot:#ubuntu-release- New binary: numba [ppc64el] (hirsute-proposed/universe) [0.51.2-3] (no packageset)
[18:39] -queuebot:#ubuntu-release- Unapproved: cloud-init (bionic-proposed/main) [20.3-2-g371b392c-0ubuntu1~18.04.1 => 20.4-0ubuntu1~18.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[18:43] <doko> LocutusOfBorg: please don't work around numba being Python 3.8 only
[18:48] -queuebot:#ubuntu-release- Unapproved: libfprint (groovy-proposed/main) [1:1.90.3+tod1-0ubuntu1 => 1:1.90.3+tod1-0ubuntu2~20.10.1] (ubuntu-desktop)
[18:55] -queuebot:#ubuntu-release- Unapproved: cloud-init (focal-proposed/main) [20.3-2-g371b392c-0ubuntu1~20.04.1 => 20.4-0ubuntu1~20.04.1] (core, edubuntu, ubuntu-cloud)
[19:14] <bdmurray> juliank / vorlon: given that apport and gdb passed together why is gdb still stuck in -proposed?
[19:16] <doko> bdmurray: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#gdb
[19:16] <bdmurray> doko: right but it just passed with ubuntu53 https://autopkgtest.ubuntu.com/packages/a/apport/hirsute/amd64
[19:18] <doko> the gdb triggered an earlier version: autopkgtest for apport/2.20.11-0ubuntu51: amd64: Regression ♻ ,
[19:24] <amurray> rbasak: hey I see you are on SRU vanguard today, I just had a quick question re my iptables update for LP #1904192 in groovy, jdstrand sponsored this for me to groovy-proposed and it's been sitting in unapproved for about a week now - do you know when it might migrate to -proposed? is there anything else I need to do on my side for this or is it just on the SRU team to get around to looking at it?
[19:36] <LocutusOfBorg> doko, ack,  I didn't spot it was python3.8 only
[19:38] <LocutusOfBorg> in any case doko dolfinx without numba is not passing autopkgtests, so meh
[19:40] <doko> that's why it's only in -proposed
[19:40] <rbasak> amurray: it is nominally my shift but I'm out this week, sorry.
[19:41] <rbasak> I expect it's just in the queue, if there's no comment in the bug.
[19:41] <amurray> rbasak: ok no worries - sorry to bother you.. will hit up sil_2100 tomorrow to take a look
[19:54] <vorlon> bdmurray: possibly because the apport test was retriggered with gdb only, and failed, and the two test results were collected by britney at the same time, so the later failure won
[19:54] <vorlon> bdmurray: so retry again with both triggers?
[19:55] <vorlon> bdmurray: oh; but also, both of those results post-date the start of the latest published britney run
[19:55] <vorlon> (because the run started at 16:08, and the passing result came in at 16:40)
[19:56] <bdmurray> okay, I'll try and be patient
[19:57] <bdmurray> amurray: Do you still get that whoopsie crash which Marc fixed?
[19:59] <amurray> bdmurray: no I haven't seen that in a while (although I recall only seeing it a few times at that initial time and not again after even before Marc fixed it...)
[20:08] -queuebot:#ubuntu-release- Unapproved: libfprint (focal-proposed/main) [1:1.90.2+tod1-0ubuntu1~20.04.2 => 1:1.90.2+tod1-0ubuntu1~20.04.3] (desktop-core, ubuntu-desktop)
[20:15] -queuebot:#ubuntu-release- New binary: numba [armhf] (hirsute-proposed/universe) [0.51.2-3] (no packageset)
[20:24] -queuebot:#ubuntu-release- New: accepted numba [amd64] (hirsute-proposed) [0.51.2-3]
[20:24] -queuebot:#ubuntu-release- New: accepted numba [ppc64el] (hirsute-proposed) [0.51.2-3]
[20:24] -queuebot:#ubuntu-release- New: accepted paraview [s390x] (hirsute-proposed) [5.9.0~rc1-1]
[20:24] -queuebot:#ubuntu-release- New: accepted numba [armhf] (hirsute-proposed) [0.51.2-3]
[20:24] -queuebot:#ubuntu-release- New: accepted numba [s390x] (hirsute-proposed) [0.51.2-3]
[20:24] <bdmurray> ss
[20:36] <cyphermox> hey, not sure if it's just me, but I'm having some issues reaching ca.archive.ubuntu.com via IPv6; archive.ubuntu.com works just fine.
[20:36] <cyphermox> stgraber: maybe you're someone who could confirm
[20:39] <stgraber> cyphermox: there have been issues on the US servers following the DC move over the weekend. Things work now if you're coming from HE.net but if you're coming from another provider you may be bounced to the UK on the return path which currently has some kind of PMTU issue.
[20:39] <cyphermox> that would explain what I see, yes
[21:12] <doko> cyphermox: \o/
[21:13] <cyphermox> doko: hey :)
[22:05] <LocutusOfBorg> don't know why gloo is not autosyncd, but meh
[22:05] -queuebot:#ubuntu-release- New sync: gloo (hirsute-proposed/primary) [0.0~git20200918.3dc0328-1]
[22:20] <vorlon> `auto-sync --dry-run --new-only --batch` fails for me with a traceback; possibly related
[22:26] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [20.3-2-g371b392c-0ubuntu1~16.04.1 => 20.4-0ubuntu1~16.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[22:31] <blackboxsw> bdmurray: rbasak or any other sru team member available this week. we have just queued a cloud-init for -proposed for SRU into Xenial, Bionic, Focal and Groovy given the cloud-init SRU process bug #1905599. If someone gets a chance to let that in this week it'd be awesome. if not, we'll pick it up next week
[23:01] <bdmurray> blackboxsw: Could you sru-verify bug 1881632 for focal?
[23:21] -queuebot:#ubuntu-release- New binary: xxdiff [s390x] (hirsute-proposed/none) [1:5.0~b1+git20200622+dfsg-2] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: xxdiff [ppc64el] (hirsute-proposed/none) [1:5.0~b1+git20200622+dfsg-2] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: xxdiff [amd64] (hirsute-proposed/universe) [1:5.0~b1+git20200622+dfsg-2] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: xxdiff [armhf] (hirsute-proposed/universe) [1:5.0~b1+git20200622+dfsg-2] (no packageset)
[23:38] -queuebot:#ubuntu-release- New binary: xxdiff [arm64] (hirsute-proposed/universe) [1:5.0~b1+git20200622+dfsg-2] (no packageset)
[23:41] -queuebot:#ubuntu-release- New: accepted xxdiff [amd64] (hirsute-proposed) [1:5.0~b1+git20200622+dfsg-2]
[23:41] -queuebot:#ubuntu-release- New: accepted xxdiff [armhf] (hirsute-proposed) [1:5.0~b1+git20200622+dfsg-2]
[23:41] -queuebot:#ubuntu-release- New: accepted xxdiff [s390x] (hirsute-proposed) [1:5.0~b1+git20200622+dfsg-2]
[23:41] -queuebot:#ubuntu-release- New: accepted xxdiff [arm64] (hirsute-proposed) [1:5.0~b1+git20200622+dfsg-2]
[23:41] -queuebot:#ubuntu-release- New: accepted xxdiff [ppc64el] (hirsute-proposed) [1:5.0~b1+git20200622+dfsg-2]
[23:50] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (focal-proposed/main) [5.4.0-56.62] (core, kernel)
[23:50] -queuebot:#ubuntu-release- New binary: pynpoint [amd64] (hirsute-proposed/universe) [0.8.3-1] (no packageset)
[23:50] <vorlon> doko: do you have any insight into the z3 build failure on s390x (but not in Debian)? I can't figure out what the missing symbol even is, I've never seen a [0,1] suffix to a templated symbol before
[23:51] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (focal-proposed/main) [5.4.0-56.62] (core, kernel)
[23:51] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (groovy-proposed/main) [5.8.0-31.33] (core, kernel)
[23:51] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (focal-proposed/main) [5.4.0-56.62] (core, kernel)
[23:51] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (groovy-proposed/main) [5.8.0-31.33] (core, kernel)
[23:56] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (focal-proposed/main) [5.4.0-56.62] (core, kernel)
[23:56] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (groovy-proposed/main) [5.8.0-31.33] (core, kernel)
[23:57] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (groovy-proposed/main) [5.8.0-31.33] (core, kernel)