[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-cups [amd64] (bionic-proposed) [1.0.0-0ubuntu1]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-cups [armhf] (bionic-proposed) [1.0.0-0ubuntu1]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-cups [ppc64el] (bionic-proposed) [1.0.0-0ubuntu1]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-gcp [amd64] (bionic-proposed) [1.0.0-0ubuntu2]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-gcp [armhf] (bionic-proposed) [1.0.0-0ubuntu2]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-gcp [ppc64el] (bionic-proposed) [1.0.0-0ubuntu2]
[02:15] -queuebot:#ubuntu-release- New: accepted node-isomorphic-fetch [amd64] (bionic-proposed) [2.2.1-1]
[02:15] -queuebot:#ubuntu-release- New: accepted py-radix [amd64] (bionic-proposed) [0.10.0-1]
[02:15] -queuebot:#ubuntu-release- New: accepted py-radix [armhf] (bionic-proposed) [0.10.0-1]
[02:15] -queuebot:#ubuntu-release- New: accepted py-radix [ppc64el] (bionic-proposed) [0.10.0-1]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-cups [arm64] (bionic-proposed) [1.0.0-0ubuntu1]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-cups [s390x] (bionic-proposed) [1.0.0-0ubuntu1]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-gcp [i386] (bionic-proposed) [1.0.0-0ubuntu2]
[02:15] -queuebot:#ubuntu-release- New: accepted node-pretty-bytes [amd64] (bionic-proposed) [4.0.2-2]
[02:15] -queuebot:#ubuntu-release- New: accepted py-radix [i386] (bionic-proposed) [0.10.0-1]
[02:15] -queuebot:#ubuntu-release- New: accepted python-backports.tempfile [amd64] (bionic-proposed) [1.0-1]
[02:15] -queuebot:#ubuntu-release- New: accepted scour [amd64] (bionic-proposed) [0.36-2]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-cups [i386] (bionic-proposed) [1.0.0-0ubuntu1]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-gcp [s390x] (bionic-proposed) [1.0.0-0ubuntu2]
[02:15] -queuebot:#ubuntu-release- New: accepted py-radix [s390x] (bionic-proposed) [0.10.0-1]
[02:15] -queuebot:#ubuntu-release- New: accepted wcstools [amd64] (bionic-proposed) [3.9.5-2]
[02:15] -queuebot:#ubuntu-release- New: accepted cpdb-backend-gcp [arm64] (bionic-proposed) [1.0.0-0ubuntu2]
[02:15] -queuebot:#ubuntu-release- New: accepted python-backports.weakref [amd64] (bionic-proposed) [1.0-1]
[02:15] -queuebot:#ubuntu-release- New: accepted py-radix [arm64] (bionic-proposed) [0.10.0-1]
[02:32] -queuebot:#ubuntu-release- New binary: poppler [s390x] (bionic-proposed/main) [0.62.0-1ubuntu1] (desktop-core, ubuntu-server)
[02:33] -queuebot:#ubuntu-release- New binary: poppler [ppc64el] (bionic-proposed/main) [0.62.0-1ubuntu1] (desktop-core, ubuntu-server)
[02:36] <handsome_feng> Hi, Could someone in archive admins team help to review the ukui-menus in bionic upload queue? Thanks a lot!
[02:38] -queuebot:#ubuntu-release- New binary: poppler [arm64] (bionic-proposed/main) [0.62.0-1ubuntu1] (desktop-core, ubuntu-server)
[02:38] -queuebot:#ubuntu-release- New binary: poppler [armhf] (bionic-proposed/main) [0.62.0-1ubuntu1] (desktop-core, ubuntu-server)
[02:39] -queuebot:#ubuntu-release- New: accepted poppler [arm64] (bionic-proposed) [0.62.0-1ubuntu1]
[02:39] -queuebot:#ubuntu-release- New: accepted poppler [ppc64el] (bionic-proposed) [0.62.0-1ubuntu1]
[02:39] -queuebot:#ubuntu-release- New: accepted poppler [armhf] (bionic-proposed) [0.62.0-1ubuntu1]
[02:39] -queuebot:#ubuntu-release- New: accepted poppler [s390x] (bionic-proposed) [0.62.0-1ubuntu1]
[02:54] -queuebot:#ubuntu-release- New binary: poppler [i386] (bionic-proposed/main) [0.62.0-1ubuntu1] (desktop-core, ubuntu-server)
[03:08] -queuebot:#ubuntu-release- New: accepted poppler [i386] (bionic-proposed) [0.62.0-1ubuntu1]
=== lotuspsychje_ is now known as lotuspsychje
[07:06] <handsome_feng> Hi, Could someone in archive admins team help to review the ukui-menus in bionic upload queue? Thanks a lot!
[09:47] <cpaelzer> apw: I wonder if your wet kipper whacking yesterday was too much
[09:47] <apw> cpaelzer, ?
[09:48] <cpaelzer> open-vm-tools is no more listed in update-excuses, but still didn't make it into the release pocket
[09:48] <cpaelzer> https://launchpad.net/ubuntu/+source/open-vm-tools/2:10.2.0-1
[09:48] <cpaelzer> I wonder where it is hanging now :-)
[09:49] <cpaelzer> rmadison condiers it complete actually
[09:49] <cpaelzer> hmm yeah
[09:49] <cpaelzer> in a container I can also install it
[09:50] <cpaelzer> so only LP didn't pick it up on the build page and also didn't do the usual updates on associated bugs
[09:51] <apw> cpaelzer, i don't understand -2 is in the -release pocket, is that not correct ?
[09:51] <cpaelzer> yes all good
[09:51] <cpaelzer> I now finally found, I still had the -1 page on LP open
[09:51] <cpaelzer> sorry for the noise
[09:51] <cpaelzer> on https://launchpad.net/ubuntu/+source/open-vm-tools/2:10.2.0-2 all looks good
[09:51] <cpaelzer> the -2 came in and autosynced in between
[09:52] <cpaelzer> I'll close the bugs manually
[09:56] <apw> cpaelzer, great
[12:14] <ahasenack> hi guys, can someone please mark the s390x autopkgtest as "always failed" for ocfs2-tools? Reasoning is two-fold:
[12:14] <ahasenack> a) it started failing last year since the switch from lxc to vm. That allowed new tests, that were previously blocked by lxc, to be run
[12:15] <ahasenack> b) the new tests fail because the tools don't work on big endian according to https://github.com/markfasheh/ocfs2-tools/issues/22
[12:15] <ahasenack> I have an LP bug for that issue as well: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1745155
[12:15] <ubot5> Ubuntu bug 1745155 in ocfs2-tools (Ubuntu) "o2image fails on s390x" [Undecided,New]
[12:16] <apw> ahasenack, we actually don't have a way to mark something back to "always failed" how i wish we did
[12:16] <ahasenack> you mean you can mark it, but a new upload has to happen?
[12:17] <apw> no i mean there is no syntax to say please ignore any previous good
[12:17] <juliank> apw: I think you can reset s390x?
[12:17] <juliank> and then it reruns and it's basically the first failure?
[12:17] <apw> i believe the only way is to remove the old results for its
[12:18] <apw> entire history, or to kick an ignore for the current version along the road
[12:18] <ahasenack> the ignore would be for this upload only?
[12:18] <apw> we tend to do the latter when we have a hope the tests will be fixed "soon"
[12:18] <juliank> in any case ocfs2 does not work on s390x at all
[12:18] <ahasenack> next time it's uploaded, it will happen again?
[12:18] <apw> right, it needs updating for each and every upload, yes, it _is_ dumb
[12:18] <apw> Laney, ^ about right ?
[12:19] <juliank> I'd probably just upload it with s390x blacklisted next time, and remove s390x binaries.
[12:20] <juliank> because if the tools all assume little endian, they're of no use anyway
[12:20] <ahasenack> I did some googling, I didn't find a statement "ocfs2 does not work on s390"
[12:20] <ahasenack> maybe it's just some of the tools
[12:20] <ahasenack> but I'm far from certain
[12:21] <juliank> yeah the tools
[12:21] <juliank> "ocfs2 tools read lots of stuff directly from disk without converting to the endian of cpu using, since the stuff in the disk is in little endian, the tools only works in little endian arch, need modify all those to support big endian."
[12:21] <juliank> from https://github.com/markfasheh/ocfs2-tools/issues/22
[12:21] <ahasenack> mkfs worked
[12:21] <ahasenack> what confused me is that the "disk" was created in s390x for that test
[12:21] <ahasenack> so it's not a case of sharing the filesytem with another not-big-endian system
[12:22] <ahasenack> it was all done on the same system
[12:22] <ahasenack> localhost
[12:23] <Laney> apw: yeah, best you can do is badtest "all"
[12:23] <apw> we _really_ should fix that, it is so fundamentally something you nee
[12:23] <apw> need
[12:25] <slashd> o/ sil2100 Good Thursday, could you please (when you have a moment) have a look in the upload queues to approve landscape-client for TXA ?
[12:27] <ahasenack> apw: I'd rather not remove the history, it's what helped us diagnose why these tests started failing in the first place
[12:27] <ahasenack> (bceause they were not run before when the tests were run in an lxc)
[12:27] <ahasenack> apw: so a) "ignore" it now; or b) change the test to fake a success result if run on s390x, with a link to the bug?
[12:28] <apw> ahasenack, if you remind me the version i can add a hint for now so we can kick it down the road a bit
[12:28] <ahasenack> apw: which version specifically, the one that is failing?
[12:28] <apw> ahasenack, then you can update the test if you get bored of asking for the hint
[12:28] <apw> ahasenack, yep, whatever you think is failing and should not be
[12:28] <apw> imagine i have only read the last 3 lines of irc
[12:29] <ahasenack> apw: >= 1.8.5-2
[12:29] <ahasenack> mine in the queue is 1.8.5-3ubuntu1
[12:29] <ahasenack> bug link is https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1745155
[12:29] <ubot5> Ubuntu bug 1745155 in ocfs2-tools (Ubuntu) "o2image fails on s390x" [Undecided,New]
[12:29] <ahasenack> which also links to https://github.com/markfasheh/ocfs2-tools/issues/22
[15:16] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.16 => 2.02~beta2-36ubuntu3.17] (core)
[15:17] -queuebot:#ubuntu-release- Unapproved: grub2-signed (xenial-proposed/main) [1.66.16 => 1.66.17] (core)
[15:31] -queuebot:#ubuntu-release- New binary: gcc-7-cross [amd64] (bionic-proposed/main) [12ubuntu1] (ubuntu-desktop)
[15:36] <slangasek> jibel: hi, I see you just reassigned LP: #1739675 from gnome-software to shim-signed; I've assigned it back, hopefully the adjusted bug title adds clarity
[15:36] <ubot5> Launchpad bug 1737772 in gnome-software (Ubuntu) "duplicate for #1739675 gnome-software frontend can close while packages are still configuring, breaking debconf prompts (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1)" [High,Confirmed] https://launchpad.net/bugs/1737772
[15:53] <jibel> slangasek, yes it's clear, thanks.
[15:54] <jibel> i didn't see your comment initially sorry about that
[16:09] -queuebot:#ubuntu-release- New binary: sphinx-gallery [amd64] (bionic-proposed/universe) [0.1.13-1ubuntu1] (no packageset)
[17:13] <slashd> bdmurray, sil2100 : (Sorry if I ask twice, the first time I forgot to include bdmurray who is also a SRU vanguard today) could you please (if you have a moment) have a look at landscape-client waiting in the upload queues for T/X/A ?
[17:23] <sil2100> slashd: I can!
[17:23] <sil2100> On it
[17:25] <slashd> sil2100, thanks
[18:02] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (artful-proposed) [16.03-0ubuntu3.17.10.2]
[18:03] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (xenial-proposed) [16.03-0ubuntu2.16.04.3]
[18:18] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (trusty-proposed) [14.12-0ubuntu6.14.04.2]
[18:18] <tjaalton> the excuses list for bionic shows a lot of "test in progress" which seem to be stuck?
[18:19] <tjaalton> for instance, I don't understand why nvidia-384 is stuck there
[18:26] <slangasek> tjaalton: "in progress" generally means "queued", as shown on http://autopkgtest.ubuntu.com/running; the CPU apocalypse has had an impact on autopkgtest throughput
[18:27] <tjaalton> slangasek: ok, the queue length does look long enough
[18:28] <slangasek> Laney: https://wiki.ubuntu.com/EndOfLifeProcess says to ask you to disable zesty in https://git.launchpad.net/~ubuntu-desktop/+git/appstream-cloud/
[18:29] <tjaalton> it's a pity that for instance aptdaemon test takes 3h on arm64 and has always failed
[18:32] <slangasek> Laney: ah, but this is an entry you just added, after you did it for zesty ;)
[18:33] <tjaalton> how about dropping the aptdaemon test?
[18:39] <jdstrand> chrony (currently in universe) is stuck because arm64, armhf and ppc64el autopkgtests are 'in progress'
[18:39] <jdstrand> aiui, these haven't been turned back on. should I just wait? is there a process to request it migrate?
[18:40] <nacc> jdstrand: they are all on now
[18:40] <nacc> jdstrand: just backed up, and slow
[18:40] <jdstrand> ah, ok. cool
[18:40] <jdstrand> I'll just wait then
[18:40] <jdstrand> nacc: thanks
[18:40] <nacc> jdstrand: np
[18:41] <slangasek> tjaalton: a bit of a false optimization to drop the tests from one package that are failing, there are a lot of failing tests across the archive and it's not a problem under normal circumstances
[18:41] <slangasek> fwiw if you have access, autopkgtest queue depth over time: https://cloud.kpi.canonical.com/dashboard/db/ubuntu-foundations?panelId=19&fullscreen
[18:43] <slangasek> ppc64el is having the hardest time keeping up, and there's an open RT about scalingstack for it
[18:51] -queuebot:#ubuntu-release- Unapproved: accepted simple-scan [source] (artful-proposed) [3.26.3-0ubuntu0.17.10.0]
[19:04] <tjaalton> slangasek: just that it takes 3h on arm64 because of timing out.. but anyway, cool graphs :)
[19:26] -queuebot:#ubuntu-release- Unapproved: linux-firmware (xenial-proposed/main) [1.157.15 => 1.157.16] (core, kernel)
[19:26] <slangasek> tjaalton: the time would be better spent porting things from aptdaemon to packagekit and dropping aptdaemon, fwiw
[19:27] -queuebot:#ubuntu-release- Unapproved: rejected linux-firmware [source] (xenial-proposed) [1.157.16]
[20:55] -queuebot:#ubuntu-release- New: accepted gcc-7-cross [amd64] (bionic-proposed) [12ubuntu1]
[20:55] -queuebot:#ubuntu-release- New: accepted sphinx-gallery [amd64] (bionic-proposed) [0.1.13-1ubuntu1]
[21:04] -queuebot:#ubuntu-release- Unapproved: linux-firmware (xenial-proposed/main) [1.157.15 => 1.157.16] (core, kernel)
[21:05] -queuebot:#ubuntu-release- Unapproved: linux-firmware (artful-proposed/main) [1.169.2 => 1.169.3] (core, kernel)
[21:17] <tjaalton> slangasek: indeed, the lack of uploads in the past year made me realize it's going away..
[21:22] <juliank> slangasek: nice graphs in that dashboard
[21:22] <juliank> I'm still not sure how we want down so much in needs-merge in one day last week
[21:23] <juliank> I do feel like we should teach MoM a third state to output, like needs-merge-but-proposed
[21:23] <juliank> matching the gray rows
[21:25] <juliank> oh, and maybe we should track average days old or something
[21:29] <tsimonq2> slangasek: Are you allowed to screenshot for those who do not have access? ;)
[21:30] <slangasek> tsimonq2: allowed, yes, but I don't think it's actually so interesting on a one-off basis; what I really need to do is get a public grafana set up for these
[21:31] <slangasek> the executive summary is "ppc64el queue isn't draining nearly as fast as it should be, and needs investigation"
[21:31] <juliank> Should it drain about as fast as s390x?
[21:31] <juliank> I noticed that s390x is ahead of the others, it was already testing my 3 day old gnutls merge
[21:32] <tsimonq2> slangasek: Sure, thanks.
[21:32] <tsimonq2> slangasek: (Are there similar statistics that Foundations has access to about the Ubuntu Development process that could be interesting?)
[21:33] <juliank> for MoM the stats are in https://merges.ubuntu.com/stats-foundations-bugs.txt BTW
[21:35] <tsimonq2> Right, but that's public :)
[21:35] <juliank> but obviously these are for foundations-bugs packages, not general
[21:35] <juliank> https://merges.ubuntu.com/stats.txt is
[21:35] <juliank> It's 44MB large :D
[21:36] <juliank> starts at 2006-10-26 00:00 event Edgy Release
[21:36] <slangasek> juliank: not /as/ fast as s390x, but before the meltdown, ppc64el was the second fastest to clear its queues
[21:36] <juliank> right
[21:37] <juliank> I won't be looking at the autopkgtests results again until next week I think. I get all these notifications, but stuff just has not been tested yet.
[21:37] <tsimonq2> slangasek: One thing I'm scratching my head on is why half the amd64/i386 builders are disabled...
[21:37]  * juliank hopes weekend clears some of that up
[21:37] <tsimonq2> juliank: Wait, notifications? :D
[21:37] <slangasek> tsimonq2: don't know, that'd be a launchpad team question.  It could be related to an upgrade on one of the two cloud regions
[21:37] <juliank> tsimonq2: Yeah, for my uploads stuck in proposed
[21:38] <juliank> "[proposed-migration] gnutls28 3.5.17-1ubuntu1 stuck in bionic-proposed for 3 days."
[21:38] <juliank> ugh
[21:38] <juliank> I know, it's not tested yet
[21:38] <juliank> that stuff
[21:38] <wgrant> tsimonq2: Many of our compute nodes don't yet have Spectre microcode updates, so we don't have full x86 capacity available.
[21:38] <tsimonq2> juliank: oh, gotcha
[21:39] <slangasek> tsimonq2: as far as statistics, yes there are some generically interesting ones where we're graphing public data (proposed-migration backlog, MoM, etc); those are precisely the ones I want to get onto a public grafana
[21:39] <tsimonq2> wgrant: Alright, does anyone have an ETA for when those will be back? (Even if it's one of {hours,days,weeks,months,years}?)
[21:39] <tsimonq2> slangasek: Right, ok.
[21:40] <tsimonq2> (TIL about Grafana)
[21:40] <wgrant> tsimonq2: The world is waiting for Intel and AMD, unfortunately.
[21:41] <tsimonq2> wgrant: So then why are some builders good and others not? ;)
[21:42] <stgraber> they are not all on the same generation of hardware
[21:42] <tsimonq2> Oh, fair.
[21:42] <tsimonq2> I was just curious; I know Intel had to pull some patches but I didn't dig into it much :)
[21:42] <stgraber> which in this case is a good thing, we could have ended up with no microcode for any of our compute nodes and then the entire build farm would still be offline
[21:43] <tsimonq2> Right. :/
[21:44] <juliank> did any other distro turn of their build nodes BTW?
[21:44] <juliank> would be interesting to know
[21:44] <juliank> but I'm not good at finding this out
[22:00] <Laney> slangasek: Yup, well detected
[22:00] <slangasek> ;)
[22:01] <Laney> Might want a corresponding thing for autopkgtest
[22:03] <slangasek> hmm, what is the corresponding thing in autopkgtest's case?
[22:03] <Laney> something tedious like https://git.launchpad.net/autopkgtest-cloud/commit/?id=4e53dd2c90389f967164b4dd12295942faed5481
[22:03] <slangasek> aha
[22:04] <Laney> most things that might cause errors use distro-info so it's not a big deal
[22:04] <Laney> was slightly fun when doing some admin in the broken zesty period though
[22:05] <Laney> also, pp64el> was wondering if we could use a bit of bos02 for that
[22:05] <Laney> too late for me to investigate that right now: /me inserts brain worm
[23:14] -queuebot:#ubuntu-release- New binary: canid [s390x] (bionic-proposed/none) [0.0~git20170120.15a8ca0-1] (no packageset)
[23:14] -queuebot:#ubuntu-release- New binary: movit [s390x] (bionic-proposed/universe) [1.6.0-1] (kubuntu)
[23:15] -queuebot:#ubuntu-release- New binary: hellfire [s390x] (bionic-proposed/none) [0.0~git20170319.c2272fb-1] (no packageset)
[23:15] -queuebot:#ubuntu-release- New binary: hippomocks [s390x] (bionic-proposed/none) [5.0-1] (no packageset)
[23:18] -queuebot:#ubuntu-release- New binary: canid [ppc64el] (bionic-proposed/universe) [0.0~git20170120.15a8ca0-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: hellfire [ppc64el] (bionic-proposed/universe) [0.0~git20170319.c2272fb-1] (no packageset)
[23:19] -queuebot:#ubuntu-release- New binary: hippomocks [ppc64el] (bionic-proposed/universe) [5.0-1] (no packageset)
[23:20] -queuebot:#ubuntu-release- New binary: movit [ppc64el] (bionic-proposed/universe) [1.6.0-1] (kubuntu)
[23:25] -queuebot:#ubuntu-release- New binary: hellfire [armhf] (bionic-proposed/universe) [0.0~git20170319.c2272fb-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: canid [armhf] (bionic-proposed/universe) [0.0~git20170120.15a8ca0-1] (no packageset)
[23:26] -queuebot:#ubuntu-release- New binary: hellfire [arm64] (bionic-proposed/universe) [0.0~git20170319.c2272fb-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: canid [arm64] (bionic-proposed/universe) [0.0~git20170120.15a8ca0-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: canid [amd64] (bionic-proposed/universe) [0.0~git20170120.15a8ca0-1] (no packageset)
[23:28] -queuebot:#ubuntu-release- New binary: hellfire [amd64] (bionic-proposed/universe) [0.0~git20170319.c2272fb-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: canid [i386] (bionic-proposed/universe) [0.0~git20170120.15a8ca0-1] (no packageset)
[23:29] -queuebot:#ubuntu-release- New binary: movit [armhf] (bionic-proposed/universe) [1.6.0-1] (kubuntu)
[23:30] -queuebot:#ubuntu-release- New binary: hippomocks [amd64] (bionic-proposed/universe) [5.0-1] (no packageset)
[23:30] -queuebot:#ubuntu-release- New binary: movit [amd64] (bionic-proposed/universe) [1.6.0-1] (kubuntu)
[23:31] -queuebot:#ubuntu-release- New binary: pg-cloudconfig [amd64] (bionic-proposed/universe) [0.8] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: hellfire [i386] (bionic-proposed/universe) [0.0~git20170319.c2272fb-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: python-aws-xray-sdk [amd64] (bionic-proposed/universe) [0.95-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: coreschema [amd64] (bionic-proposed/universe) [0.0.4-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: hippomocks [i386] (bionic-proposed/universe) [5.0-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: git-secret [amd64] (bionic-proposed/universe) [0.2.3-1] (no packageset)
[23:34] -queuebot:#ubuntu-release- New binary: movit [i386] (bionic-proposed/universe) [1.6.0-1] (kubuntu)
[23:42] -queuebot:#ubuntu-release- New binary: movit [arm64] (bionic-proposed/universe) [1.6.0-1] (kubuntu)