[00:07] <cjwatson> sure
[00:25] -queuebot:#ubuntu-release- New binary: firefox [arm64] (bionic-proposed/main) [58.0.1+build1-0ubuntu1] (kubuntu, mozilla, ubuntu-desktop)
[00:28] -queuebot:#ubuntu-release- New sync: livecd-rootfs (bionic-release/primary) [2.490]
[00:33] -queuebot:#ubuntu-release- New: accepted livecd-rootfs [sync] (bionic-release) [2.490]
[00:36] <slangasek> cjwatson: is it certain that .scalingstack matches the hostname?  the log only ever shows the local part in output
[00:37] <cjwatson> *.buildd is legacy but harmless; *.ppa|*.scalingstack I think matches all our current hosts, though I can't be completely certain - I'm going from what LP believes their hostnames to be
[00:38] <cjwatson> there are unfortunately a couple of different naming schemes, but I'm not aware of anything that wouldn't match
[00:40] <slangasek> cjwatson: ok; since the autopkgtests also don't catch this, and since *.ppa suggests the hostnames might be different if I triggered a livefs build in a ppa for testing (?), it'd be nice to know with certainty before uploading and potentially having to revert again
[00:40] <slangasek> I guess I could upload, block in -proposed, and do a PROPOSED=1 test
[00:42] <cjwatson> "in a ppa" no, not that
[00:42] <cjwatson> the differences are per-region
[00:42] <slangasek> ok
[00:42] <cjwatson> AFAICT due to either prevailing documentation or personal sysadmin preference at the time the region in question was deployed
[00:42] <cjwatson> PROPOSED=1 has a decent (not 100%) chance of catching any errors though
[00:43]  * cjwatson sleeps
[00:44] -queuebot:#ubuntu-release- New: accepted lubuntu-artwork [amd64] (bionic-proposed) [0.70]
[00:44] -queuebot:#ubuntu-release- New: accepted node-fn-name [amd64] (bionic-proposed) [2.0.1-2]
[00:44] -queuebot:#ubuntu-release- New: accepted firefox [amd64] (bionic-proposed) [58.0.1+build1-0ubuntu1]
[00:44] -queuebot:#ubuntu-release- New: accepted firefox [i386] (bionic-proposed) [58.0.1+build1-0ubuntu1]
[00:44] -queuebot:#ubuntu-release- New: accepted firefox [arm64] (bionic-proposed) [58.0.1+build1-0ubuntu1]
[01:09] <tsimonq2> Interesting proposal: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2018-February/017875.html
[01:29] -queuebot:#ubuntu-release- New binary: togl [amd64] (bionic-proposed/universe) [2.0-1] (no packageset)
[01:29] -queuebot:#ubuntu-release- New binary: togl [ppc64el] (bionic-proposed/universe) [2.0-1] (no packageset)
[01:29] -queuebot:#ubuntu-release- New binary: togl [i386] (bionic-proposed/universe) [2.0-1] (no packageset)
[01:29] -queuebot:#ubuntu-release- New binary: togl [s390x] (bionic-proposed/universe) [2.0-1] (no packageset)
[01:31] -queuebot:#ubuntu-release- New binary: togl [armhf] (bionic-proposed/universe) [2.0-1] (no packageset)
[01:33] -queuebot:#ubuntu-release- New binary: togl [arm64] (bionic-proposed/universe) [2.0-1] (no packageset)
[01:45] -queuebot:#ubuntu-release- New: accepted togl [amd64] (bionic-proposed) [2.0-1]
[01:45] -queuebot:#ubuntu-release- New: accepted togl [armhf] (bionic-proposed) [2.0-1]
[01:45] -queuebot:#ubuntu-release- New: accepted togl [ppc64el] (bionic-proposed) [2.0-1]
[01:45] -queuebot:#ubuntu-release- New: accepted togl [arm64] (bionic-proposed) [2.0-1]
[01:45] -queuebot:#ubuntu-release- New: accepted togl [s390x] (bionic-proposed) [2.0-1]
[01:45] -queuebot:#ubuntu-release- New: accepted togl [i386] (bionic-proposed) [2.0-1]
[02:47] <infinity> tsimonq2: Not particularly, no.
[02:57] <tsimonq2> infinity: Depends on your opinion of it. It could work well if implemented properly.
[02:58] <infinity> tsimonq2: "If implemented properly" implies a lot more work.  Curious who plans to staff that.
[02:58] <tsimonq2> infinity: I'm curious about that as well.
[05:10] -queuebot:#ubuntu-release- New binary: gdbm [ppc64el] (bionic-proposed/main) [1.14.1-2] (core)
[05:10] -queuebot:#ubuntu-release- New binary: gdbm [s390x] (bionic-proposed/main) [1.14.1-2] (core)
[05:11] -queuebot:#ubuntu-release- New binary: gdbm [arm64] (bionic-proposed/main) [1.14.1-2] (core)
[05:11] -queuebot:#ubuntu-release- New binary: gdbm [i386] (bionic-proposed/main) [1.14.1-2] (core)
[05:11] -queuebot:#ubuntu-release- New binary: gdbm [armhf] (bionic-proposed/main) [1.14.1-2] (core)
[05:12] -queuebot:#ubuntu-release- New binary: gdbm [amd64] (bionic-proposed/main) [1.14.1-2] (core)
[05:12] <ginggs> morning! octave-symbol's autokpgtests have regressed in release on amd64 and ppc64el. octave-ltfat's autopkgtests are now timing out on arm64.  can these be force-badtest'd please?
[07:34] -queuebot:#ubuntu-release- New: accepted gdbm [amd64] (bionic-proposed) [1.14.1-2]
[07:34] -queuebot:#ubuntu-release- New: accepted gdbm [armhf] (bionic-proposed) [1.14.1-2]
[07:34] -queuebot:#ubuntu-release- New: accepted gdbm [ppc64el] (bionic-proposed) [1.14.1-2]
[07:34] -queuebot:#ubuntu-release- New: accepted gdbm [arm64] (bionic-proposed) [1.14.1-2]
[07:34] -queuebot:#ubuntu-release- New: accepted gdbm [s390x] (bionic-proposed) [1.14.1-2]
[07:34] -queuebot:#ubuntu-release- New: accepted gdbm [i386] (bionic-proposed) [1.14.1-2]
[09:09] <cpaelzer> infinity: you already had a vagrant-libvirt rule so I set you as reviewer of https://code.launchpad.net/~paelzer/britney/hints-ubuntu-libvirt-blocked-s390x-vagrant/+merge/336955
[09:10] <cpaelzer> but essentially I think the case is clear, so anyone else acking on it would be fine as well
[09:11] <cpaelzer> also ipxe-qemu-256k-compat is still in bionic's new queue
[09:12] <cpaelzer> infinity: you mentioned you wanted to take a look, but I assume high prio interrupts stopped you
[09:12] <infinity> cpaelzer: Yeah, didn't quite get to it yet.
[09:12] <infinity> cpaelzer: britney hint LGTM, merging.
[09:12] <cpaelzer> thanks
[09:13] <cpaelzer> knowing that ipxe-qemu-256k-compa still on your list is fine enough for now
[09:21] <LocutusOfBorg> can anybody please ignore haskell-hoogle/arm64 test so we can finally see haskell migrate? the test is flaky, I don't see a point in clicking retry until it passes
[09:21] <LocutusOfBorg> apw, Laney ^^
[09:21] <LocutusOfBorg> http://autopkgtest.ubuntu.com/packages/h/haskell-hoogle/bionic/arm64 see the history
[09:21] <doko> nfs for main? joy ...
[09:22] <LocutusOfBorg> (and I smell the problem to be around the container stuff, not a flaky package in real environment?)
[09:23] <infinity> LocutusOfBorg: arm64 autopkgtests aren't in containers.
[09:23] <infinity> LocutusOfBorg: Probably more to do with arm64 ghc being sketchy.
[09:24] <LocutusOfBorg> maybe, but at this point I don't care too much honestly
[09:25] <LocutusOfBorg> it has been that way for years probably
[09:28] <rbasak> doko: so in Debian they've uploaded mariadb-10.2 to unstable as well, and are preparing mariadb-10.3. They moved some binaries from mariadb-10.1 to mariadb-10.2, leaving mariadb-10.1 somewhat broken in terms of dep8 (one of the tests can no longer run).
[09:29] <rbasak> I'm not sure how imminent the removal of mariadb-10.1 is.
 doko: if you need mariadb-10.1 through, I think it's appropriate to force-badtest it.
[09:32] <LocutusOfBorg> infinity, this one is also mostly trivial and will make something migrate https://code.launchpad.net/~costamagnagianfranco/britney/hints-ubuntu/+merge/335626
[09:39] <LocutusOfBorg> <3
[09:41] <LocutusOfBorg> please cleanup consolekit, it is now built only on kfreebsd so we can NBS/remove it?
[09:43] <infinity> LocutusOfBorg: It has rdeps.
[09:44] <LocutusOfBorg> nice way to do a transition :)
[09:44] <infinity> (IOW: I'm not deleting it from -release until that's fixed)
[09:44] <LocutusOfBorg> sure, it makes a lot of sense :)
[09:46] <LocutusOfBorg> do you think we can do some systemd ignore on amd64 so we can move forward with perl and bind9 transitions? the new systemd is not building on arm64 probably due to https://bugs.debian.org/888789
[09:46] <LocutusOfBorg> doko, there is an upstream merged patch, any reason for not having uploaded it?
[09:47] <doko> I haven't seen any patch yet
[09:48] <LocutusOfBorg> you might be right, I'm pretty sure I saw it with a link from the debian bug, but I can't find it anymroe
[09:48] <LocutusOfBorg> will look after coffee
[09:52] <LocutusOfBorg> infinity, question: I made openmw build on arm64, but this will likely not work anymore because it works only with gl and not with gles
[09:52] <LocutusOfBorg> can you please remove that package? https://launchpad.net/ubuntu/+source/openmw/0.43.0-3 on arm64? so we can force-sync next time?
[09:52] <LocutusOfBorg> I don't see a point in making it build if it will not work
[09:52] <LocutusOfBorg> mitya57, ^^
[09:55] <doko> LocutusOfBorg: yes, discussed yesterday with ginggs. did you look for rdeps?
[10:16] <LocutusOfBorg> I can't find any rdep
[11:07] <LocutusOfBorg> please make perl migrate, seriously
[11:08] <LocutusOfBorg> gdbm transition is ongoing, and a perl rebuild will make it entangle even more
[11:16] <ginggs> LocutusOfBorg: do ko did remove it, and tinyxml2 migrated, but then you uploaded 0.43.0-3ubuntu1
[11:22] <doko> LocutusOfBorg: did you look at the systemd failure triggered by perl?
[11:27] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (artful-proposed) [3.5-1~ubuntu17.10.2]
[11:28] <LocutusOfBorg> doko, cryptofoo timeout while starting?
[11:29] <LocutusOfBorg> varcrypt, whatever it means
[11:31] <LocutusOfBorg> ginggs, I think the ubuntu1 is the one who did make it migrate... did we do it at the exact same time? (upload+removal)
[11:31] <LocutusOfBorg> hurray for haskell migration
[11:35] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (xenial-proposed) [3.5-1~ubuntu16.04.2]
[11:36] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (trusty-proposed) [3.5-1~ubuntu14.04.2]
[11:39] -queuebot:#ubuntu-release- Unapproved: accepted php-sabre-vobject-3 [source] (artful-proposed) [3.5.2-1ubuntu0.1]
[11:41] <ginggs> LocutusOfBorg: from emails, i think tinyxml2 migrated at 2018-01-30 20:54 GMT
[11:43] <LocutusOfBorg> and openmw 2018-01-30 23:03:50 CET
[11:43] <LocutusOfBorg> damn, I uploaded because stuff was not migrating, I missed it for one hour
[12:20] -queuebot:#ubuntu-release- Unapproved: accepted intltool [source] (artful-proposed) [0.51.0-4ubuntu1.17.04.1]
[12:28] -queuebot:#ubuntu-release- Unapproved: accepted intltool [source] (xenial-proposed) [0.51.0-2ubuntu1.16.04.1]
[12:33] -queuebot:#ubuntu-release- Unapproved: accepted apparmor [source] (artful-proposed) [2.11.0-2ubuntu17.1]
[12:36] -queuebot:#ubuntu-release- Unapproved: accepted apparmor [source] (xenial-proposed) [2.10.95-0ubuntu2.8]
[12:42] -queuebot:#ubuntu-release- Unapproved: accepted apparmor [source] (trusty-proposed) [2.10.95-0ubuntu2.6~14.04.2]
[12:46] <doko> ginggs: https://launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/9.0.176-2 isn't migrating
[13:13] <jbicha> any volunteers to put out a "non-announcement" on the ubuntu-devel-announce list today to let people know that there won't be an Alpha 2 release?
[13:29]  * rbasak considers copying and pasting that
[14:06] <ginggs> doko: nvidia-cuda-toolkit not installable due to: libgl1-mesa-glx conflicts libgl1
[14:06] <ginggs> doko: so the problem lies with mesa?
[14:08] <ginggs> doko: eztrace-contrib, hwloc-contrib and pycuda are all affected
[14:14] <doko> tjaalton: ^^^
[14:15] <tjaalton> huh?
[14:15] <tjaalton> tseliot: ^?
[14:15] <doko> mesa?
[14:16] <tseliot> I'm pretty sure I didn't change anything there
[14:16] <tjaalton> libgl1-mesa-glx has conflicted with libgl1 for a long time
[14:16] <tseliot> not yet, at least
[14:16] <tjaalton> it's C/R/P: libgl1
[14:17] <doko> see also:
[14:17] <doko> libglvnd (0.2.999+git20170802-2 to 1.0.0-2)
[14:17] <doko> Maintainer: Debian X Strike Force
[14:17] <doko> Section: universe/misc
[14:17] <doko> 5 days old
[14:17] <doko> libegl1/amd64 unsatisfiable Depends: libegl-mesa0 | libegl-vendor
[14:17] <doko> libglx0/amd64 unsatisfiable Depends: libglx-mesa0 | libglx-vendor
[14:18] <tseliot> tjaalton: it looks like fun ^ ;)
[14:18] <tjaalton> libglvnd has been there since august
[14:18] <tjaalton> it'
[14:18] <tjaalton> it shouldn't be causing issues
[14:18] <ginggs> tjaalton tseliot: this has been like this for a while - at least end December, nvidia-cuda-toolkit 9.0.176-1 did not migrate either
[14:19] <tjaalton> synced from debian?
[14:19] <tjaalton> not going to work then
[14:19] <tjaalton> most likely
[14:19] <tjaalton> debian migrated to libglvnd already, we will in a week or two
[14:23] <rbasak> Could someone force-badtest dovecot/1:2.2.33.2-1ubuntu1/armhf please? It's the same racy pattern with the dovecot tests as ever.
[14:25] <LocutusOfBorg> cjwatson, please block haskell autosync again, now the switch to 8.2 might be imminent in some days :)
[14:27] <ginggs> tjaalton: <tjaalton> synced from debian? - is what synced from debian?
[14:27] <tjaalton> nvidia-cuda-toolkit 9.0.176-2
[14:27] <tjaalton> if it depends on the debian nvidia driver model, it's not going to work on ubuntu
[14:27] <ginggs> tjaalton: ok, yes it is
[14:28] <tjaalton> tseliot: don't we have cuda too?
[14:28] <tjaalton> so this should be blacklisted, I think
[14:28] <ginggs> tjaalton: anbe, tseliot and i made it work with the ubuntu driver model too
[14:28] <tjaalton> something is missing then
[14:29] <cjwatson> LocutusOfBorg: Done.  It's a fairly simple sync-blacklist change FWIW, any AA should be able to look at the blacklist history and dig out what's necessary
[14:29] <tjaalton> ginggs: if you are not able to install on a chroot with bionic-proposed enabled, then try with ppa:canonical-x/testing
[14:30] <tjaalton> ginggs: if that works, then either change the package or wait until glvnd has landed
[14:31] <LocutusOfBorg> oh nice thanks! I was wondering if it was something that was under your only control
[14:35] <cjwatson> LocutusOfBorg: it used to be a slightly more involved change to auto-sync, but I fixed that ages ago
[14:35] <LocutusOfBorg> ack thanks
[14:36] <LocutusOfBorg> BTW I won't give up for ghc 8.2/bionic, but only if it settles down in Debian before
[14:41] <tjaalton> ginggs: I don't see anything in the package blocking it's install
[14:42] <ginggs> tjaalton: i was able to install libgl1 and libglx0 from ppa:canonical-x/testing
[14:42] <tjaalton> ginggs: on a clean chroot, install libgl1-mesa-glx, then install nvidia-cuda-toolkit. no problems
[14:43] <ginggs> but not sure what that tells us
[14:43] <tjaalton> this was with pure bionic-proposed
[14:43] <tjaalton> no ppa
[14:43] <tjaalton> so whatever says there are conflicts is wrong
[14:44] <ginggs> chdist aptitude bionic build-dep pycuda
[14:44] <ginggs> libgl1-mesa-glx: Conflicts: libgl1 but 1.0.0-2 is to be installed
[14:45] <tjaalton> with just proposed?
[14:45] <tjaalton> not here
 with just proposed? - not sure what you mean here
[14:46] <tjaalton> use a clean chroot
[14:46] <tjaalton> don't enable the ppa
[14:46] <tjaalton> enable proposed
[14:47] <tjaalton> you didn't test the first case I asked?
[14:47] <tjaalton> 16:29 < tjaalton> ginggs: if you are not able to install on a chroot with bionic-proposed enabled, then
[14:47] <tjaalton>                   try with ppa:canonical-x/testing
[14:47] <tjaalton> just using -proposed works fine here
[14:47] <ginggs> the output i showed is from 'chdist aptitude bionic build-dep pycuda'
[14:48] <ginggs> with bionic-proposed enable in .chdist/etc/apt/sources.list
[14:48] <tjaalton> I have no problem running 'apt build-dep pycuda'
[14:48] <tjaalton> works fine
[14:49] <tjaalton> aha
[14:49] <tjaalton> works fine if libgl1-mesa-glx is already installed
[14:50] <tjaalton> so, remove libglvnd from proposed
[14:50] <tjaalton> it'll be fixed later anyway
 so, remove libglvnd from proposed <- doko
[14:50] <ginggs> thanks tjaalton
[14:51] <tjaalton> the current version won't work on ubuntu as-is because it refers to mesa version where debian migrated
[14:52] <tseliot> yes, we'll be moving to glvnd soon
[14:54] <tjaalton> clean chroot, enable the testing ppa; apt build-dep pycuda works
[14:54] <tjaalton> anyway, we'll get there before FF
[14:55] <tjaalton> libglvnd can be removed from -proposed for now
[16:23] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (trusty-proposed/universe) [20171129+dfsg1-0ubuntu1~14.04.0 => 20180129+dfsg1-0ubuntu1~14.04.0] (ubuntu-cloud)
[16:23] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (xenial-proposed/universe) [20171129+dfsg1-0ubuntu1~16.04.0 => 20180129+dfsg1-0ubuntu1~16.04.0] (ubuntu-cloud)
[16:24] -queuebot:#ubuntu-release- Unapproved: gce-compute-image-packages (artful-proposed/universe) [20171129+dfsg1-0ubuntu1~17.10.0 => 20180129+dfsg1-0ubuntu1~17.10.0] (ubuntu-cloud)
[18:18] <slangasek> doko: fwiw I noticed that you had demoted packages that only Recommends: python-imaging rather than Depends:; I'm going to readd these since these are allowed per proposed-migration
[18:19] <doko> slangasek: hmm, .... I had removed the packages now. not sure, which ones will migrate
[18:19] <slangasek> doko: it's fine, I'm re-adding, just wanted to give you a heads-up
[18:19] <doko> python-aalib python-trml2pdf streamtuner2 trac-diavisview trac-odtexport trac-wikiprint twms utopia-documents weboob cfv comix fofix-dfsg griffith htmlgen ibid impressive impressive-display mcomix oboinus phatch photon pisa psychopy
[18:20] <doko> these were removed
[18:20] <slangasek> cfv, pisa I'm readding
[18:20] <doko> ta
[20:32] -queuebot:#ubuntu-release- Unapproved: accepted preseed [source] (artful-proposed) [1.71ubuntu5.1]
[20:38] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (artful-proposed) [20101020ubuntu523.2]
[20:55] -queuebot:#ubuntu-release- Unapproved: rejected pulseaudio [source] (artful-proposed) [1:10.0-2ubuntu3.1]
[20:56] -queuebot:#ubuntu-release- Unapproved: rejected pulseaudio [source] (xenial-proposed) [1:8.0-0ubuntu3.8]
[21:01] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [source] (xenial-proposed) [0.8.3-0ubuntu1]
[21:10] -queuebot:#ubuntu-release- New binary: budgie-extras [amd64] (bionic-proposed/universe) [0.4.1-0ubuntu1] (personal-fossfreedom)
[21:20] <slangasek> Laney: did you find anything that explained arm64 autopkgtest queue flatlining last weekend? because it seems to be doing it again
[21:23] -queuebot:#ubuntu-release- Unapproved: accepted qttools-opensource-src [source] (xenial-proposed) [5.5.1-3ubuntu0.1]
[21:35] -queuebot:#ubuntu-release- New binary: budgie-artwork [amd64] (bionic-proposed/universe) [0.9.0] (personal-fossfreedom)
[22:04] -queuebot:#ubuntu-release- New binary: rustc [ppc64el] (bionic-proposed/universe) [1.23.0+dfsg1+llvm-0ubuntu1] (no packageset)
[22:37] <nacc> slangasek: did you figure out what is going on the with arm builders
[22:38] <slangasek> nacc: I wasn't aware anything was going on with arm builders; context?
[22:38] <nacc> slangasek: or maybe i'm just missing their queues being rather long?
[22:38] <nacc> slangasek: i saw you mentioned it above for the dep8 queues
[22:38] <nacc> but perhaps those are separate?
[22:38] <slangasek> nacc: dep8 queues != builders
[22:38] <nacc> ah ok
[22:38] <nacc> i assumed they were the same population of machines
[22:39] <slangasek> they both run on scalingstack, so there can be problems affecting both; but so far I've only noticed a symptom on autopkgtest
[22:39] <slangasek> and maybe I should highlight wgrant so we can compare notes
[22:39] <nacc> i think i'm just hitting the builders while ruby is too
[22:47] <slangasek> GOOD NEWS EVERYONE, autosynced ruby transition
[22:47] <tsimonq2> SO AMAZINGLY WONDERFUL.
[22:47] <tsimonq2> Now, quick, someone upload Perl!
[22:49] <slangasek> it's already there, if somebody uploads it again before it transitions I will tele-murderize
[22:49] <tsimonq2> slangasek: ...why in the hell isn't something huge like this blacklisted from autosync?!?
[22:50] <Laney> slangasek: Not really here but things seem to be progressing albeit very slowly
[22:50] <Laney> It's possible I tipped the cloud over the edge when moving the armhf workers over there --- IS might be able to tell you more (and maybe hurry up adding some of the bos01 capacity there)
[22:51] <slangasek> tsimonq2: because that just moves the pain around
[22:52] <tsimonq2> slangasek: It delays the pain until sane times when our infra isn't crippled :P
[22:52] <tsimonq2> Or am I wrong here?
[22:53] <slangasek> tsimonq2: "delays the pain" has the risk of causing us to miss it completely for a release cycle and ship out-of-date stuff instead
[22:53] <slangasek> anyway, changing ruby-defaults is not automatically a huge transition right away
[22:53] <tsimonq2> slangasek: ah ok
[23:08] -queuebot:#ubuntu-release- New binary: liblivemedia [ppc64el] (bionic-proposed/universe) [2018.01.29-1] (kubuntu)
[23:08] -queuebot:#ubuntu-release- New binary: libplacebo [ppc64el] (bionic-proposed/universe) [0.3.0-2] (no packageset)
[23:09] -queuebot:#ubuntu-release- New binary: liblivemedia [s390x] (bionic-proposed/universe) [2018.01.29-1] (kubuntu)
[23:09] -queuebot:#ubuntu-release- New binary: libplacebo [s390x] (bionic-proposed/universe) [0.3.0-2] (no packageset)
[23:19] -queuebot:#ubuntu-release- Unapproved: salt (artful-proposed/universe) [2016.11.5+ds-1 => 2017.7.2+dfsg1-1ubuntu1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: libplacebo [armhf] (bionic-proposed/universe) [0.3.0-2] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: liblivemedia [arm64] (bionic-proposed/universe) [2018.01.29-1] (kubuntu)
[23:21] -queuebot:#ubuntu-release- New binary: libplacebo [arm64] (bionic-proposed/universe) [0.3.0-2] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: liblivemedia [armhf] (bionic-proposed/universe) [2018.01.29-1] (kubuntu)
[23:26] -queuebot:#ubuntu-release- New binary: liblivemedia [amd64] (bionic-proposed/universe) [2018.01.29-1] (kubuntu)
[23:26] -queuebot:#ubuntu-release- New binary: libplacebo [amd64] (bionic-proposed/universe) [0.3.0-2] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: libplacebo [i386] (bionic-proposed/universe) [0.3.0-2] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: liblivemedia [i386] (bionic-proposed/universe) [2018.01.29-1] (kubuntu)
[23:37] -queuebot:#ubuntu-release- New binary: node-buf-compare [amd64] (bionic-proposed/universe) [1.0.1-2] (no packageset)
[23:40] -queuebot:#ubuntu-release- New binary: streamtuner2 [amd64] (bionic-proposed/universe) [2.2.0+dfsg-1] (no packageset)