[06:21] -queuebot:#ubuntu-release- Unapproved: qemu (bionic-proposed/main) [1:2.11+dfsg-1ubuntu7.19 => 1:2.11+dfsg-1ubuntu7.20] (ubuntu-server, virt)
[06:21] -queuebot:#ubuntu-release- Unapproved: qemu (disco-proposed/main) [1:3.1+dfsg-2ubuntu3.5 => 1:3.1+dfsg-2ubuntu3.6] (ubuntu-server, virt)
[07:05] <ginggs> LocutusOfBorg: why not move to Texas?
[08:17] <LocutusOfBorg> ginggs, -EDIDNTGET
[08:29] <cjwatson> infinity: Plausibly related.  Does it happen in an unstable chroot?
[08:46] <ginggs> LocutusOfBorg: plenty of space in Texas (old BOfH joke)
[08:50] <LocutusOfBorg> lol! :D
[08:51] <cjwatson> The only way to increase space there would be to increase the allocation for all builders, which would need care to ensure that it doesn't run the whole cloud out of space.  A more immediately practical solution is often to remove intermediate outputs during the build.
[09:14] <Laney> :|
[09:15] <Laney> second time this has happened now - rabbitmq has stopped delivering events to the autopkgtest workers
[09:15] <Laney> if I restart them, they get one job only and then sit around waiting for the next queue item
[09:15] <Laney> which is there but isn't sent to them
[09:16] <apw> Laney, as if they had not acked it, or tried to ack the wrong 'correspondance-id'; do you check the return from ack (if it returns things)
[09:17] <doko> cjwatson: that's probably triggered by building for one more python version ...
[09:19] <doko> hmm, no, b-d on python3-dev
[09:22] <doko> update_excuses is outdated
[09:22] <LocutusOfBorg> cjwatson, I was trying to avoid an useless patching of opencv, specially if Debian seems to have generally a little bit more space wrt Ubuntu (it might be not the only package)
[09:22] <LocutusOfBorg> but yes, I can steal the itk4 removal bits post build and to some ppa testing
[09:23] <Laney> apw: the acking seems to work fine, at least as far as I can tell
[09:23] <Laney> it's like the server craps itself somehow
[09:25] <apw> we had a lot of trouble with our one on precise doing things like that; i have not seen the saem since it moved to bionic
[09:25] <apw> though it tended to do that when a queue was not being drained and it ran out of literally everything to store the incoming messages on
[09:25] <apw> i assume you've checked for that kind of thing
[09:26] <Laney> I don't see anything in the logs
[09:26] <Laney> but if you wanted to look too, maybe you would ?
[09:26] <Laney> rabbitmq-server/0
[09:26] <Laney> it is xenial so perhaps when we upgrade it'll be better ?
[09:53] <Laney> ok, recovered it for now with apw's help
[09:54] <Laney> (it was blocking on a memory threshold which we increased, should probably be deployed on a larger instance next time)
[10:40] <RikMills> could an AA please remove the s390x binary from telegram-desktop? debian maintainer was patching the build scripts to make that build, but has now dropped that, as the resulting build had other issues that meant it didn't work anyway
[11:08] -queuebot:#ubuntu-release- Unapproved: zsys (eoan-proposed/universe) [0.2.2 => 0.2.2+19.04] (no packageset)
[11:34] <cjwatson> infinity: I analysed the rumur failure and filed https://bugs.debian.org/943705 with my findings
[11:35] -queuebot:#ubuntu-release- Unapproved: rejected carla [source] (eoan-proposed) [2.0.0-0ubuntu4+gitde67dcb]
[11:37] <sil2100> Laney: hey! Looking at the gnome-terminal eoan SRU - you want to copy it forward into focal once it's in eoan? SInce I see focal is still on 3.34.0
[11:38] <Laney> yeah was going to
[11:38] <Laney> for some of the later SRUs I did upload backports
[11:39] <Laney> but I didn't go back and do that for the earlier ones, hoped copy up would be ok
[11:42] <sil2100> Yeah, I think it should be ok at least now,
[11:42] <sil2100> As long as we don't forget to bin copy it ;p
[11:43] <Laney> aye
[11:46] -queuebot:#ubuntu-release- Unapproved: accepted gnome-terminal [source] (eoan-proposed) [3.34.2-1ubuntu1]
[11:48] <LocutusOfBorg> please NBS proposed cleanup? missing build on amd64: python-bzrlib, python-bzrlib-dbg (from 2.7.0+bzr6622-17ubuntu1)
[11:52] <cjwatson> hm, that feels like a proposed-migration bug?  those binaries don't exist in focal-proposed, so the only way to stop p-m saying that seems to be to remove them from focal, which seems like a bad idea without a full migration
[11:57] -queuebot:#ubuntu-release- Unapproved: accepted chromium-browser [source] (eoan-proposed) [77.0.3865.120-0ubuntu1.19.10.1]
[12:02] -queuebot:#ubuntu-release- Unapproved: haproxy (bionic-proposed/main) [1.8.8-1ubuntu0.5 => 1.8.8-1ubuntu0.6] (ubuntu-server)
[12:03] -queuebot:#ubuntu-release- Unapproved: haproxy (disco-proposed/main) [1.8.19-1ubuntu1 => 1.8.19-1ubuntu1.1] (ubuntu-server)
[12:03] -queuebot:#ubuntu-release- Unapproved: haproxy (eoan-proposed/main) [2.0.5-1 => 2.0.5-1ubuntu0.1] (ubuntu-server)
[12:04] <LocutusOfBorg> somebody accepted remmina-plugin-kwallet in main, it should be probably moved to universe, what do you think?
[12:05] -queuebot:#ubuntu-release- Unapproved: accepted haproxy [source] (disco-proposed) [1.8.19-1ubuntu1.1]
[12:05] -queuebot:#ubuntu-release- Unapproved: accepted haproxy [source] (eoan-proposed) [2.0.5-1ubuntu0.1]
[12:05] -queuebot:#ubuntu-release- Unapproved: accepted haproxy [source] (bionic-proposed) [1.8.8-1ubuntu0.6]
[12:06] <LocutusOfBorg> unless you want to consider MIRing libkf5wallet-bin
[12:06] <LocutusOfBorg> can anybody please do the magic?
[12:08] -queuebot:#ubuntu-release- Unapproved: accepted opencryptoki [source] (eoan-proposed) [3.11.1+dfsg-0ubuntu2.1]
[12:09] -queuebot:#ubuntu-release- Unapproved: accepted opencryptoki [source] (disco-proposed) [3.11.0+dfsg-0ubuntu2.1]
[12:16] -queuebot:#ubuntu-release- Unapproved: rejected mutter [source] (eoan-proposed) [3.34.1+git20191022-1ubuntu1]
[12:17] -queuebot:#ubuntu-release- Unapproved: rejected gnome-shell [source] (eoan-proposed) [3.34.1+git20191024-1ubuntu1~19.04.1]
[12:18] <sil2100> Laney: (I assume you have uploaded gnome-shell there, looks like a version error - 19.04.1 instead of 19.10.1?)
[12:18] <sil2100> ^
[12:22] -queuebot:#ubuntu-release- Unapproved: accepted wslu [source] (eoan-proposed) [2.3.2-0ubuntu2~19.10.0]
[12:23] <cjwatson> LocutusOfBorg: remmina-plugin-kwallet moved to universe
[12:35] -queuebot:#ubuntu-release- Unapproved: accepted wslu [source] (disco-proposed) [2.3.2-0ubuntu2~19.04]
[12:49] -queuebot:#ubuntu-release- Unapproved: accepted wslu [source] (bionic-proposed) [2.3.2-0ubuntu2~18.04.0]
[12:54] -queuebot:#ubuntu-release- Unapproved: accepted wslu [source] (xenial-proposed) [2.3.2-0ubuntu2~16.04.0]
[12:58] -queuebot:#ubuntu-release- Unapproved: rejected cinder [sync] (disco-proposed) [2:14.0.1-0ubuntu3]
[13:14] -queuebot:#ubuntu-release- Unapproved: accepted cinder [source] (disco-proposed) [2:14.0.2-0ubuntu1]
[13:17] <Laney> sil2100: ah!
[13:18] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (disco-proposed) [2:19.0.3-0ubuntu1]
[13:29] <RikMills> proposed migration runs are crashing with a connection error
[13:29] <RikMills> not sure if someone gets an alert on that, so just saying
[13:30] <Laney> run*s*?
[13:31] <RikMills> last 2
[13:31] <Laney> just watch this one
[13:31] <Laney> I restarted rabbitmq
[13:32] <RikMills> ok. fingers crossed
[13:35] <Laney> not that we need any more test requests :-)
[13:44] <LocutusOfBorg> tga
[13:44] <LocutusOfBorg> thanks for remmina
[14:01] -queuebot:#ubuntu-release- Unapproved: gnome-shell (eoan-proposed/main) [3.34.1-1ubuntu1 => 3.34.1+git20191024-1ubuntu1~19.10.1] (desktop-extra, mozilla, ubuntu-desktop)
[14:02] <Laney> sil2100: proper version there now, thanks!
[15:10] <RikMills> Laney: failed with a slightly different error, and restarted again on a new run
[15:11] <Laney> completely different
[15:11] <Laney> but yes, I know, I'm watching
[15:11] <Laney> if that keeps happening we'll need to beef up this code with a retry
[15:13] <RikMills> ok. thanks :)
[15:14] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-68.77~16.04.1] (kernel)
[15:16] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-68.77~16.04.1] (kernel)
[15:21] -queuebot:#ubuntu-release- Unapproved: open-iscsi (bionic-proposed/main) [2.0.874-5ubuntu2.7 => 2.0.874-5ubuntu2.8] (ubuntu-desktop, ubuntu-server)
[15:25] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-68.77~16.04.1]
[15:25] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-68.77~16.04.1]
[15:29] <Laney> sil2100: just noticed
[15:29] <Laney> I: [Mon Oct 28 15:28:48 2019] - rust-rand-isaac/0.2.0-1 stuck for 48 days (email last sent at 0 days old, threshold for sending 35 days), emailing
[15:29] <Laney> I: [Mon Oct 28 15:28:48 2019] - Failed to send mail! Is SMTP server running?
[15:29] <Laney> I: [Mon Oct 28 15:28:48 2019] - {'': (501, b'5.1.3 Bad recipient address syntax')}
[15:29] <Laney> in proposed-migration logs
[15:30] <sil2100> Laney: oh, looks like something's busted in the Robert-code, I can take a look at that
[15:32] <Laney> I like the "it's probably the system' fault" error message :D
[15:32] <Laney> system's*
[15:34] <Eickmeyer> sil2100: Thanks for the reject on that, I'll upload a new version. Your reply clarified something for me. Thanks!
[16:16] <Laney> looks like there's a perl -8 and a perl -9
[16:16]  * Laney kills the -8 jobs
[16:28] <Laney> that was GREAT!
[16:30] -queuebot:#ubuntu-release- Unapproved: python3.8 (disco-proposed/universe) [3.8.0-1~19.04 => 3.8.0-3~19.04] (no packageset)
[16:31] -queuebot:#ubuntu-release- Unapproved: python3.8 (eoan-proposed/universe) [3.8.0-1 => 3.8.0-3~19.10] (no packageset)
[16:33] -queuebot:#ubuntu-release- Unapproved: python3-stdlib-extensions (bionic-proposed/main) [3.6.8-1~18.04 => 3.6.9-1~18.04] (core)
[16:34] <rbalint> sil2100, if you have some sru cycles left could you please accept open-iscsi?
[16:42] <sil2100> rbalint: what series?
[16:44] -queuebot:#ubuntu-release- New source: python3.8 (bionic-proposed/primary) [3.8.0-3~18.04]
[16:52] <rbalint> sil2100, bionic
[17:05] -queuebot:#ubuntu-release- Unapproved: accepted open-iscsi [source] (bionic-proposed) [2.0.874-5ubuntu2.8]
[17:07] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-68.77] (core, kernel)
[17:09] <infinity> cjwatson: Ta.
[17:10] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-68.77] (core, kernel)
[17:56] <vorlon> jamespage: Debian has removed neutron-lbaas as "replaced by Octavia"; are we good to drop it in focal also?
[17:59] <RikMills> can these binaries be removed in -release please?
[17:59] <RikMills> telegram-desktop/s390x: debian maintainer stopped patching to build on this, as the build is not usable anyway.
[18:00] <RikMills> calibre ppc64el/s390x: switched to building with qtwebengine, not available on those arches
[18:01] <RikMills> both are part of the Qt transition
[18:14] <ginggs> RikMills: files bugs, subscribe ~ubuntu-archive
[18:24] <RikMills> never had to do that before for removals
[18:30] <ginggs> RikMills: you've just been lucky
[18:33] <RikMills> vorlon: you want bugs?
[18:34] <ginggs> ...this is how you get bugs :D
[18:35] <RikMills> I don't mind. on binaries in the past I have just asked an AA, and they JFDI if it was valid
[18:37] <vorlon> I don't need bug reports for binary removals no
[18:38] <RikMills> vorlon: thanks. I was stating to wonder if my memory was off
[18:39] <RikMills> the calibre one is quite clear. if you need it, I can dig out the salsa comments on telegram-desktop
[18:42] <RikMills> https://salsa.debian.org/debian/telegram-desktop/commit/86d77755e0d40220e3d592b312d28315e134664f#note_116029
[18:51] <vorlon> RikMills: removals done
[18:52] <RikMills> vorlon: thank you! :)
[19:08] -queuebot:#ubuntu-release- Unapproved: carla (eoan-proposed/universe) [2.0.0-0ubuntu3 => 2.0.0-0ubuntu4] (ubuntustudio)
[19:50] <LocutusOfBorg> please kick out opencv from proposed pocket, otherwise this big chunk won't ever migrate...
[19:50] <LocutusOfBorg> otb is now entangled with qt/opencv, not building and unpatchabile in the near future
[21:51] <tkamppeter> The Bionic SRU for network-manager is hanging in -proposed with
[21:51] <tkamppeter> Not touching package due to block request by freeze (contact #ubuntu-release if update is needed)
[21:51] <tkamppeter> What does it mean? I cannot imagine any freeze in Bionic.
[21:52] <tkamppeter> Or can someone unblock it?
[21:52] <apw> tkamppeter, everything in all stable releases are blocked, they are not rleeased by britney
[21:54] <tkamppeter> apw, is network-manager available for the verification of the SR in -prposed now?
[21:59] <infinity> tkamppeter: I'm not sure I understand the question.  The binaries are built, and someone should verify all three linked bugs are fixed.  That's not been done.
[22:07] <tkamppeter> infinity, OK, thanks.
[22:20] <wxl> shouldn't focal be in packages.ubuntu.com?
[22:25] <infinity> Rhonda's response time on updating packages.ubuntu.com isn't always immediate.
[22:26] <wxl> okie dokie
[22:33] <tomreyn> is pinging Rhonda about it part of the post-release-upgrade-things-to-do list, though?
[22:36] <Ukikie> I did on another channel, as I'm sure someone else did somewhere else.
[22:51] <wxl> fcitx now unconditionally breaks fcitx-module-quickphrase-editor (qt4) in lieu of fcitx5-module-quickphrase-editor. in eoan the former was a virtual package for the latter, but not so in focal. anyways, this apparently has been breaking at least lubuntu, kubuntu, and kylin builds for several days. at some point the build process seems to remove fcitx5-module-quickphrase-editor, which is weird.
[22:53] <valorie> wxl: is this part of tsimonq2's acts of violence on qt4?
[22:53] <valorie> unforeseen I'm sure
[22:53] <wxl> valorie: heh, no, i don't think him specifically. this happened up in debian land.
[22:54] <valorie> ah, but he's doing it in debland too!
[22:54] <wxl> well his name ain't on it XD https://salsa.debian.org/input-method-team/fcitx/commit/2de59f4f0cf93c37cded286bfd0c2dcb055aac12
[22:55] <wxl> and indeed not mentioned anywhere on the upstream bug either https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874868
[22:56] <wxl> you know i am the first one to jump at the opportunity to blame simon, but i think i can safely say he had little to do with this
[22:59] <RikMills> wxl: the reason is that the issue is fixed in fcitx-qt5, but that fixed version is stuck in proposed due to the Qt5 transition
[22:59] <RikMills> *I think*
[23:01] <wxl> i think you're right given the change i see in the proposed version:
[23:01] <wxl>     + No longer let fcitx5-module-quickphrase-editor provide
[23:01] <wxl>       fcitx-module-quickphrase-editor since the new fcitx is
[23:01] <wxl>       declaring "Breaks:" relationship on the latter one.
[23:01] <RikMills> yep
[23:02] <wxl> ok so can we at least blame simon for not fixing the transition already? XD
[23:02] <RikMills> seems reasonable :D
[23:02] <valorie> no good deed goes unpunished!
[23:03] <wxl> ok well that mystery is solved