[00:56] <mwhudson> can someone reject base-files 10.1ubuntu2.2 from bionic UNAPPROVED please
[00:58] -queuebot:#ubuntu-release- Unapproved: base-files (bionic-proposed/main) [10.1ubuntu2.2 => 10.1ubuntu2.3] (core)
[04:51] <slangasek> doko: heh, fwiw binutils-mingw-w64 8ubuntu1 apparently has a completely broken library search path (openat(AT_FDCWD, "no/usr/i686-w64-mingw32/lib/libkernel32.dll.a", O_RDONLY) = -1 ENOENT (No such file or directory))
[05:16] -queuebot:#ubuntu-release- New binary: 389-ds-base [amd64] (cosmic-proposed/universe) [1.4.0.15-1] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: 389-ds-base [s390x] (cosmic-proposed/universe) [1.4.0.15-1] (no packageset)
[05:17] -queuebot:#ubuntu-release- New binary: 389-ds-base [i386] (cosmic-proposed/universe) [1.4.0.15-1] (no packageset)
[05:17] -queuebot:#ubuntu-release- New binary: 389-ds-base [ppc64el] (cosmic-proposed/universe) [1.4.0.15-1] (no packageset)
[05:20] -queuebot:#ubuntu-release- New source: octave-statistics (cosmic-proposed/primary) [1.4.0-2ubuntu1]
[05:21] -queuebot:#ubuntu-release- New binary: 389-ds-base [arm64] (cosmic-proposed/universe) [1.4.0.15-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: 389-ds-base [armhf] (cosmic-proposed/universe) [1.4.0.15-1] (no packageset)
[05:48] -queuebot:#ubuntu-release- New: accepted 389-ds-base [amd64] (cosmic-proposed) [1.4.0.15-1]
[05:48] -queuebot:#ubuntu-release- New: accepted 389-ds-base [armhf] (cosmic-proposed) [1.4.0.15-1]
[05:48] -queuebot:#ubuntu-release- New: accepted 389-ds-base [ppc64el] (cosmic-proposed) [1.4.0.15-1]
[05:48] -queuebot:#ubuntu-release- New: accepted 389-ds-base [arm64] (cosmic-proposed) [1.4.0.15-1]
[05:48] -queuebot:#ubuntu-release- New: accepted 389-ds-base [s390x] (cosmic-proposed) [1.4.0.15-1]
[05:48] -queuebot:#ubuntu-release- New: accepted 389-ds-base [i386] (cosmic-proposed) [1.4.0.15-1]
[05:48] -queuebot:#ubuntu-release- New: accepted octave-statistics [source] (cosmic-proposed) [1.4.0-2ubuntu1]
[05:55] -queuebot:#ubuntu-release- New binary: octave-statistics [amd64] (cosmic-proposed/universe) [1.4.0-2ubuntu1] (no packageset)
[06:57] <ginggs> please accept octave-statistics ^
[07:23] -queuebot:#ubuntu-release- New: accepted octave-statistics [amd64] (cosmic-proposed) [1.4.0-2ubuntu1]
[07:29] <ginggs> ta!
[07:56] -queuebot:#ubuntu-release- Unapproved: libvirt (bionic-proposed/main) [4.0.0-1ubuntu8.3 => 4.0.0-1ubuntu8.4] (ubuntu-server, virt)
[08:35] -queuebot:#ubuntu-release- Unapproved: accepted libvirt [source] (bionic-proposed) [4.0.0-1ubuntu8.4]
[08:52] -queuebot:#ubuntu-release- Unapproved: accepted gpgme1.0 [source] (bionic-proposed) [1.10.0-1ubuntu2]
[08:57] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (bionic-proposed) [3.28.1-0ubuntu4.18.04.3]
[09:08] -queuebot:#ubuntu-release- Unapproved: accepted rkhunter [source] (bionic-proposed) [1.4.6-2~ubuntu18.04.1]
[10:46] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (bionic-proposed/multiverse) [5.2.10-3ubuntu18.04.1 => 5.2.10-3ubuntu18.04.2] (no packageset)
[10:52] <LocutusOfBorg> please reject it ^^
[10:52] <LocutusOfBorg> I fixed twice the same old bug :/
[11:14] <abeato> hey, who is archive admin?
[12:17] <santa_> doko: re: kde autopkgtests - my idea was moving some autopkgtests to debian/rules but I couldn't complete the research properly yet. I wanted to do it in the beginning of the cosmic cycle but I had to fix our automatic tooling to handle the debian merges first
[12:20] <santa_> now that we have proper tooling to handle the merges we could try to give it another shot in the next cycle, after doing  the debian merges with the tooling which, by  now, actually works
[12:41] <lotuspsychje> hey guys we having gnome-shell-common held back when updating system in bionic
[12:41] <lotuspsychje> anyone working on that?
[12:42] <lotuspsychje> another user reported tty after a reboot
[12:42]  * bogusjokes did that
[12:43] <lotuspsychje> tnx for reporting bogusjokes
[12:44] <bogusjokes> i checked the apply upgrades box on reboot, it applied gnome-shell and gnome-shell-common from -upgrades, but libmutter-2-0 is stuck on older version so dependency broke and it only boots into tty now
[12:47] <LocutusOfBorg> tjaalton, syncpackage -f dogtag-pki, right?
[12:47] <tjaalton> LocutusOfBorg: just did
[12:47] <LocutusOfBorg> <3
[12:47] <LocutusOfBorg> lovely thanks
[12:48] <LocutusOfBorg> this should unblock some stuff :D
[12:48] <tjaalton> we'll see..
[12:48] <seb128> lotuspsychje, why is it hold back? could you pastebin a log? what package would be removed if you installed the upgrade?
[12:49] <lotuspsychje> seb128: https://hastebin.com/logurubimu.rb
[12:50] <bogusjokes> it needs to be hold back seb128! it applied for me but since it requires a newer version of libmutter-2-0 than is in the -upgrades repository the whole installation breaks if it upgrades, as it did for me
[12:50] <seb128> lotuspsychje, what happens if you apt install that one?
[12:50] <lotuspsychje> lets c
[12:51] <bogusjokes> The following packages have unmet dependencies:
[12:51] <bogusjokes>  gnome-shell : Depends: libmutter-2-0 (>= 3.28.3-1~ubuntu18.04.1) but 3.28.2-2~ubuntu18.04.1 is to be installed
[12:51] <lotuspsychje> seb128: https://hastebin.com/elaxagiyiz.rb
[12:52] <bogusjokes> libmutter-2-0 3.28.3 has to be pushed to -updates archive, since gnome-shell 3.28.3 is there and requires it
[12:52] <lotuspsychje> better not proceed right? remove ubuntu-desktop?
[12:52] <seb128> right
[12:53] <seb128> seems like the SRU team moved gnome-shell alone and they should have been going together
[12:53] <seb128> I don't think our tools make those case options to the SRU reviewers :/
[12:53] <seb128> SRU team ^
[12:53] <bogusjokes> https://paste.ubuntu.com/p/ttT8jBWySx/
[12:54] <bogusjokes> but might it be a problem with the checkbox for applying updates in gnome when rebooting, since it's hold back with apt and update tool?
[12:55] <jbicha> sil2100: do you want to push mutter into bionic-updates now or we do we need to phase gnome-shell down to 0%?
[12:56] <seb128> bogusjokes, that checkbox shouldn't exist/be used, it doesn't work on debian/ubuntu since the offline mode doesn't handle debconf
[12:56] <seb128> there is a gnome-software SRU in proposed that make it not show, it was displayed by error in some corner cases
[12:57] <bogusjokes> seb128: well, i sure used it and it applied the gnome-shell updates for my installation :D
[12:57] <seb128> how is that incompatible with what I wrote?
[12:58] <bogusjokes> it's not, but it's there, and people use it
[12:58] <seb128> right, that's a bug which has a fix in bionic-proposed
[12:58] <bogusjokes> sweet
[12:58] <seb128> but also the gnome-shell SRU is in a buggy state, which normal apt dist-upgrade users would hit as well
[12:59] <seb128> that's more the problem and what is urgent to fix
[13:00] <seb128> infinity, apw, bdmurray_, slangasek, stgraber, sil2100, ^ someone please do something before it hits more users?
[13:00] <sil2100> I'm around now, let me see the backlog
[13:01] <sil2100> argh
[13:02] <sil2100> I guess I'll phase gnome-shell down to 0% since mutter doesn't have 3 bugs verified
[13:03] <sil2100> But I would prefer if we got mutter out in the nearest 24h
[13:03] <sil2100> Can anyone help verify mutter?
[13:04] <sil2100> Ok, two of those are crash fixes, but the monitor one needs verification
[13:04] <jbicha> since update-manager is the only thing that respects phasing, that still wouldn't help the one who got the update presented in gnome-software :(
[13:05] <sil2100> Yeah, this is why 24 hours for getting mutter released or I revert gnome-shell
[13:06] <sil2100> Damn -proposed
[13:06] <jbicha> Trevinho: are you able to verify the fix for bug 1784398?
[13:08] <sil2100> Phasing set to 0
[13:14] <seb128> jibel, ^can you help?
[13:15] <seb128> sil2100, those are just e.u.c report, not obvious testing to do/follow, worth case they are not fixed but that's not a reason to block the SRU if there are no regression
[13:15] <seb128> and verifying those 3 fixes isn't going to tell you if there are no regression
[13:15] <seb128> so basically what's the point?
[13:17] <sil2100> That's why I just wanted the monitor one verified
[13:17] <sil2100> But I guess we can do without that
[13:18] <sil2100> The change for the monitor one is small enough that I guess I'll just release it as sis
[13:18] -queuebot:#ubuntu-release- New source: initramfs-tools-devices (cosmic-proposed/primary) [0.1]
[13:19] <seb128> well, let's see if Trevinho or jibel can help today
[13:19] <seb128> block it 0% meanwhile
[13:19] <seb128> and unblock later/tomorrow
[13:19] <Trevinho> jbicha: mh no, Laney was affected... But I never noticed that
[13:19] <ogra> abeato, https://launchpad.net/ubuntu/cosmic/+queue now find an archive-admin ;)
[13:20] <Trevinho> seb128: well that wasn't either a e.u.c was related to a Laney issue at debconf
[13:20] <Trevinho> seb128: while e.u.c are quite easier as if the package stays in proposed for a couple of weeks we can easily notice that there are no issues for such version. It's not 100% accurate as proposed is used by less people, but in general I'm quite confident in using those stats.
[13:21] <jbicha> the monitor patch is from the gnome-3-28 branch but hasn't made it into a 3.28 release yet
[13:21] <Trevinho> in case it won't be the case, we can just re-mark the bug, but otherwise I think it's the best way to go
[13:21] <Trevinho> jbicha: yep...
[13:21]  * abeato re-posts https://launchpad.net/ubuntu/cosmic/+queue and waits for slangasek ...
[13:21] <abeato> ogra, thanks a lot
[13:21] <ogra> np
[13:22] <sil2100> Trevinho: ok, I'll take another quick look at e.u.c and if all looks good I'll release mutter as is
[13:22] <ogra> abeato, did you base your -core package on the PPA one ? (thats far ahead, the archive one has not been touched for at least one release)
[13:23] <abeato> ogra, no, in the one in the archive I'm afraid
[13:23] <ogra> if not, we need to sync
[13:23] <ogra> ouch ... k
[13:23] <ogra> (given that there wont be an ubuntu-core 18.10 this isnt a biggie indeed
[13:23] <ogra> )
[13:23] <abeato> yeah, I forgot about the core ppa :/
[13:24] <ogra> well, core images will only happen for 16 or 18
[13:24] <ogra> (which means 18.04)
[13:24] <ogra> so nothing will break
[13:25] <ogra> but we should sync that code into the archive nontheless
[13:25] <Trevinho> sil2100: good, thanks
[13:26] <ogra> abeato, we need to make sure that -devices gets the latest resize from the PPA right after it got out of NEW though to make sure you use the latest fixes
[13:27] <abeato> ogra, yup, will upload a debdiff as soon as that happens
[13:27] <ogra> yeah ... just ping me, happy to sponsor that
[13:28] <abeato> ogra, but we need -devices in main and it is in universe in the queue
[13:28] <ogra> yes, all packages enter through universe
[13:28] <abeato> aha, ok
[13:29] <ogra> it will need to either go into some seed or some main package needs to depend on it to make it want to move over (and then it also needs manual ACKing)
[13:29] <ogra> ... but first it needs to go through NEW
[13:30] <abeato> I see, after it moves in we can make it enter main with the change initramfs-tools-ubuntu-core, that makes it depend on -devices
[13:30] <abeato> s/change/change in/
[13:31] <ogra> i uploaded that alongside btw
[13:31] <ogra> (you should have gotten mail=
[13:31] <ogra> )
[13:31] <abeato> nice!
[13:31] <abeato> but no email yet :p
[13:32] <ogra> weird, i got them immediately, for both packages
[13:33]  * ogra wonders if the archive stopped mailing the person in "Changed-By:" ... 
[13:35] <ogra> or perhaps i just mis-remember ... havent uploaded a deb in ages :)
[13:49] -queuebot:#ubuntu-release- New binary: golang-github-canonicalltd-raft-test [amd64] (cosmic-proposed/universe) [0.0~git20180628.c3345b5-1] (no packageset)
[14:09] <ahasenack> hi, sssd now has a component mismatch: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#sssd
[14:09] <ahasenack> python-sss comes from the same source, but is in universe. Could an archive admin please move it to main, where sssd is?
[14:10] <ahasenack> where sssd-tools* is
[14:10] <ahasenack> (and sssd)
[14:18] -queuebot:#ubuntu-release- New binary: vala [s390x] (cosmic-proposed/universe) [0.41.92-0build1] (ubuntu-desktop)
[14:20] -queuebot:#ubuntu-release- New binary: vala [ppc64el] (cosmic-proposed/universe) [0.41.92-0build1] (ubuntu-desktop)
[14:21] -queuebot:#ubuntu-release- New binary: vala [i386] (cosmic-proposed/universe) [0.41.92-0build1] (ubuntu-desktop)
[14:22] -queuebot:#ubuntu-release- New binary: vala [amd64] (cosmic-proposed/universe) [0.41.92-0build1] (ubuntu-desktop)
[14:28] -queuebot:#ubuntu-release- New binary: vala [arm64] (cosmic-proposed/universe) [0.41.92-0build1] (ubuntu-desktop)
[14:28] -queuebot:#ubuntu-release- New binary: vala [armhf] (cosmic-proposed/universe) [0.41.92-0build1] (ubuntu-desktop)
[14:32] <Trevinho> sil2100: thanks for relasing :)
[14:32] <Trevinho> releasing*
[14:40] <sil2100> yw!
[14:44] -queuebot:#ubuntu-release- Unapproved: cryptsetup (bionic-proposed/main) [2:2.0.2-1ubuntu1 => 2:2.0.2-1ubuntu1.1] (core)
[14:45] -queuebot:#ubuntu-release- New: accepted golang-github-canonicalltd-raft-test [amd64] (cosmic-proposed) [0.0~git20180628.c3345b5-1]
[14:45] -queuebot:#ubuntu-release- New: accepted vala [arm64] (cosmic-proposed) [0.41.92-0build1]
[14:45] -queuebot:#ubuntu-release- New: accepted vala [i386] (cosmic-proposed) [0.41.92-0build1]
[14:45] -queuebot:#ubuntu-release- New: accepted vala [s390x] (cosmic-proposed) [0.41.92-0build1]
[14:45] -queuebot:#ubuntu-release- New: accepted vala [amd64] (cosmic-proposed) [0.41.92-0build1]
[14:45] -queuebot:#ubuntu-release- New: accepted vala [ppc64el] (cosmic-proposed) [0.41.92-0build1]
[14:45] -queuebot:#ubuntu-release- New: accepted vala [armhf] (cosmic-proposed) [0.41.92-0build1]
[14:50] <tkamppeter> The autopkg tests on the build servers stopped working, only the tests on ppc64el and s390x are actually running.
[14:51] <xnox> tkamppeter, that is not true
[14:51] <xnox> tkamppeter, why/how do you assert that?
[14:52] <xnox> yesterday queues on all arches were above 1.5k, now they are about 0.5k everywhere, so clearly 1000s of tests across all arches have executed over the past 48h
[14:54] <xnox> based on KPI stats, it is expected to clear over the weekend.
[14:54] <xnox> private stats are in e.g. https://cdo.okr.canonical.com/d/000000030/ubuntu-foundations?panelId=19&fullscreen&orgId=1
[14:55] <xnox> ppc64el is simply the fastest/more hardware we have, then s390x, then intel, than arms.
[14:55] <tkamppeter> On http://people.canonical.com/~ubuntu-archive/proposed-migration/cosmic/update_excuses.html#gutenprint
[14:55] <tkamppeter> http://people.canonical.com/~ubuntu-archive/proposed-migration/cosmic/update_excuses.html
[14:56] <xnox> look at http://autopkgtest.ubuntu.com/running where in the queue the tests are....
[14:56] <acheronuk> tkamppeter: ppc64el and s390x run a great deal quicker than other arches, so they clear their test backlog much sooner. that is all
[14:56] <tkamppeter> Most tests show amd64: Test in progress, arm64: Test in progress, armhf: Test in progress, i386: Test in progress, ppc64el: Pass, s390x: Pass
[14:56] <xnox> tkamppeter, yes, because there is 18k of tests to run for KDE stack that was uploaded two days ago.....
[14:56] <acheronuk> and test in progress includes when they are queued
[14:56] <tkamppeter> Especially cpdb-libs is stuck in this state since yesterday.
[14:57] <tkamppeter> xnox, OK, then I understand.
[14:57] <xnox> tkamppeter, please open http://autopkgtest.ubuntu.com/running and ctrl-f the package you want, to see how much tests are scheduled ahead of it.
[14:57] <xnox> tkamppeter, there you can also check up as it bubbles up.
[14:59] <xnox> tkamppeter, some tests do get lost - but wait for the queues to be all empty on http://autopkgtest.ubuntu.com/running to retrigger anything that is "not running, not in the queue to run, in-progress state" but i expect that only by like monday or tuesday.
[14:59] <xnox> most likely it will just clear by monday.
[15:19] -queuebot:#ubuntu-release- Unapproved: accepted fonts-liberation [source] (bionic-proposed) [1:1.07.4-7ubuntu0.18.04.1]
[15:33] <slangasek> seb128, sil2100: is gnome-shell + mutter stabilized now?  Should I be rolling back gnome-shell in the -updates pocket as well?
[15:38] -queuebot:#ubuntu-release- Unapproved: accepted fonts-liberation2 [source] (bionic-proposed) [2.00.1-7ubuntu0.18.04.1]
[15:38] -queuebot:#ubuntu-release- Unapproved: maas (bionic-proposed/main) [2.4.0-6981-g011e51b7a-0ubuntu1~18.04.1 => 2.4.2-7034-g2f5deb8b8-0ubuntu1] (ubuntu-server)
[15:41] <sil2100> slangasek: should be all good now
[15:44] <ahasenack> fyi, I'm chasing down the paramiko dep8 failures. They are happening because the tarball is lacking the *.pub files that testsuse. The github paramiko release tarball has them, but the pypi one does not. I'm asking in #paramiko
[15:44] <ahasenack> https://pastebin.ubuntu.com/p/GKgxv64t2K/ shows the missing files
[15:49] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (trusty-proposed/main) [4.15.0-1022.22~14.04.1] (no packageset)
[16:02] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (trusty-proposed) [4.15.0-1022.22~14.04.1]
[16:04] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (bionic-proposed) [2.525.7]
[16:09] -queuebot:#ubuntu-release- Unapproved: rejected tkblt [source] (bionic-proposed) [3.2.7-1ubuntu1]
[16:25] -queuebot:#ubuntu-release- Unapproved: rejected base-files [source] (bionic-proposed) [10.1ubuntu2.2]
[16:37] <tjaalton> could an archive admin remove cockpit-389-ds armhf deb?
[16:39] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.14.7]
[16:40] -queuebot:#ubuntu-release- Unapproved: maas (xenial-proposed/main) [2.3.4-6508-g4f77e30-0ubuntu1 => 2.3.5-6511-gf466fdb-0ubuntu1] (ubuntu-server)
[16:43] -queuebot:#ubuntu-release- Unapproved: accepted software-properties [source] (bionic-proposed) [0.96.24.32.5]
[16:45] <lotuspsychje> seb128: ping me if i have to test the updates on bionic
[16:47] -queuebot:#ubuntu-release- Unapproved: accepted cryptsetup [source] (bionic-proposed) [2:2.0.2-1ubuntu1.1]
[16:50] <lotuspsychje> sil2100 seb128 ok system updating here, new kernels and gnome-shell upgrading lookin good
[16:51] <seb128> lotuspsychje, thx
[16:51] <lotuspsychje> +1 for the fix guys
[16:57] <ahasenack> fix for the paramiko dep8 failures: https://code.launchpad.net/~ahasenack/ubuntu/+source/paramiko/+git/paramiko/+merge/353660
[16:58] <slangasek> tjaalton: done
[17:00] <slangasek> abeato: hi, not sure I'm going to have time to look at NEW processing today, sorry
[17:03] <abeato> slangasek, nw, it is not super-urgent, thanks
[17:07] <tjaalton> slangasek: thanks
[17:17] <LocutusOfBorg> jbicha, you might have a guile issue?
[17:18] <LocutusOfBorg> are you working to port stuff in main to guile 2.2?
[17:23] <jbicha> LocutusOfBorg: no issue, there's only one package in main using guile :)
[17:26] <LocutusOfBorg> :)
[17:26] <LocutusOfBorg> nice!
[17:26] <LocutusOfBorg> maybe we should merge both guiles now
[18:35] <infinity> sil2100: What was with the "review" on that bionic/ubiquity upload? :P
[18:37] <infinity> mwhudson: ^--- and while I'm mentioning it, want to fix that to not include 1MB of accidental package updates from cosmic?
[18:52] <ahasenack> hi, sssd now has a component mismatch: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#sssd
[18:52] <ahasenack> python-sss comes from the same source, but is in universe. Could an archive admin please move it to main, where sssd{,-tools} is?
[18:54] <infinity> ahasenack: Done.
[18:55] <ahasenack> infinity: \o/ thanks
[19:19] <sil2100> infinity: I thought those happen automatically - and since the package updates landed in -updates already, no harm in pulling those into ubiquity... where actually I forgot to check if those were actually just from -updates
[19:21] <sil2100> eh, too warm here, I blame it on the heat
[19:22] <sil2100> My brain tissue has melted
[19:24] <infinity> sil2100: They were from cosmic. :P
[19:24] <infinity> And definitely not "automatic", it was mwhudson building in a dirty checkout.
[19:25] <sil2100> Ok ok, just another fallout of not looking at the sources that were being updated
[19:25] <sil2100> You got me there, argh
[19:25] <sil2100> Sorry about that
[19:28] <sil2100> ...and that would explain why I thought I didn't see the d-i/manifest updated
[19:29] <sil2100> Uber fail
[19:30] -queuebot:#ubuntu-release- New binary: grub2 [arm64] (cosmic-proposed/main) [2.02+dfsg1-5ubuntu1] (core)
[19:31] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.3 => 2.02-2ubuntu8.4] (core)
[19:37] -queuebot:#ubuntu-release- New binary: neutron-fwaas-dashboard [amd64] (cosmic-proposed/universe) [1.3.0-1ubuntu1] (no packageset)
[19:50] <slangasek> hmm why does MoM only list nagios3 3.5.1.dfsg-2.1ubuntu4?
[19:57] <slangasek> ah because it was removed from unstable
[20:12] <slangasek> jbicha: have you gotten notification emails about your zc.lockfile sync being stuck in -proposed for 77 days (because you dropped an Ubuntu delta that is required by revdeps)?
[20:13] <slangasek> jbicha: I have had my doubts about whether notification emails are properly sent out to people who have done syncs
[20:22] -queuebot:#ubuntu-release- New binary: grub2 [amd64] (cosmic-proposed/main) [2.02+dfsg1-5ubuntu1] (core)
[20:34] <mwhudson> infinity: oh ffs
[20:35] -queuebot:#ubuntu-release- New binary: grub2 [i386] (cosmic-proposed/main) [2.02+dfsg1-5ubuntu1] (core)
[20:40] <mwhudson> i hate native packages
[20:52] <mwhudson> infinity, sil2100: uploaded 18.04.14.8
[20:53] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.14.7 => 18.04.14.8] (core)
[22:30] -queuebot:#ubuntu-release- New binary: pscan-tfbs [ppc64el] (cosmic-proposed/universe) [1.2.2-2] (no packageset)
[22:30] -queuebot:#ubuntu-release- New binary: pscan-tfbs [s390x] (cosmic-proposed/universe) [1.2.2-2] (no packageset)
[22:31] -queuebot:#ubuntu-release- New binary: pscan-tfbs [amd64] (cosmic-proposed/universe) [1.2.2-2] (no packageset)
[22:31] -queuebot:#ubuntu-release- New binary: pscan-tfbs [armhf] (cosmic-proposed/universe) [1.2.2-2] (no packageset)
[22:31] -queuebot:#ubuntu-release- New binary: pscan-tfbs [arm64] (cosmic-proposed/universe) [1.2.2-2] (no packageset)
[22:31] -queuebot:#ubuntu-release- New binary: pscan-tfbs [i386] (cosmic-proposed/universe) [1.2.2-2] (no packageset)
[22:33] -queuebot:#ubuntu-release- New: accepted pscan-tfbs [amd64] (cosmic-proposed) [1.2.2-2]
[22:33] -queuebot:#ubuntu-release- New: accepted pscan-tfbs [armhf] (cosmic-proposed) [1.2.2-2]
[22:33] -queuebot:#ubuntu-release- New: accepted pscan-tfbs [ppc64el] (cosmic-proposed) [1.2.2-2]
[22:33] -queuebot:#ubuntu-release- New: accepted pscan-tfbs [arm64] (cosmic-proposed) [1.2.2-2]
[22:33] -queuebot:#ubuntu-release- New: accepted pscan-tfbs [s390x] (cosmic-proposed) [1.2.2-2]
[22:33] -queuebot:#ubuntu-release- New: accepted pscan-tfbs [i386] (cosmic-proposed) [1.2.2-2]
[22:38] -queuebot:#ubuntu-release- Unapproved: console-setup (bionic-proposed/main) [1.178ubuntu2.6 => 1.178ubuntu2.7] (core)
[22:52] <slangasek> and I check if the gnucash build failures are reproducible, and it now ftbfs on all archs due to gcc-8 because of course it should
[22:55] <slangasek> /<<PKGBUILDDIR>>/libgnucash/engine/Account.cpp:575:59: error: ‘void g_type_class
[22:55] <slangasek> _add_private(gpointer, gsize)’ is deprecated [-Werror=deprecated-declarations]
[22:55] <slangasek>      g_type_class_add_private(klass, sizeof(AccountPrivate));
[22:55] <slangasek>                                                            ^
[22:55] <slangasek> ... and the first gtk3 implementation of gnucash is already using deprecated functions
[23:19] -queuebot:#ubuntu-release- New: accepted grub2 [amd64] (cosmic-proposed) [2.02+dfsg1-5ubuntu1]
[23:19] -queuebot:#ubuntu-release- New: accepted grub2 [i386] (cosmic-proposed) [2.02+dfsg1-5ubuntu1]
[23:19] -queuebot:#ubuntu-release- New: accepted grub2 [arm64] (cosmic-proposed) [2.02+dfsg1-5ubuntu1]
[23:19] -queuebot:#ubuntu-release- New: accepted neutron-fwaas-dashboard [amd64] (cosmic-proposed) [1.3.0-1ubuntu1]