[00:06] -queuebot:#ubuntu-release- Unapproved: focuswriter (bionic-proposed/universe) [1.6.11-1 => 1.6.12-1] (no packageset) (sync)
[00:06] -queuebot:#ubuntu-release- Unapproved: accepted focuswriter [sync] (bionic-proposed) [1.6.12-1]
[00:08] -queuebot:#ubuntu-release- Unapproved: ostree (bionic-proposed/universe) [2018.4-1 => 2018.4-2] (ubuntugnome) (sync)
[00:08] -queuebot:#ubuntu-release- Unapproved: gnumeric (bionic-proposed/universe) [1.12.35-1 => 1.12.35-1.1] (desktop-extra) (sync)
[00:14] -queuebot:#ubuntu-release- Unapproved: flent (bionic-proposed/universe) [1.2.1-1 => 1.2.2-1] (no packageset) (sync)
[00:14] -queuebot:#ubuntu-release- Unapproved: accepted flent [sync] (bionic-proposed) [1.2.2-1]
[00:40] -queuebot:#ubuntu-release- Unapproved: mugshot (bionic-proposed/universe) [0.3.2-0ubuntu1 => 0.4.0-0ubuntu1] (ubuntustudio, xubuntu)
[00:41] <bluesabre> ^ No functional changes, only translations, URLs, and version number bump to stable
[00:52] -queuebot:#ubuntu-release- Unapproved: xubuntu-docs (bionic-proposed/universe) [18.04 => 18.04.1] (xubuntu)
[01:20] -queuebot:#ubuntu-release- Unapproved: docker.io (bionic-proposed/universe) [17.03.2-0ubuntu5 => 17.12.1-0ubuntu1] (no packageset)
[01:21] -queuebot:#ubuntu-release- Unapproved: accepted docker.io [source] (bionic-proposed) [17.12.1-0ubuntu1]
[01:21] -queuebot:#ubuntu-release- Unapproved: docker.io (xenial-proposed/universe) [17.03.2-0ubuntu1~16.04.1 => 17.03.2-0ubuntu2~16.04.1] (no packageset)
[01:40] -queuebot:#ubuntu-release- Unapproved: fslint (bionic-proposed/universe) [2.44-3 => 2.44-4] (no packageset) (sync)
[01:40] -queuebot:#ubuntu-release- Unapproved: accepted fslint [sync] (bionic-proposed) [2.44-4]
[02:23] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-settings (bionic-proposed/universe) [18.04.15 => 18.04.16] (ubuntu-mate)
[02:25] -queuebot:#ubuntu-release- Unapproved: netplan.io (bionic-proposed/main) [0.34.1 => 0.35] (core)
[04:22] -queuebot:#ubuntu-release- Unapproved: keyutils (bionic-proposed/main) [1.5.9-9.2ubuntu1 => 1.5.9-9.2ubuntu2] (core)
[05:09] -queuebot:#ubuntu-release- Unapproved: libreoffice-dictionaries (bionic-proposed/main) [1:6.0.3-2 => 1:6.0.3-3] (personal-gunnarhj, ubuntu-desktop) (sync)
[05:33] -queuebot:#ubuntu-release- Unapproved: jss (bionic-proposed/universe) [4.4.2-6 => 4.4.3-1] (no packageset) (sync)
[05:34] -queuebot:#ubuntu-release- Unapproved: accepted jss [sync] (bionic-proposed) [4.4.3-1]
[05:34] -queuebot:#ubuntu-release- Unapproved: freeipa (bionic-proposed/universe) [4.7.0~pre1+git20180411-1 => 4.7.0~pre1+git20180411-2] (no packageset) (sync)
[05:35] -queuebot:#ubuntu-release- Unapproved: dogtag-pki (bionic-proposed/universe) [10.6.0~beta2-3 => 10.6.0-1] (no packageset) (sync)
[05:35] -queuebot:#ubuntu-release- Unapproved: accepted dogtag-pki [sync] (bionic-proposed) [10.6.0-1]
[05:35] -queuebot:#ubuntu-release- Unapproved: accepted freeipa [sync] (bionic-proposed) [4.7.0~pre1+git20180411-2]
[06:26] -queuebot:#ubuntu-release- Unapproved: command-not-found (bionic-proposed/main) [18.04.2 => 18.04.3] (core)
[06:32] -queuebot:#ubuntu-release- Unapproved: accepted keyutils [source] (bionic-proposed) [1.5.9-9.2ubuntu2]
[06:39] -queuebot:#ubuntu-release- Unapproved: qemu (bionic-proposed/main) [1:2.11+dfsg-1ubuntu6 => 1:2.11+dfsg-1ubuntu7] (ubuntu-server, virt)
[06:43] -queuebot:#ubuntu-release- Unapproved: networkd-dispatcher (bionic-proposed/universe) [1.7-0ubuntu1 => 1.7-0ubuntu2] (no packageset)
[06:47] -queuebot:#ubuntu-release- Unapproved: xfsprogs (bionic-proposed/main) [4.9.0+nmu1ubuntu1 => 4.9.0+nmu1ubuntu2] (core)
[07:01] -queuebot:#ubuntu-release- Unapproved: hedgewars (bionic-proposed/universe) [0.9.23-dfsg-2build1 => 0.9.24-dfsg-2] (no packageset) (sync)
[07:01] -queuebot:#ubuntu-release- Unapproved: virtualbox (bionic-proposed/multiverse) [5.2.8-dfsg-7 => 5.2.10-dfsg-1] (ubuntu-cloud) (sync)
[07:01] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (bionic-proposed/multiverse) [5.2.8-2 => 5.2.10-1] (no packageset) (sync)
[07:02] -queuebot:#ubuntu-release- Unapproved: accepted hedgewars [sync] (bionic-proposed) [0.9.24-dfsg-2]
[07:02] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-ext-pack [sync] (bionic-proposed) [5.2.10-1]
[07:30] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-17.18]
[07:40] <LocutusOfBorg> please accept virtualbiox, this upload should make it work again as guest, with the GL native implementation
[07:40] <LocutusOfBorg> (not enabled by default, I'll do a call for testing later once it is accepted!)
[07:46] -queuebot:#ubuntu-release- Unapproved: kdeclarative (bionic-proposed/universe) [5.44.0-0ubuntu2 => 5.44.0-0ubuntu3] (kubuntu)
[08:16] -queuebot:#ubuntu-release- Unapproved: thermald (bionic-proposed/main) [1.7.0-3 => 1.7.0-5] (core) (sync)
[08:16] -queuebot:#ubuntu-release- Unapproved: ubuntu-report (bionic-proposed/main) [1.0.8 => 1.0.9] (no packageset)
[08:59] -queuebot:#ubuntu-release- Unapproved: zfs-linux (artful-proposed/main) [0.6.5.11-1ubuntu3.3 => 0.6.5.11-1ubuntu3.4] (core)
[09:00] -queuebot:#ubuntu-release- Unapproved: zfs-linux (xenial-proposed/main) [0.6.5.6-0ubuntu20 => 0.6.5.6-0ubuntu21] (no packageset)
[09:05] -queuebot:#ubuntu-release- New: accepted musescore-sftools [amd64] (bionic-proposed) [20180325-1]
[09:05] -queuebot:#ubuntu-release- New: accepted musescore-sftools [armhf] (bionic-proposed) [20180325-1]
[09:05] -queuebot:#ubuntu-release- New: accepted musescore-sftools [ppc64el] (bionic-proposed) [20180325-1]
[09:05] -queuebot:#ubuntu-release- New: accepted musescore-sftools [arm64] (bionic-proposed) [20180325-1]
[09:05] -queuebot:#ubuntu-release- New: accepted musescore-sftools [s390x] (bionic-proposed) [20180325-1]
[09:05] -queuebot:#ubuntu-release- New: accepted musescore-sftools [i386] (bionic-proposed) [20180325-1]
[09:08] -queuebot:#ubuntu-release- Unapproved: accepted thermald [sync] (bionic-proposed) [1.7.0-5]
[09:10] -queuebot:#ubuntu-release- Unapproved: accepted apparmor [source] (bionic-proposed) [2.12-4ubuntu5]
[09:26] -queuebot:#ubuntu-release- Unapproved: ubuntu-settings (bionic-proposed/main) [18.04.4 => 18.04.5] (ubuntu-desktop)
[09:37] -queuebot:#ubuntu-release- Unapproved: ukui-control-center (bionic-proposed/universe) [1.1.2-0ubuntu1 => 1.1.3-0ubuntu1] (ubuntukylin)
[09:38] -queuebot:#ubuntu-release- Unapproved: virtualbox-hwe (bionic-proposed/multiverse) [5.2.10-dfsg-1ubuntu18.04.1 => 5.2.10-dfsg-2ubuntu18.04.1] (no packageset)
[09:39] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-hwe [source] (bionic-proposed) [5.2.10-dfsg-2ubuntu18.04.1]
[09:47] -queuebot:#ubuntu-release- Unapproved: accepted command-not-found [source] (bionic-proposed) [18.04.3]
[10:08] -queuebot:#ubuntu-release- Unapproved: accepted gnome-calendar [source] (bionic-proposed) [3.28.1-1ubuntu2]
[10:17] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (bionic-proposed) [2:12.0.0-0ubuntu3]
[10:29] -queuebot:#ubuntu-release- Unapproved: accepted mate-terminal [source] (bionic-proposed) [1.20.0-3ubuntu1]
[10:36] <Laney> seb128: i'm reviewing this gjs... it seems a bit concerning at this point - how confident are you in it?
[10:36] <Laney> it's hard to tell where the patches are from since they aren't properly attributed in d/patches/*.patch
[10:36] <Laney> and there are different GC fixes in master atm
[10:36] <Laney> which aren't in this upload
[10:37] <Laney> so... it's confusing
[10:45] <sergiusens> sil2100: hello there. Are you the current guardian of ubuntu-image? It seems to be blocking snapcraft on bionic due to an unrelated error on booting the created image
[10:51] <seb128> Laney, duflu and Trevinho are confident it's not going to create issues and the problem it addresses as being judged as important for the release by will
[10:52] <Laney> I understand that fixing what is apparently a big leak is important
[10:52] <seb128> Laney, duflu mentioned on the bug that there are more fixes that could be backported indeed, but the ones in master didn't address the most important issue from what I understood
[10:53] <Laney> This upload is quite difficult to review though
[10:53] <sil2100> sergiusens: hey!
[10:53] <seb128> right, I appreciate that, I had that conversation before upload with duflu on -desktop as you might have read
[10:53] <sil2100> sergiusens: yeah, let me take a look
[10:53] <sil2100> sergiusens: one ADT test there is flaky recently, it might be that
[10:53] <seb128> Laney, it basically going to down on whether we trust duflu/Trevinho opinion on the fix
[10:54] <Laney> not really
[10:54] <sil2100> sergiusens: ok, re-running those, it looks like the usual flakyness ;/ Wasn't so flaky before bionic
[10:55] <Laney> We could not have to go on trusting opinions if we use the SRU process to verify the fix
[10:55] <Laney> in any event I would really appreciate proper attribution
[10:58] <seb128> Laney, you mean "use the SRU process"? willcooke said he would do a call for testing once it's in proposed
[11:00] <seb128> Laney, I can ask duflu to fix the attribution thing tomorrow, I'm unsure who wrote the patches and where he got them from
[11:00] <seb128> he's eod by now though
[11:00] <Laney> two of them are from https://gitlab.gnome.org/GNOME/gjs/merge_requests/114, which I found by searching
[11:00] <ubot5-ng> GNOME bug (Merge request) 114 in gjs "Queue a GC when a toggle reference goes from >1 to 1" (comments: 15) [Opened]
[11:00] <Laney> there is another patch that I can't find the source of though
[11:00] <seb128> the cairo regression fix?
[11:01] <seb128> that's from master afaik, dunno why they didn't commit it in .52 as well
[11:01] <Laney> yes
[11:01] <Laney> it says "Unreviewed" on it
[11:02] <Laney> ok
[11:02] <seb128> Laney, https://gitlab.gnome.org/GNOME/gjs/commit/8510bede
[11:02] <seb128> the upstream commit includes that "Unreviewed" for some reason
[11:03] <Laney> alright, so again proper attribution in the patches please
[11:03] <seb128> like renaming it git_ and writting "backport from master" in the changelot?
[11:03] <seb128> changelog
[11:04] <Laney> Origin: upstream, <url>
[11:04] <seb128> k, I though we usually didn't bother for backports of upstream commit
[11:04] <seb128> people usually seem to throw a git format-patch patch in there
[11:04] <seb128> but ok, if you want I can do that
[11:05] <seb128> is the upload fine then once the attribution question sorted out?
[11:05] <Laney> those are just things that make it harder to review
[11:05] <seb128> I'm unsure we addressed the fact that you find the commits not easy to review or what would make it feel better about those
[11:05] <seb128> right
[11:05] <seb128> I can fix that part
[11:05] <Laney> otherwise, I don't know, I'm worried about having a different behaviour here and that we'll be on our own when it comes to debugging
[11:05] <seb128> I share that concern
[11:06] <Laney> we'll have patches which aren't upstream, and we won't have patches which are
[11:06] <seb128> but upstream isn't acting on a tempo that works for us
[11:06] <Laney> and it's final freeze tomorrow
[11:06] <Laney> which means any time to react and fix things is very limited
[11:06] <seb128> right
[11:06] <seb128> I argued about that yesterday on -desktop
[11:06] <darkxst> Laney, I was hoping to do a proper review of the patches last night but its been a crazy week
[11:06] <Laney> ok, I didn't follow that
[11:06] <Laney> hey darkxst
[11:06] <seb128> but our options are basically to take that upload
[11:07] <seb128> or to have a big leak in the release
[11:07] <seb128> will and others fear it might lead to bad reviews/user opinion
[11:07] <Laney> and have more managed testing by using an SRU
[11:08] <darkxst> Laney that is my feeling too from a quick review of patches
[11:08] <seb128> will & duflu believed it would be a big error to release with that leak
[11:08] <seb128> willcooke, ^ the gjs fix is being nacked it sounds like
[11:08] <Laney> do they remember that upgrades aren't turned on until .1?
[11:08] <seb128> yes
[11:08] <Laney> right...
[11:09] <seb128> seems like the interweb is already hating on us for thinking about releasing with a such leak
[11:09] <seb128> and they fear it builds up as a negative PR against the release
[11:09] <seb128> anyway I'm just the messenger there
[11:09] <Laney> would it be more hateful to release with a buggy GC?
[11:09] <Laney> or cause slowdowns or something
[11:09] <seb128> that's the point where I said I trusted duflu & Trevinho
[11:09] <seb128> they both believe it's not possible/likely
[11:10] <seb128> and duflu said it tested it to no end
[11:10] <didrocks> (I don't think "when people upgrade" is something to take into account as people reviewing/PReleasing/making noise about it are just installing it fresh in a VM/machine IMHO)
[11:11] <Laney> OK, please remove the pressure from the press from me.
[11:11] <seb128> I'm just the messenger there, I'm relying the argument that were made to me when I pushed back sponsoring yesterday
[11:12] <darkxst> seb128, I am not against landing the patches, but wouldnt personally do it this late in the cycle
[11:12] <seb128> neither would I
[11:12] <seb128> but we are there now
[11:12] <seb128> it's late with an issue some people arguing we can't release with
[11:12] <seb128> so our options are limited
[11:12] <Laney> Being able to say that we are carefully considering these fixes rather than rushing them in to satisfy some bad headlines is a fine story.
[11:13] <seb128> " and duflu said it tested it to no end"
[11:13] <seb128> I wrote that just before
[11:13] <seb128> unsure if you saw?
[11:13] <seb128> Trevinho and duflu believe it's a right move
[11:13] <Laney> I did see that
[11:13] <Laney> I know!
[11:13] <seb128> I wouldn't say we are rushing
[11:13] <Laney> But that's not the same as giving the change to everyone is it?
[11:13] <seb128> no
[11:14] <seb128> as said the people who know the best that stack in our team judge it's the right call at this point
[11:14] <seb128> I don't know that codebase enough to judge
[11:14] <Laney> ok, I think I abstain
[11:14] <sergiusens> thanks sil2100
[11:15] <Laney> someone that's not in the same team should review things like this
[11:15] <seb128> Laney, k, I can understand that
[11:15] <seb128> yeah, in fact I was not expecting you to pick on that
[11:15] <seb128> but thanks for the review/sharing your opinion!
[11:15] <darkxst> seb128, did you know the nvidia prop driver leaks caches into the reported gnome-shell memory usage that is actually in GPU RAM?
[11:16] <darkxst> its a complex world and the reported gnome-shell memory usage is not always accurate
[11:16] <Laney> I don't see a particular leak in the gnome-shell process here either
[11:16] <willcooke> Wimpress, is that the same issue you mentioned re: nvidia driver ^
[11:16] <seb128> duflu has been testing on intel
[11:16] <Laney> and it's been running since April 05
[11:16] <seb128> so it's not an nvidia issue we are talking about
[11:17] <seb128> Laney, https://irclogs.ubuntu.com/2018/04/16/%23ubuntu-desktop.html#t09:59 has more context if you are interested
[11:18] <seb128> again I'm only the messenger/uploader here
[11:19] <seb128> Laney, darkxst, I'm glad you guys don't see the leak, the bug linked to the upload shows a real problem with lot of users unhappy about it so let's not dismiss there is a problem
[11:19] <Laney> I believe it, and I'm not dismissing it
[11:19] <Laney> it is different to a problem that is urgent for everybody
[11:19] <Laney> ok, that's me, I need someone else to make a decision on this thing
[11:19] <seb128> "duflu, I'm not arguing against the issue or shooting the messenger, I just think you overstate the proper by making it sounds like it makes GNOME unusable for everyone"
[11:19] <seb128> that's what I wrote on that log in pointed out
[11:20] <seb128> said differently I'm on the same line as you are
[11:20] <seb128> anyway
[11:21] <seb128> if r-t is unhappy about the fix for release maybe we can at least get it approved in proposed and block it there and see how it goes/turn it into a SRU if needed
[11:21] <seb128> at least if it's in proposed it would get more testing
[11:23] <darkxst> seb128, that was only an example, I have spent alot of time over the years looking into -shell memomry leaks
[11:23] <seb128> shame that nobody has been doing that in recent cycles
[11:24] <seb128> or we wouldn't be there
[11:24] <darkxst> it is impossible to tell from the surface what are caches etc
[11:24] <seb128> I think you should give more credit to duflu
[11:24] <seb128> he spent most of his cycle digging in gnome-shell performances issues and got several fixes commited upstream
[11:24] <seb128> he probably understand things better than you think he does
[11:27] <darkxst> seb128, I'm not arguing that he doesnt understand things, more that its super late to be hastily landing GC patches
[11:28] <seb128> darkxst, I think "hastily" is wrong
[11:28] <seb128> duflu has been testing those carefully for weeks from what he said
[11:28] <darkxst> who else has tested them?
[11:28] <seb128> in anything the issue is that it hasn't been hasted, if we had uploaded before he tested them they would be in
[11:29] <darkxst> apart from a few developers?
[11:29] <seb128> what's your point?
[11:30] <seb128> what fixes/commits are tested by more than a few developers before being commited?
[11:30] <seb128> none
[11:30] <didrocks> chicken & egg argument here :)
[11:30] <willcooke> If they get in to proposed then we can do a wide call for testing this week
[11:31] <seb128> right, I asked about that earlier but that didn't get a response
[11:31] <seb128> anyway I need to get some food, I didn't eat anything since 7am and I feeling weak, back in half an hour
[11:31] <willcooke> the people in the desktop team best qualified to comment on the suitablility of that patch say that its good, so I would really like to get more eyes on it from the general community
[11:32] <jbicha> willcooke: PPA then?
[11:32] <seb128> PPA doesn't give us enough visibility
[11:32] <seb128> or at least less
[11:32] <seb128> and if it's in proposed it can be a 0 day SRU
[11:32] <willcooke> well, I really want it in for release so that would add more delay wouldn';t it?
[11:35] <willcooke> what seb128 said
[11:38] <seb128> Laney, willcooke, I need to talk to Trevinho later or duflu tomorrow, but upstream commited that to master 6 hours ago, https://gitlab.gnome.org/GNOME/gjs/commit/a6b6fc1342
[11:38] <seb128> which I wonder is supposed/could address the same problem in a different way
[11:38] <seb128> though upstream didn't comment on the other merge request/didn't close it as superseeded
[11:39] <seb128> but unsure changing our strategy at this point would be wise
[11:39] <seb128> even if it's commited in master it didn't get more testing than our patch
[11:39] <seb128> and duflu made the work to verify that the patches he included fixes the issue we want to see resolved
[11:39] <Laney> I think you've made your case
[11:39] <seb128> we would have to redo the validation work on that other commit
[11:40] <seb128> k, I guess that's a polite "please shut up now" :p
[11:40] <seb128> which I guess is the signal I should really go and grab something to eat :)
[11:40] <seb128> bbiab
[11:42] -queuebot:#ubuntu-release- Unapproved: gnome-shell (bionic-proposed/main) [3.28.0-0ubuntu5 => 3.28.1-0ubuntu1] (desktop-extra, mozilla, ubuntu-desktop)
[11:44] <Laney> sil2100: or apw: in case you missed me saying above; please review gjs
[11:44] <Laney> as you can see people from the desktop team are lobbying for it
[11:45] <Laney> but I'm also in that team so I would like to not be the one deciding since it seems potentially risky
[11:52] <Laney> (garnacho is still hoping for it to go in upstream though, I just asked him in #gnome-shell)
[12:04] <willcooke> the same patch Laney?
[12:04] <Laney> yeah
[12:05] <willcooke> thx
[12:07] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (bionic-proposed) [3.191]
[12:07] -queuebot:#ubuntu-release- Unapproved: xfsprogs (trusty-proposed/main) [3.1.9ubuntu2 => 3.1.9ubuntu2.1] (core)
[12:12] -queuebot:#ubuntu-release- Unapproved: accepted software-properties [source] (bionic-proposed) [0.96.24.32]
[12:12] -queuebot:#ubuntu-release- Unapproved: rejected mutter [source] (bionic-proposed) [3.28.1-1]
[12:12] -queuebot:#ubuntu-release- Unapproved: mutter (bionic-proposed/main) [3.28.0-2 => 3.28.1-1] (desktop-extra, ubuntu-desktop) (sync)
[12:13] -queuebot:#ubuntu-release- Unapproved: accepted nginx [source] (bionic-proposed) [1.14.0-0ubuntu1]
[12:19] -queuebot:#ubuntu-release- Unapproved: accepted fluidr3mono-gm-soundfont [sync] (bionic-proposed) [2.315-4]
[12:20] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-release-upgrader [source] (bionic-proposed) [1:18.04.17]
[12:31] -queuebot:#ubuntu-release- Unapproved: peony-extensions (bionic-proposed/universe) [1.1.1-0ubuntu1 => 1.1.1-0ubuntu2] (no packageset)
[12:33] <LocutusOfBorg> apw, can you please remove hedgewars on ppc64el binaries? they have been building by luck, but never been supported at all, a simple no-change rebuild should make the FTBFS again, I already asked to remove such architectures in Debian too
[12:34] <LocutusOfBorg> I tried a rebuild, but seriously, the support for BE machines is just broken
[12:40] -queuebot:#ubuntu-release- Unapproved: peony (bionic-proposed/universe) [1.1.1-0ubuntu1 => 1.1.1-0ubuntu2] (ubuntukylin)
[12:40] -queuebot:#ubuntu-release- Unapproved: accepted haproxy [sync] (bionic-proposed) [1.8.7-1]
[12:40] -queuebot:#ubuntu-release- Unapproved: accepted ibus [source] (bionic-proposed) [1.5.17-3ubuntu4]
[12:55] <cjwatson> LocutusOfBorg: ... abstaining on the general issue here, but you know that ppc64el isn't BE, right?
[12:56] <LocutusOfBorg> cjwatson, let me do things more clear, thanks!
[12:57] <LocutusOfBorg> upstream provides a clang-based pascal->C conversion stuff that makes things build even without fpc compiler
[12:57] <LocutusOfBorg> but this sucks :)
[13:00] <LocutusOfBorg> and yes, somebody should just bootstrap fpc everywhere, now it should work also on ppc64el
[13:03] <ginggs> LocutusOfBorg: fpc support for ppc64el still not in released version
[13:04] <LocutusOfBorg> this is why I prefer to just kick out hedgewars there
[13:04] <LocutusOfBorg> we don't need to have angry bug reports about a game that crashes during online play :)
[13:04] <LocutusOfBorg> people might loose and give the fault to the package and not their skills :p
[13:06] -queuebot:#ubuntu-release- Unapproved: 389-ds-base (bionic-proposed/universe) [1.3.7.10-1 => 1.3.7.10-1ubuntu1] (no packageset)
[13:07] -queuebot:#ubuntu-release- Unapproved: accepted 389-ds-base [source] (bionic-proposed) [1.3.7.10-1ubuntu1]
[13:18] -queuebot:#ubuntu-release- Unapproved: ubuntu-meta (bionic-proposed/main) [1.416 => 1.417] (core)
[13:31] <sforshee> Laney: we haven't been able to promote our raspi2 kernel for bionic because britney is waiting for arm64 test results. My understanding is that we won't get any test results because we don't have cloud images for it, what can we do about that?
[13:53] <Laney> sforshee: Sure we do, but I'm not sure why results didn't come in, one second
[13:56] <Laney> sforshee: hmm, ok, they all failed but I'm not sure right now why that didn't get associated with the request on update_excuses
[13:56] <Laney> e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/a/acpi-call/20180406_175859_b6c0d@/log.gz
[13:57] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (bionic-proposed) [2.522]
[13:58] -queuebot:#ubuntu-release- Unapproved: accepted gjs [source] (bionic-proposed) [1.52.1-1ubuntu1]
[13:58] -queuebot:#ubuntu-release- Unapproved: accepted sddm [source] (bionic-proposed) [0.17.0-1ubuntu6]
[13:59] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-settings [source] (bionic-proposed) [18.04.16]
[13:59] <Laney> who's doing these reviews? I'd left a comment on the bug report for livecd-rootfs
[13:59] <apw> no me
[14:01] -queuebot:#ubuntu-release- Unapproved: accepted networkd-dispatcher [source] (bionic-proposed) [1.7-0ubuntu2]
[14:01] -queuebot:#ubuntu-release- Unapproved: accepted xfsprogs [source] (bionic-proposed) [4.9.0+nmu1ubuntu2]
[14:02] -queuebot:#ubuntu-release- Unapproved: accepted kdeclarative [source] (bionic-proposed) [5.44.0-0ubuntu3]
[14:02] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-settings [source] (bionic-proposed) [18.04.5]
[14:02] -queuebot:#ubuntu-release- Unapproved: accepted ukui-control-center [source] (bionic-proposed) [1.1.3-0ubuntu1]
[14:04] <Laney> looks like seb128 got his gjs ;-)
[14:04] -queuebot:#ubuntu-release- Unapproved: accepted peony-extensions [source] (bionic-proposed) [1.1.1-0ubuntu2]
[14:04] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (bionic-proposed) [1.417]
[14:04] -queuebot:#ubuntu-release- Unapproved: accepted peony [source] (bionic-proposed) [1.1.1-0ubuntu2]
[14:08] <sforshee> Laney: I don't suppose we have a console log for any of these test cases? Given that the kernel config for raspi2 is pretty specific to that hardware it wouldn't surprise me to find that it doesn't work in that environment
[14:08] <Laney> sforshee: it's there at the end of that log
[14:10] <sforshee> Laney: oh so that's all we got. In which case I think we can probably conclude that it's because of not having efi support
[14:10] <seb128> Laney, yeah, I got lucky :)
[14:13] -queuebot:#ubuntu-release- Unapproved: mate-menu (bionic-proposed/universe) [18.04.3-1 => 18.04.3-2ubuntu1] (ubuntu-mate)
[14:14] -queuebot:#ubuntu-release- Unapproved: mate-themes (bionic-proposed/universe) [3.22.16-1 => 3.22.16-2ubuntu1] (ubuntu-mate)
[14:17] <sforshee> Laney: if we can get the results associated with the request in update_excuese we would at least be able to hint those
[14:17] <Laney> sforshee: you can force-skiptest anyway
[14:17] <Laney> if it's not supposed to work we probably shouldn't evne trigger those
[14:17] <sforshee> agreed about that
[14:18] <apw> Laney, i think you can only force-skiptest when a result is finished right ?
[14:19] <apw> Laney, and britney thinks these are in flight
[14:19] <Laney> apw: I think you can do it any time
[14:19] <Laney> try it
[14:19] <apw> vorlon:force-badtest linux-raspi2/all linux/all/armhf
[14:20] -queuebot:#ubuntu-release- Unapproved: accepted netplan.io [source] (bionic-proposed) [0.35]
[14:20] -queuebot:#ubuntu-release- Unapproved: youker-assistant (bionic-proposed/universe) [2.2.7-0ubuntu5 => 3.0.0-0ubuntu1] (ubuntukylin)
[14:20] <Laney> skiptest
[14:20] <apw> oh, derp, ok will try that
[14:20] <apw> Laney, oh, but that will ignore all of its tests forever going forward right ?
[14:21] <Laney> no it's just for the triggering package/version
[14:35] <Laney> stgraber: wow at that upload :P
[14:35] <Laney> didn't fancy doing a point release?
[14:37] <stgraber> Laney: haha, no, not quite, we have a few more things we'll want in before we tag an actual point release
[14:42] -queuebot:#ubuntu-release- Unapproved: zfs-linux (bionic-proposed/main) [0.7.5-1ubuntu14 => 0.7.5-1ubuntu15] (core)
[14:49] -queuebot:#ubuntu-release- Unapproved: rax-nova-agent (bionic-proposed/main) [2.1.13-0ubuntu2 => 2.1.13-0ubuntu3] (no packageset)
[14:49] -queuebot:#ubuntu-release- Unapproved: accepted rax-nova-agent [source] (bionic-proposed) [2.1.13-0ubuntu3]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted corosync [source] (bionic-proposed) [2.4.3-0ubuntu1]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted gnumeric [sync] (bionic-proposed) [1.12.35-1.1]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (bionic-proposed) [3.0.0-0ubuntu4]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted mate-themes [source] (bionic-proposed) [3.22.16-2ubuntu1]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted mutter [sync] (bionic-proposed) [3.28.1-1]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted pacemaker [source] (bionic-proposed) [1.1.18-0ubuntu1]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-report [source] (bionic-proposed) [1.0.9]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted xubuntu-docs [source] (bionic-proposed) [18.04.1]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell [source] (bionic-proposed) [3.28.1-0ubuntu1]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted mate-menu [source] (bionic-proposed) [18.04.3-2ubuntu1]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted ostree [sync] (bionic-proposed) [2018.4-2]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox [sync] (bionic-proposed) [5.2.10-dfsg-1]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice-dictionaries [sync] (bionic-proposed) [1:6.0.3-3]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (bionic-proposed) [1:2.11+dfsg-1ubuntu7]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted mugshot [source] (bionic-proposed) [0.4.0-0ubuntu1]
[14:50] -queuebot:#ubuntu-release- Unapproved: accepted youker-assistant [source] (bionic-proposed) [3.0.0-0ubuntu1]
[14:52] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.32.3.2 => 2.32.5] (desktop-core, ubuntu-server)
[14:52] -queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.32.3.2~14.04 => 2.32.5~14.04] (no packageset)
[14:53] -queuebot:#ubuntu-release- Unapproved: snapd (artful-proposed/main) [2.32.3.2+17.10 => 2.32.5+17.10] (desktop-core, ubuntu-server)
[14:57]  * apw looks at snapd
[14:59] -queuebot:#ubuntu-release- Unapproved: software-properties (bionic-proposed/main) [0.96.24.32 => 0.96.24.34] (desktop-core, ubuntu-server)
[15:06] -queuebot:#ubuntu-release- Unapproved: gnome-online-accounts (bionic-proposed/main) [3.28.0-0ubuntu1 => 3.28.0-0ubuntu2] (ubuntu-desktop)
[15:09] -queuebot:#ubuntu-release- Unapproved: snapcraft (bionic-proposed/universe) [2.41+18.04.1 => 2.41+18.04.2] (no packageset)
[15:10] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (bionic-proposed) [2.41+18.04.2]
[15:16] -queuebot:#ubuntu-release- Unapproved: indicator-china-weather (bionic-proposed/universe) [2.2.7-0ubuntu1 => 2.2.8-0ubuntu1] (ubuntukylin)
[15:18] -queuebot:#ubuntu-release- Unapproved: ukui-menus (bionic-proposed/universe) [1.1.2-0ubuntu1 => 1.1.3-0ubuntu1] (ubuntukylin)
[15:33] -queuebot:#ubuntu-release- Unapproved: curtin (bionic-proposed/main) [18.1-1-g45564eef-0ubuntu1 => 18.1-5-g572ae5d6-0ubuntu1] (ubuntu-desktop, ubuntu-server)
[15:41] -queuebot:#ubuntu-release- Unapproved: dogtag-pki (bionic-proposed/universe) [10.6.0-1 => 10.6.0-1ubuntu1] (no packageset)
[15:42] -queuebot:#ubuntu-release- Unapproved: accepted dogtag-pki [source] (bionic-proposed) [10.6.0-1ubuntu1]
[15:56] -queuebot:#ubuntu-release- Unapproved: freeipa (bionic-proposed/universe) [4.7.0~pre1+git20180411-2 => 4.7.0~pre1+git20180411-2ubuntu1] (no packageset)
[15:57] -queuebot:#ubuntu-release- Unapproved: accepted freeipa [source] (bionic-proposed) [4.7.0~pre1+git20180411-2ubuntu1]
[16:17] -queuebot:#ubuntu-release- Unapproved: rejected software-properties [source] (bionic-proposed) [0.96.24.34]
[16:28] -queuebot:#ubuntu-release- Unapproved: accepted gnome-online-accounts [source] (bionic-proposed) [3.28.0-0ubuntu2]
[16:36] -queuebot:#ubuntu-release- Unapproved: kbuild (bionic-proposed/universe) [1:0.1.9998svn3149+dfsg-1 => 1:0.1.9998svn3149+dfsg-2] (no packageset) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: accepted kbuild [sync] (bionic-proposed) [1:0.1.9998svn3149+dfsg-2]
[17:30] <rbalint> hi, i'm seeking approval of two FFe-s, LP: #1764797 and LP: #1488620
[17:30] <ubot5`> Launchpad bug 1764797 in unattended-upgrades (Ubuntu) "[FFe] please merge unattended-upgrades 1.1 (main) from Debian unstable (main)" [Critical,New] https://launchpad.net/bugs/1764797
[17:30] <ubot5`> Launchpad bug 1488620 in initramfs-tools (Ubuntu) "[FFe] Add LZ4 support to initramfs-tools" [Low,New] https://launchpad.net/bugs/1488620
[17:32] <rbalint> the first one is really critical, the second one is something that got a lot of positive feedback and it would be very nice to have in Bionic
[17:37] -queuebot:#ubuntu-release- Unapproved: neutron (bionic-proposed/main) [2:12.0.0-0ubuntu3 => 2:12.0.1-0ubuntu1] (openstack, ubuntu-server)
[17:46] <slangasek> tsimonq2: your ffmpeg sync is not migrating because it drops libav-tools, which has reverse-dependencies.  Please follow up.
[17:50] <LocutusOfBorg> slangasek, I quickly checked, they are all "recommended"
[17:50] <LocutusOfBorg> can we just ignore the issue?
[17:51] <slangasek> LocutusOfBorg: are you responding wrt ffmpeg or something else?
[17:53] <slangasek> LocutusOfBorg: if ffmpeg: p-m does not block on recommends.  Please look at the update_output results, those packages have depends, not recommends.
[18:01] <LocutusOfBorg> yep, found that now, thanks! I was getting off the train
[18:03] <LocutusOfBorg> alternate dependencies are fine? e.g. python*-woo
[18:03] <rbalint> slangasek: i'm about to upload FFe-approved fix for LP: #1764220, can i go ahead now?
[18:03] <ubot5`> Launchpad bug 1764220 in dpkg (Ubuntu) "[FFe] dpkg zstd support" [Undecided,Triaged] https://launchpad.net/bugs/1764220
[18:03] <slangasek> rbalint: yes you can
[18:03] <slangasek> LocutusOfBorg: proposed-migration checks for installability of the package, and does a very reliable job of it
[18:05] -queuebot:#ubuntu-release- Unapproved: kbuild (bionic-proposed/universe) [1:0.1.9998svn3149+dfsg-2 => 1:0.1.9998svn3149+dfsg-3] (no packageset) (sync)
[18:05] -queuebot:#ubuntu-release- Unapproved: accepted kbuild [sync] (bionic-proposed) [1:0.1.9998svn3149+dfsg-3]
[18:05] -queuebot:#ubuntu-release- Unapproved: virtualbox (bionic-proposed/multiverse) [5.2.10-dfsg-1 => 5.2.10-dfsg-2] (ubuntu-cloud) (sync)
[18:05] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (bionic-proposed/multiverse) [5.2.10-1 => 5.2.10-2] (no packageset) (sync)
[18:06] <rbalint> slangasek: thanks, it lands in a few minutes
[18:06] <LocutusOfBorg> bouncing email for maintainer field are RC in debian ^^ I fixed vbox now
[18:06] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-ext-pack [sync] (bionic-proposed) [5.2.10-2]
[18:06] <slangasek> rbalint: wrt initramfs-tools, I'm nacking this; it's too late in the cycle, not a critical bug, and doesn't have the same rationale as the dpkg changes for needing to be landed in previous release by GA
[18:07] <tsimonq2> slangasek: ack
[18:07] <rbalint> slangasek: :-(, but ok
[18:55] -queuebot:#ubuntu-release- Unapproved: dpkg (bionic-proposed/main) [1.19.0.5ubuntu1 => 1.19.0.5ubuntu2] (core)
[18:58] <jbicha> slangasek: interested in removing gksu? bug 1740618
[18:58] <ubot5`> bug 1740618 in umit (Ubuntu) "Remove gksu from Ubuntu" [Undecided,New] https://launchpad.net/bugs/1740618
[19:05] <slangasek> jbicha: reverse-depends points a finger at peony-extensions which is not in your task list?
[19:07] <slangasek> jbicha: ah, has just been resolved to an NBS; removing
[19:08] <rbalint> slangasek: do you have an opinion on the unattended-upgrades FFe, too?
[19:09] <slangasek> rbalint: sorry, I have it queued up but haven't been able to review it yet (which means my opinion is that I think it should be approved, but I need to read the fine print)
[19:09] <rbalint> slangasek: ok, np, thanks!
[19:15] <fossfreedom> hi - anyone around that can help me diagnose why both the 32bit and 64bit daily Ubuntu Budgie 18.04 is booting straight to the live session - seems to miss the installer
[19:16] <jbicha> fossfreedom: did that happen with the Final Beta also?
[19:16] <slangasek> jbicha: if you believe Debian bug #496448 is sufficient rationale for removal of macchanger-gtk+libui-dialog-perl independent of gksu, can you please open that as a separate bug?  I do not consider a Recommends: on a removed package to be grounds for removal, and solving a Recommends: on a removed package by removing the recommending package doesn't do anything to improve the user's experience
[19:16] <ubot5`> Debian bug 496448 in libui-dialog-perl "libui-dialog-perl: Dialog backend allows execution of arbitrary shell commands (CVE-2008-7315)" [Grave,Open] http://bugs.debian.org/496448
[19:16] <slangasek> on upgrade
[19:17] <slangasek> fossfreedom: LP: #1763739 and I'm looking into it (currently on xubuntu)
[19:17] <ubot5`> Launchpad bug 1763739 in ubiquity (Ubuntu) "[xubuntu, budgie & mate] ISO boots directly to desktop" [Critical,Triaged] https://launchpad.net/bugs/1763739
[19:17] <fossfreedom> thanks slangasek
[19:18] <flocculant> fossfreedom: I had seen it - and commented in that on budgie ^^ think I also reported on the tracker against budgie (and mate for the record)
[19:18] <fossfreedom> cheers - much appreciated
[19:20] <slangasek> jbicha: btw, gksu is also seeded in ubuntukylin daily-live despite not having any revdeps there; please follow through on the seed cleanup w/ ubuntukylin team
[19:21] <slangasek> jbicha: hmm or perhaps that's transitive and goes away now that peony-gksu is dropped; n/m
[19:30] -queuebot:#ubuntu-release- Unapproved: leptonlib (bionic-proposed/universe) [1.75.3-2 => 1.75.3-3] (kubuntu) (sync)
[19:33] <jbicha> filed bug 1765178
[19:33] <ubot5`> bug 1765178 in macchanger-gtk (Ubuntu) "Please remove libui-dialog-perl; open security vulnerability" [Undecided,New] https://launchpad.net/bugs/1765178
[19:35] <teward> is there a listing of the 'queue' of autopkgtests that are queued to run but haven't been run yet?
[19:36] <jbicha> teward: https://autopkgtest.ubuntu.com/running
[19:36] <teward> ah, the one page that takes eternity to load for me... which explains why I didn't see this earlier :P
[19:37] <jbicha> it loads much faster when the queue is empty :|
[19:37] <teward> i believe it.  (I'm keeping an eye on all the autopkgtests that nginx 1.14.0-0ubuntu1 triggered for any signs of the weird issue I found that xnox opened a bug about... or failures in general, but I don't think any of the triggers that nginx 1.14.0 set off have been reached yet...)
[19:40] <slangasek> teward: nginx tests are queued behind glibc, because both glibc and nginx hit the threshold where their tests go in the 'large' queue and nginx was uploaded after glibc.  So you can expect to wait a while
[19:41] <teward> indeed.
[19:41] <teward> i'd expect that, but it's just still on my radar nonetheless :)
[19:48] <tsimonq2> slangasek: Is there a way I can find out what other packages I have in proposed?
[19:50] <tsimonq2> (Hm, I wonder if I could hack something up with UDD and launchpadlib?)
[19:50] <slangasek> ¯\(シ)/¯
[19:51] <tsimonq2> ¯\_(ツ)_/¯
[19:51] <tsimonq2> OK :)
[19:52] <nacc> tsimonq2: packages you've uploaded to proposed, you mean?
[19:52]  * tsimonq2 adds to post-release TODO list...
[19:52] <tsimonq2> nacc: Yeah.
[19:52] <tsimonq2> Sometimes I lose track.
[19:52] <tsimonq2> (Look at how many packages I upload...)
[19:52] <teward> *hands tsimonq2 a link* does https://launchpad.net/~tsimonq2/+related-packages help?
[19:52] <teward> or rather, https://launchpad.net/~tsimonq2/+uploaded-packages
[19:53] <nacc> the problem is the 'uploaded to' there isn't where it currently is
[19:53] -queuebot:#ubuntu-release- Unapproved: tesseract (bionic-proposed/universe) [4.00~git2219-40f43111-1.2 => 4.00~git2288-10f4998a-2] (kubuntu) (sync)
[19:53] <nacc> it's a release name
[19:53] <nacc> but i do think that's roughly what you want
[19:53] <teward> i think that's going to be an issue regardless, though, isn't it?
[19:53] <nacc> tsimonq2: it would be nice to have a slightly more developer-focused view of that, and for +synchronized_packages
[19:53] <nacc> *synchronised
[19:54] <tsimonq2> I can probably query those via launchpadlib and cross-reference each upload with publishing history...
[19:54] <nacc> tsimonq2: i think for each of those, you just need to go into the publishing state
[19:54] <nacc> yeah :)
[19:54] <ginggs> please accept tesseract, needed to fix autopkgtests on ocrmypdf, and leptonlib is a related package with only a CVE fix
[19:54] <nacc> teward: right, i think that's just what laucnhpad web is surfacing, there is more data in the object in lplib (if i had to guess)
[19:56] <tsimonq2> nacc: So, for me that'd be fine. I've only uploaded 289 times. But if I look at e.g. vorlon's page, that gets unmanageable...
[19:56] <nacc> tsimonq2: right, i think you're right on a tool (ubuntu-dev-tools), i was just suggesting starting with bascially the query that produces that page
[19:56] <tsimonq2> I could probably add launchpadlib integration to that fancy p-m script (that's hiding right now!) so I can just query that...
[19:57] <tsimonq2> nacc: Thanks. :)
[20:09] -queuebot:#ubuntu-release- Unapproved: gnocchi (bionic-proposed/universe) [4.2.0-0ubuntu4 => 4.2.0-0ubuntu5] (no packageset)
[20:10] -queuebot:#ubuntu-release- Unapproved: accepted gnocchi [source] (bionic-proposed) [4.2.0-0ubuntu5]
[20:25] <cjwatson> IMO the best place to surface that information would be in update_excuses
[20:26] <tsimonq2> cjwatson: That has no uploader info.
[20:26] <tsimonq2> But yeah, that's my plan.
[20:26] <tsimonq2> (Parse that then find out who uploaded each.)
[20:26] <cjwatson> tsimonq2: You misunderstand; I'm suggesting that that would be the best place to *add* this information
[20:27] <tsimonq2> Ahh.
[20:29] <slangasek> p-m already does have some concept of this, in order to generate the nag mails
[20:30] <tsimonq2> If someone wants to report a bug and assign it to me, that'd be cool.
[20:31] <tsimonq2> Otherwise I can do so myself, but post-release.
[20:32] <jdstrand> can someone help me look at why all the apparmor autopkgtests are failing? eg: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/a/apparmor/20180418_173050_fb390@/log.gz
[20:32] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-guide (bionic-proposed/universe) [18.04.3-0ubuntu1 => 18.04.4-0ubuntu1] (ubuntu-mate)
[20:32] <jdstrand> it has to do with package dependencies not being installable. It isn't clear to me how the failures relate at all to my upload
[20:33] <jdstrand> Depends: apparmor perl (not considered)
[20:33] <jdstrand> hmm
[20:33] <jdstrand> perl was in the mix with that log url
[20:35]  * jdstrand notes all the other autopkgtests that consume apparmor pass, it is just the 'apparmor' autopkgtests fail on every arch
[20:36] <tsimonq2> Perl has not migrated yet.
[20:36] <tsimonq2> It could be that.
[20:37] <jdstrand> maybe... I guess when perl migrates I could retry the tests
[22:00] -queuebot:#ubuntu-release- Unapproved: unity-settings-daemon (bionic-proposed/universe) [15.04.1+18.04.20180216-0ubuntu1 => 15.04.1+18.04.20180413-0ubuntu1] (mythbuntu) (sync)
[22:04] -queuebot:#ubuntu-release- Unapproved: gnome-initial-setup (bionic-proposed/main) [3.28.0-2ubuntu3 => 3.28.0-2ubuntu4] (ubuntugnome)
[22:22] -queuebot:#ubuntu-release- Unapproved: mugshot (bionic-proposed/universe) [0.4.0-0ubuntu1 => 0.4.0-1] (ubuntustudio, xubuntu) (sync)
[22:49] -queuebot:#ubuntu-release- Unapproved: stress-ng (bionic-proposed/universe) [0.09.24-1 => 0.09.25-1] (no packageset) (sync)
[22:50] -queuebot:#ubuntu-release- Unapproved: accepted stress-ng [sync] (bionic-proposed) [0.09.25-1]
[22:56] -queuebot:#ubuntu-release- Unapproved: prewikka (bionic-proposed/universe) [4.1.5-1 => 4.1.5-2] (no packageset) (sync)
[22:57] -queuebot:#ubuntu-release- Unapproved: accepted prewikka [sync] (bionic-proposed) [4.1.5-2]
[23:25] -queuebot:#ubuntu-release- Unapproved: gnome-initial-setup (bionic-proposed/main) [3.28.0-2ubuntu3 => 3.28.0-2ubuntu5] (ubuntugnome)
[23:31] <slangasek> eta 40h for the amd64 autopkgtest queue to clear, hmph