[00:00] -queuebot:#ubuntu-release- New binary: qgis [s390x] (eoan-proposed/universe) [3.4.7+dfsg-1] (no packageset)
[00:12] -queuebot:#ubuntu-release- New binary: qgis [i386] (eoan-proposed/universe) [3.4.7+dfsg-1] (no packageset)
[00:18] -queuebot:#ubuntu-release- New binary: qgis [ppc64el] (eoan-proposed/universe) [3.4.7+dfsg-1] (no packageset)
[00:21] <teward> vorlon: indeed, I didn't expect it to hit that quickly though, and I'm assuming it'll happen again.  I'll keep checking back on nginx and the autopkgtests it triggers and keep an eye on more regressions due to that intermittent issue.
[00:21] <teward> if it continues TOO much then I'll probably drop by the canonical sysadmin channel and see if they can dig into it more.
[00:22] <teward> (though I'm sure they're aware)
[00:22] -queuebot:#ubuntu-release- New binary: qgis [amd64] (eoan-proposed/universe) [3.4.7+dfsg-1] (no packageset)
[02:27] -queuebot:#ubuntu-release- New binary: qgis [arm64] (eoan-proposed/universe) [3.4.7+dfsg-1] (no packageset)
[02:54] -queuebot:#ubuntu-release- New binary: qgis [armhf] (eoan-proposed/universe) [3.4.7+dfsg-1] (no packageset)
[05:16] <acheronuk> vorlon: can you kill off the running and queued tests that are not against marble and umbrello 19.04 in proposed?
[07:33] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (bionic-proposed) [5.0.0-13.14~18.04.2]
[07:33] -queuebot:#ubuntu-release- New: accepted linux-signed-oem-osp1 [amd64] (bionic-proposed) [5.0.0-1004.5]
[07:33] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [ppc64el] (bionic-proposed) [5.0.0-13.14~18.04.2]
[07:53] <mvo> sil2100: hey, sorry for bothering you - I just wanted to wanted to check if the "shadow" sru for xenial/bionic is releasable now or if there is anything missing on our side?
[08:07] <Laney> vorlon: it sure does catch dead things from time to time
[08:07] <Laney> sorry to say this for the millionth time, but this KDE autopkgtest situation needs to be addressed
[08:07] <Laney> we don't have unlimited resources to support people doing whatever they want
[08:12] <sil2100> mvo: hey! Let me get to it shortly ;)
[08:41] <acheronuk> Laney: I intend to go through the KDE tests this cycle and disable/skip ones that are onerous. debian already killed off tests in 38 kdepim sources, which where we followed suit significantly shortened amount of time taken up by rdep test on frameworks in later disco uploads
[08:42] <acheronuk> the tests causing the issue here are ones that I had earmarked to get rid of one way or another this cycle, but honestly had forgotten to do before kicking off on eoan
[08:50] <fidencio> jibel: hey/ping. any chance to have different volume-ids for Ubuntu Server and Ubuntu Live Server medias? :-)
[08:50] <fidencio> jibel: if so, where could I file a bug/rfe for that?
[08:52] <Laney> acheronuk: righto, that'll be appreciated, thanks
[08:53] <acheronuk> Laney: in fact, the cull of KDEPIM tests meant that (I think) frameworks 5.55 rdep tests cleared in ~ 1 day in disco, whereas before it would have been several days. 5.56 update took longer due to some other 'networking' issues on the runners
[08:53] <acheronuk> not saying that all is good without further work, but we are in a better place than we were
[08:53] <Laney> I personally happen to think it'd be worthwhile investing in improvements to be able to build those tests at package build time, but I can't tell people what to spend their time on :>
[08:55] <Laney> probably biased by having worked on https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests too
[08:56] <Laney> not that we fully realise all of that in autopkgtest (the sessions are anything but 'real' desktop ones)
[08:56] <acheronuk> Laney: that is something to look at indeed. debian-kde maintainers have been doing a bit more of that since migration from unstable to testing migration has gated harder on their CI test results, and deciding not to maintain tests on PIM as a result
[08:58] <acheronuk> anyway Laney, just wanted to say that this is not being ignored, but it's going to be incremental improvements over this release I hope
[09:00] <Laney> okey dokey
[10:00] <juliank> I'm a bit confused by excuses
[10:01] <juliank> the lvm2 complains about missing builds, for example for dmsetup; but they finished about 24 hours agho
[10:02] <juliank> some packages went away
[10:02] <juliank> ah
[10:02] <juliank> there were new binaries I think
[10:03] <juliank> ABI bump for  liblvm2cmd2.03 - luckily nothing outside its own source package depends on it
[10:06] <cjwatson> juliank: accepted
[10:06] <juliank> thanks cjwatson
[10:06] -queuebot:#ubuntu-release- New: accepted lvm2 [amd64] (eoan-proposed) [2.03.02-2ubuntu1]
[10:06] -queuebot:#ubuntu-release- New: accepted lvm2 [armhf] (eoan-proposed) [2.03.02-2ubuntu1]
[10:06] -queuebot:#ubuntu-release- New: accepted lvm2 [ppc64el] (eoan-proposed) [2.03.02-2ubuntu1]
[10:06] -queuebot:#ubuntu-release- New: accepted lvm2 [arm64] (eoan-proposed) [2.03.02-2ubuntu1]
[10:06] -queuebot:#ubuntu-release- New: accepted lvm2 [s390x] (eoan-proposed) [2.03.02-2ubuntu1]
[10:06] -queuebot:#ubuntu-release- New: accepted lvm2 [i386] (eoan-proposed) [2.03.02-2ubuntu1]
[10:07] -queuebot:#ubuntu-release- New: accepted pmdk-convert [amd64] (eoan-proposed) [1.5.1-1]
[10:07] -queuebot:#ubuntu-release- New: accepted qgis [amd64] (eoan-proposed) [3.4.7+dfsg-1]
[10:07] -queuebot:#ubuntu-release- New: accepted qgis [armhf] (eoan-proposed) [3.4.7+dfsg-1]
[10:07] -queuebot:#ubuntu-release- New: accepted qgis [ppc64el] (eoan-proposed) [3.4.7+dfsg-1]
[10:07] -queuebot:#ubuntu-release- New: accepted pmdk-convert [arm64] (eoan-proposed) [1.5.1-1]
[10:07] -queuebot:#ubuntu-release- New: accepted qgis [i386] (eoan-proposed) [3.4.7+dfsg-1]
[10:07] -queuebot:#ubuntu-release- New: accepted qgis [arm64] (eoan-proposed) [3.4.7+dfsg-1]
[10:07] -queuebot:#ubuntu-release- New: accepted qgis [s390x] (eoan-proposed) [3.4.7+dfsg-1]
[10:25] <sil2100> rbalint: hey! Looking at the xenial u-u bugs now - can I poke you about something there?
[10:25] <rbalint> sure
[10:26] <sil2100> rbalint: so I was looking at the verification of LP: #1624644 and I just wanted you to check the strangeness that Jarno pointed out regarding the output there
[10:26] <ubot5`> Launchpad bug 1624644 in unattended-upgrades (Ubuntu Xenial) "By default settings unattended-upgrade does not automatically remove kernel packages that become unused in conjunction with updating by other software" [High,Fix committed] https://launchpad.net/bugs/1624644
[10:26] <sil2100> rbalint: with linux-image-extra-4.8.0-54-generic mentioned both as 'Keeping auto-removable' and then actually removing it still
[10:26] <sil2100> Just to be sure there's nothing fishy there
[10:36] <mvo> sil2100: thank you!
[10:44] <rbalint> sil2100, it is fishy, but please see my answere there
[10:49] <sil2100> rbalint: ok, thanks! Yeah, your explaination makes sense
[10:49] <sil2100> mvo: yw!
[10:50] <sil2100> rbalint: phew, I think that was everything - releasing \o/
[10:51]  * mvo hugs sil2100 
[10:54] <rbalint> sil2100, please set phasing to 0, because i'd like to fix the regressions/missing parts
[10:55] <rbalint> sil2100, thanks!
[10:55] <rbalint> sil2100, like the one i just mentioned in the bug
[11:05] <sil2100> rbalint: done o/
[11:05] -queuebot:#ubuntu-release- New binary: isl [s390x] (eoan-proposed/main) [0.21-1] (core)
[11:06] <sil2100> rbalint: (hopefully setting it to 0 will stop the phasing mechanism, can't remember now if there's a special-casing for that)
[11:06] -queuebot:#ubuntu-release- New binary: isl [amd64] (eoan-proposed/main) [0.21-1] (core)
[11:09] -queuebot:#ubuntu-release- Unapproved: rejected gce-compute-image-packages [source] (disco-proposed) [20190315-0ubuntu1]
[11:11] -queuebot:#ubuntu-release- Unapproved: update-notifier (trusty-proposed/main) [0.154.1ubuntu5 => 0.154.1ubuntu6] (kubuntu, ubuntu-desktop, ubuntu-server)
[11:12] -queuebot:#ubuntu-release- New binary: isl [i386] (eoan-proposed/main) [0.21-1] (core)
[11:13] <juliank> sil2100: ^^ this should be the final edition of the update-notifier changes, I played around with it, and it works fine
[11:14] -queuebot:#ubuntu-release- New binary: isl [arm64] (eoan-proposed/main) [0.21-1] (core)
[11:14] <juliank> just a minor hickup in an if/else
[11:16] -queuebot:#ubuntu-release- New binary: isl [armhf] (eoan-proposed/main) [0.21-1] (core)
[11:16] -queuebot:#ubuntu-release- New binary: isl [ppc64el] (eoan-proposed/main) [0.21-1] (core)
[11:16] <juliank> whoa, u-u/xenial released, whoa, awesome :)
[11:18] <juliank> maybe I should actually re-upload the xenial SRU for python-apt and add Breaks: unattended-upgrades (<< $thesru)
[11:20] <juliank> ah, gotta merge locking fixes from disco anyway
[11:26] <sil2100> juliank: ACK
[11:26] <sil2100> ;)
[11:26] <sil2100> Let me just finish with the gce package
[11:27] -queuebot:#ubuntu-release- New: accepted isl [amd64] (eoan-proposed) [0.21-1]
[11:27] -queuebot:#ubuntu-release- New: accepted isl [armhf] (eoan-proposed) [0.21-1]
[11:27] -queuebot:#ubuntu-release- New: accepted isl [ppc64el] (eoan-proposed) [0.21-1]
[11:27] -queuebot:#ubuntu-release- New: accepted isl [arm64] (eoan-proposed) [0.21-1]
[11:27] -queuebot:#ubuntu-release- New: accepted isl [s390x] (eoan-proposed) [0.21-1]
[11:27] -queuebot:#ubuntu-release- New: accepted isl [i386] (eoan-proposed) [0.21-1]
[12:03] <Laney> vorlon: there's huge iowait on the cloud worker, this is likely to be a big part of the problem I'd have thought
[12:03] <Laney> this would be alleviated somewhat by being able to have multiple cloud workers ...
[12:04] <Laney> maybe we should turn *down* concurrency until these build-needed jobs are through
[12:06] <Laney> 137 tar processes running atm
[12:06] <Laney> juliank: guessing you didn't start any work on the parallelisation stuff yet?
[12:07] <juliank> I think I did a small part, but it does not seem to be aroundf
[12:09] <juliank> The major issue (apart from actually deploying it...), is likely distributing the image building
[12:15] <Laney> mmm, that's not very taxing on the host so likely the leader could do that
[12:18] <juliank> yeah
[12:18] <juliank> otherwise, it was just a few variable changes to add hostname + grep hostname in the list of instances to delete in maintenance script
[12:55] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (disco-proposed) [20190315-0ubuntu1~19.04.0]
[12:56] <sil2100> ugh, those gce package updates
[12:56] <sil2100> They confuse me frequently
[12:57] -queuebot:#ubuntu-release- Unapproved: rejected gce-compute-image-packages [source] (bionic-proposed) [20190315-0ubuntu1~18.04.0]
[13:06] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (bionic-proposed) [20190315-0ubuntu1~18.04.0]
[13:09] -queuebot:#ubuntu-release- Unapproved: rejected gce-compute-image-packages [source] (xenial-proposed) [20190315-0ubuntu1~16.04.0]
[13:11] -queuebot:#ubuntu-release- Unapproved: rejected gce-compute-image-packages [source] (trusty-proposed) [20190315-0ubuntu1~14.04.0]
[13:11] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (xenial-proposed) [20190315-0ubuntu1~16.04.0]
[13:13] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (trusty-proposed) [20190315-0ubuntu1~14.04.0]
[13:24] -queuebot:#ubuntu-release- Unapproved: accepted mariadb-10.1 [source] (cosmic-proposed) [1:10.1.38-0ubuntu0.18.10.1]
[13:28] -queuebot:#ubuntu-release- Unapproved: accepted mariadb-10.1 [source] (bionic-proposed) [1:10.1.38-0ubuntu0.18.04.2]
[13:29] -queuebot:#ubuntu-release- Unapproved: rejected gce-compute-image-packages [source] (cosmic-proposed) [20190315-0ubuntu1~18.10.0]
[13:30] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (cosmic-proposed) [20190315-0ubuntu1~18.10.0]
[13:41] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (disco-proposed) [3.30.6-2ubuntu4]
[13:43] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (cosmic-proposed) [3.30.2-0ubuntu11]
[13:49] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (bionic-proposed) [3.28.1-0ubuntu4.18.04.10]
[13:55] <Laney> meh, looks like juju 1.25 documentation has been purged from the website
[13:55] <Laney> guess we should probably move to juju 2 anyway ...
[13:55] <Laney> I'm going to ask for a staging environment
[13:57] -queuebot:#ubuntu-release- Unapproved: rejected gnome-software [source] (xenial-proposed) [3.20.5-0ubuntu0.16.04.12]
[14:07] <Laney> done
[14:07] -queuebot:#ubuntu-release- Unapproved: accepted python3-stdlib-extensions [source] (bionic-proposed) [3.6.8-1~18.04]
[14:13] -queuebot:#ubuntu-release- Unapproved: accepted python-stdlib-extensions [source] (bionic-proposed) [2.7.16-2~18.04]
[14:17] <teward> I assume that the issues with tests taking eons to get done (autopkgtests) *is* known?  (12 hours+ time and no movement on any autopkgtests I can see?)
[14:18] <Laney> yes, we've been talking about it in here
[14:18] <Laney> there is movement, just not much
[14:20] <teward> Laney: not my fault i odn't have anything but the queuebot notices in logs xD
[14:21] <teward> Laney: yeah, I ran into that ftpmaster.internal failure yesterday I saw you discussing about on armhf, but those're the only tests that've finished heh.  *shrugs*
[14:21] <Laney> no they're not
[14:21] <teward> Laney: that *I* saw finished on the packages I'm watching
[14:21] <teward> (I only focus on nginx)
[14:21] <teward> and i'm lagging BAD :|
[14:21]  * teward goes to diagnose what's up with the workplace internet.
[14:21] <Laney> anyway, we have some architectural limitations that are creating this problem right now
[14:22] <teward> ah
[14:23] <Laney> I am reducing the number of parallel test runners now
[14:23] <Laney> in (my) theory that should allow some of these tests to complete
[14:28] <acheronuk> [06:16] <acheronuk> vorlon: can you kill off the running and queued tests that are not against marble and umbrello 19.04 in proposed?
[14:28] <acheronuk> Laney: would that help? ^
[14:30] <Laney> acheronuk: I'm sorry, I don't understand what that means
[14:31] <Laney> there are loads of k* tests in flight
[14:35] <acheronuk> yes, but it's mostly the marble and umbrello ones that keep stalling, going to *many* hrs, and then seemingly respawning, preventing much progress on some of the queues
[14:35] <acheronuk> this is only from what I can observe on the status pages
[14:36] <Laney> anything with build-needed is contributing to this problem
[14:37] <acheronuk> yes, but those are particularly bad as far as I can see. asnd testing against an old version with a new one in proposed is wasteful
[14:39] <Laney> tell you what, I'll kill them off and you re-queue what you want
[14:42] <Laney> there we go
[14:43] <acheronuk> Laney: thanks. I am not sure how much it might help, but seeing those keep jumping back in the queue and blocking progress is not great. If I have to re-queue behing other stuff and wait, then hey
[14:44] <acheronuk> progress was not quick anyway!
[14:44] <xnox> tsimonq2, how does http://launchpadlibrarian.net/388784682/casper_1.395_1.396.diff.gz work at all? e.g. why did you not just guard the 'passwd -d' call? also i cannot find passwd-del.service anywhere. Where is it supposed to come from?
[14:46] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (trusty-proposed) [0.154.1ubuntu6]
[14:51] <xnox> tsimonq2,  i see that at one point that got injected, cat > /root/lib/systemd/system/passwd-del.service << EOF but not anymore!
[14:52] <xnox> tsimonq2, i'll fix it up...
[15:06] <tsimonq2> xnox: Please read the bug report first.
[15:06] <xnox> tsimonq2, i have read all bug reports.
[15:07] <tsimonq2> I don't remember particulars here, although I can reread once I get to Seattle.
[15:07] <xnox> tsimonq2, your upload makes no sense, as you symlink to enable a non-existant systemd unit.
[15:07] <xnox> tsimonq2, because the systemd unit was removed in the previous upload to yours; and you didn't restore it.
[15:07] <xnox> tsimonq2, net effect of your upload was to never delete passwords for everyone; instead of just in ssdm case.
[15:08] <xnox> tsimonq2, also caused bad error messages on subiquity image boot.
[15:08] <tsimonq2> xnox: Again, this was a complex thing I did like a year ago. I need to reread logs; there was justificatiion.
[15:08] <tsimonq2> infinity and vorlon worked on it with me here iirc.
[15:08] <tsimonq2> It's fuzzy, and I don't have the cycles to look until tonight.
[15:09] <xnox> tsimonq2, look http://launchpadlibrarian.net/383837510/casper_1.394_1.395.diff.gz
[15:09] <xnox> the job got deleted.... thus your next upload did nothing useful, but removed the thing everyone else needed.
[15:10] <tsimonq2> xnox: Diffs are pretty difficult to review properly on mobile, with no context.
[15:10] <xnox> tsimonq2, do $ git-ubuntu clone casper
[15:10] <xnox> when you get to a desktop, and do read $ git log -p ./scripts/casper-bottom/25adduser
[15:11]  * tsimonq2 comes back to this later when I can sit down and review at a computer
[15:11] <xnox> my latest upload should fix things up properly for everyone now.
[15:11] <tsimonq2> ...
[15:12] <tsimonq2> So you JFDI before having a conversation about it? Cool, you have TIL now. ;)
[15:13] <tsimonq2> If I recall correctly, it was a lightdm thing too. It was also for platform consistency, since, if I recall correctly, that was what the TB members I was working with preferred.
[15:13] <acheronuk> tsimonq2: that was to fix re-login with sddm in Kubuntu live session?
[15:13] <acheronuk> *in part
[15:14] <tsimonq2> There was more to it, iirc.
[15:14] <acheronuk> hence *in part
[15:14] <tsimonq2> Platform consistency is a thing, though.
[15:29] <xnox> tsimonq2, the code currently in, is broken, and doesn't work, and print error messages =) so yes, i am JFDI to revert uterly broken thing ;-)
[15:31] <xnox> acheronuk, and in process of unbreaking sddm, broke everyone else ;-)
[15:34] <acheronuk> xnox: if sddm live session re-login works tomorrow (or when this migrates), I'm not bothered :)
[15:35] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (disco-proposed/main) [1:19.04.16.1 => 1:19.04.16.2] (core)
[15:52] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (disco-proposed) [1:19.04.16.2]
[16:17] <Laney> ok there are barely any autopkgtests running now, will leave it this way for a bit
[16:17] <Laney> load is a mere 23.58, and a trivial 31 tar processes running /o\
[16:19] <teward> o.o
[16:28] <xnox> acheronuk, well currently sddm live session re-login is working; and it should continue to work once things build/migrate and isos are rebuild. given the current queues, i'm not sure if that will happen tomorrow or not.
[16:32] <acheronuk> Laney: is there any progress on whatever networking issue is causing the copy of the build tree to time out? or is Steve the one to ask?
[16:33] <acheronuk> xnox: yeah, not much hurry :)
[16:33] <Laney> not sure that there is one rather than just contention on the host, but he would be
[16:33] <acheronuk> ok. np
[16:37] <acheronuk> something is regressed on the infra anyway. I'm not placed to say what
[16:38] <Laney> no
[16:38] <Laney> it's a bug that caused a particular combination of packages to create issues on the host
[16:41] <Laney> we can't handle loads of packages with large build trees simultaneously
[16:42] <acheronuk> it did before. much better than this, anyway
[16:42] <Laney> thanks, but this speculation isn't very helpful
[16:44] <Laney> if vorlon/someone wanted to work on filtering & de-duping some of the requests in the queue, *that* would be helpful
[16:44] <Laney> I'll be back later on
[16:44] <Laney> o/
[16:45] <acheronuk> I'm only comparing previous behaviour to current behaviour. Steve said he noticed the transfer was V slow and speculated networking
[16:45] <acheronuk> hence me enquiring
[16:46] <acheronuk> if we can just get back to as before, and then work on improving things, all would be good
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (bionic-proposed) [3.192.1.6]
[18:59] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (cosmic-proposed/main) [4.18.0-19.20] (core, kernel)
[19:02] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [s390x] (cosmic-proposed/universe) [1:10.1.38-0ubuntu0.18.10.1] (no packageset)
[19:02] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [s390x] (bionic-proposed/universe) [1:10.1.38-0ubuntu0.18.04.2] (no packageset)
[19:06] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (disco-proposed/main) [5.0.0-14.15] (core, kernel)
[19:09] -queuebot:#ubuntu-release- Unapproved: nova (disco-proposed/main) [2:19.0.0-0ubuntu2 => 2:19.0.0-0ubuntu2.1] (openstack, ubuntu-server)
[19:29] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (disco-proposed/main) [5.0.0-14.15] (core, kernel)
[19:32] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (disco-proposed/main) [5.0.0-14.15] (core, kernel)
[20:25] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [i386] (cosmic-proposed/universe) [1:10.1.38-0ubuntu0.18.10.1] (no packageset)
[20:30] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [amd64] (cosmic-proposed/universe) [1:10.1.38-0ubuntu0.18.10.1] (no packageset)
[20:33] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [amd64] (bionic-proposed/universe) [1:10.1.38-0ubuntu0.18.04.2] (no packageset)
[20:36] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (disco-proposed) [5.0.0-14.15]
[20:36] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (disco-proposed) [5.0.0-14.15]
[20:36] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (disco-proposed) [5.0.0-14.15]
[20:36] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (cosmic-proposed) [4.18.0-19.20]
[20:39] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [ppc64el] (cosmic-proposed/universe) [1:10.1.38-0ubuntu0.18.10.1] (no packageset)
[20:40] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [ppc64el] (bionic-proposed/universe) [1:10.1.38-0ubuntu0.18.04.2] (no packageset)
[20:42] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [i386] (bionic-proposed/universe) [1:10.1.38-0ubuntu0.18.04.2] (no packageset)
[21:08] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [arm64] (cosmic-proposed/universe) [1:10.1.38-0ubuntu0.18.10.1] (no packageset)
[21:10] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [armhf] (bionic-proposed/universe) [1:10.1.38-0ubuntu0.18.04.2] (no packageset)
[21:23] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [arm64] (bionic-proposed/universe) [1:10.1.38-0ubuntu0.18.04.2] (no packageset)
[21:24] <bdmurray> Why aren't disco-proposed versions showing up here? http://autopkgtest.ubuntu.com/packages/ubuntu-release-upgrader/disco/amd64
[21:30] -queuebot:#ubuntu-release- New binary: mariadb-10.1 [armhf] (cosmic-proposed/universe) [1:10.1.38-0ubuntu0.18.10.1] (no packageset)