[01:41] -queuebot:#ubuntu-release- New: accepted ejabberd-contrib [amd64] (eoan-proposed) [0.2019.08.19~dfsg0-3]
[01:41] -queuebot:#ubuntu-release- New: accepted ejabberd-contrib [armhf] (eoan-proposed) [0.2019.08.19~dfsg0-3]
[01:41] -queuebot:#ubuntu-release- New: accepted ejabberd-contrib [ppc64el] (eoan-proposed) [0.2019.08.19~dfsg0-3]
[01:41] -queuebot:#ubuntu-release- New: accepted ejabberd-contrib [arm64] (eoan-proposed) [0.2019.08.19~dfsg0-3]
[01:41] -queuebot:#ubuntu-release- New: accepted ejabberd-contrib [s390x] (eoan-proposed) [0.2019.08.19~dfsg0-3]
[01:41] -queuebot:#ubuntu-release- New: accepted ejabberd-contrib [i386] (eoan-proposed) [0.2019.08.19~dfsg0-3]
[01:43] <vorlon> mwhudson: was the output going to also mention RC bugs filed in Debian that are keeping the package out of testing?
[01:43] <mwhudson> vorlon: yes
[01:43] <mwhudson> vorlon: in fact i have new output now
[01:43] <vorlon> k :)
[01:44] <mwhudson> vorlon: https://paste.ubuntu.com/p/XJQvjqSKJd/
[01:47] <mwhudson> vorlon: does the environment that this script will run in have access to a directory containing the Packages files for the devel series?
[01:47] <mwhudson> it must, right?
[01:48] <vorlon> mwhudson: knot-resolver has versions in both release and -proposed so would need two separate removal lines (-s eoan-proposed), maybe we should care about that nuance.  Also, knot-resolver has hddemux as a reverse build-dep ugh
[01:48] <mwhudson> vorlon: i guess i should invoke reverse-depends huh?
[01:48] <vorlon> mwhudson: yes, in ~/mirror/ubuntu/dists
[01:49] <vorlon> mwhudson: at least if it's going to recommend removal commands for cut'n'paste, yes
[01:49] <mwhudson> vorlon: those are compressed in there though?
[01:49] <mwhudson> or do they get uncompressed somewhere
[01:50] <mwhudson> vorlon: the reason for asking about Packages is that i need to map binary package to source package name
[01:50] <mwhudson> vorlon: is there an easier way to do that than grep-dctrl -SwnsPackage
[01:51] <mwhudson> er other way around
[01:51] <mwhudson> source to binaries
[01:51] <vorlon> mwhudson: compressed and uh if you're in python I guess you want to use the python apt module instead of grep-dctrl
[01:53] <mwhudson> vorlon: do i really
[01:53] <vorlon> hypothetically
[01:53] <mwhudson> i guess if they can read compressed indices i actually do...
[02:05] <mwhudson> vorlon: https://paste.ubuntu.com/p/vKZHbbCCgr/
[02:26] <mwhudson> vorlon: or even https://paste.ubuntu.com/p/6NC4VPMJTw/
[03:28]  * RAOF grumbles about gvfs autopkgtest being flaky.
[05:50] <FourDollars> RAOF: xkb-data 2.23.1-1ubuntu1.18.04.1 is not released https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1740894.
[05:50] <ubot5> Launchpad bug 1740894 in OEM Priority Project bionic "KEY_RFKILL is not passed to userspace" [Critical,Fix committed]
[05:54] <RAOF> Is that a problem? It was not clear to me on the bug (or in your email) that the systemd release needed too wait for xkb-data.
[06:02] <FourDollars> RAOF: I thought  xkb-data 2.23.1-1ubuntu1.18.04.1 will be released to bionic-updates with systemd for https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1740894.
[06:02] <ubot5> Launchpad bug 1740894 in OEM Priority Project bionic "KEY_RFKILL is not passed to userspace" [Critical,Fix committed]
[06:03] <FourDollars> RAOF: Because xkb-data 2.23.1-1ubuntu1.18.04.1 caused some regression so I included the patch for systemd.
[06:04] <FourDollars> RAOF: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1740894/comments/49 comments about it.
[06:04] <ubot5> Launchpad bug 1740894 in OEM Priority Project bionic "KEY_RFKILL is not passed to userspace" [Critical,Fix committed]
[06:05] <FourDollars> RAOF: If you only released the systemd, it will make most of Dell latops' Wifi hotkey broken.
[06:06] <RAOF> Urgh.
[06:07] <RAOF> It would have been nice to have that documented in the bug somewhere!
[06:07] <FourDollars> OK.
[06:08] <RAOF> Because I have released the systemd SRU (which you said was urgent?)
[06:10] <FourDollars> RAOF: Yes, it is urgent.
[06:11] <FourDollars> RAOF: Is it possible to release xkb-data 2.23.1-1ubuntu1.18.04.1 right now?
[06:11] <RAOF> FourDollars: The xkeyboard-config SRU appears to be a valid release candidate, but we haven't released it because you asked us not to (in https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1740894/comments/48)
[06:11] <ubot5> Launchpad bug 1740894 in OEM Priority Project bionic "KEY_RFKILL is not passed to userspace" [Critical,Fix committed]
[06:11] <RAOF> If that's no longer the case, then I can release xkeyboard-config, yes.
[06:12] <FourDollars> RAOF: So I commented https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1740894/comments/49 and made the patch for system.
[06:12] <ubot5> Launchpad bug 1740894 in OEM Priority Project bionic "KEY_RFKILL is not passed to userspace" [Critical,Fix committed]
[06:12] <FourDollars> s/system/systemd/
[06:14] <RAOF> So, I shall release xkeyboard-config  	2.23.1-1ubuntu1.18.04.1 into bionic-updates?
[06:15] <FourDollars> RAOF: Yes, please.
[06:25] <FourDollars> RAOF++ Thx a lot.
[06:44] -queuebot:#ubuntu-release- New sync: libgeotiff (eoan-proposed/primary) [1.5.1-1]
=== cpaelzer_ is now known as cpaelzer
[07:24] -queuebot:#ubuntu-release- New binary: mpi4py [amd64] (eoan-proposed/universe) [3.0.2-13] (kubuntu)
[07:26] -queuebot:#ubuntu-release- New binary: mpi4py [i386] (eoan-proposed/universe) [3.0.2-13] (kubuntu)
[07:39] -queuebot:#ubuntu-release- New binary: mpi4py [ppc64el] (eoan-proposed/universe) [3.0.2-13] (kubuntu)
[07:40] -queuebot:#ubuntu-release- New binary: mpi4py [arm64] (eoan-proposed/universe) [3.0.2-13] (kubuntu)
[07:43] -queuebot:#ubuntu-release- New binary: mpi4py [armhf] (eoan-proposed/universe) [3.0.2-13] (kubuntu)
[08:04] <Laney> vorlon: kernel bug> I assume you've appropriately reported it and cleaned up?
[08:07] -queuebot:#ubuntu-release- New binary: mpi4py [s390x] (eoan-proposed/universe) [3.0.2-13] (kubuntu)
[08:50] -queuebot:#ubuntu-release- New binary: golang-1.13 [amd64] (eoan-proposed/universe) [1.13~rc2-1ubuntu1] (no packageset)
[08:52] -queuebot:#ubuntu-release- New binary: golang-1.13 [s390x] (eoan-proposed/universe) [1.13~rc2-1ubuntu1] (no packageset)
[08:54] -queuebot:#ubuntu-release- New binary: golang-1.13 [ppc64el] (eoan-proposed/universe) [1.13~rc2-1ubuntu1] (no packageset)
[08:55] -queuebot:#ubuntu-release- New binary: golang-1.13 [i386] (eoan-proposed/universe) [1.13~rc2-1ubuntu1] (no packageset)
[09:02] -queuebot:#ubuntu-release- New binary: golang-1.13 [armhf] (eoan-proposed/universe) [1.13~rc2-1ubuntu1] (no packageset)
[09:05] -queuebot:#ubuntu-release- New binary: linux-signed-oracle [amd64] (disco-proposed/main) [5.0.0-1002.3] (core)
[09:08] -queuebot:#ubuntu-release- New source: python-infoblox-client (eoan-proposed/primary) [0.4.22-0ubuntu1]
[09:09] -queuebot:#ubuntu-release- New binary: golang-1.13 [arm64] (eoan-proposed/universe) [1.13~rc2-1ubuntu1] (no packageset)
[09:09] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (disco-proposed) [5.0.0-1002.3]
[09:37] <sil2100> RikMills: hey! Do you know what's up with the kdeconnect autopkgtests for bionic?
[09:37] <sil2100> RikMills: I see those are all red since recently, and  this is blocking qtbase-opensource-src from getting released
[09:50] <RikMills> sil2100: discussed with juliank here https://irclogs.ubuntu.com/2019/08/06/%23ubuntu-devel.html#t10:36
[09:53] <RikMills> long story short, an already flaky/racy test went completely bad with openssl 1.1.1. disable or skip I think
[09:56] <sil2100> RikMills: could you please fill in a bug for this so that we don't forget what it's all about? I'll then hint it (with a bug reference for 'future reference') and release qtbase-opensource-src
[09:57] <RikMills> sil2100: ok, will do so in a bit
[10:03] <sil2100> RikMills: thank you!
[10:21] <RikMills> sil2100: LP: #1842302
[10:21] <ubot5> Launchpad bug 1842302 in kdeconnect (Ubuntu) "autopkgtests: testsslsocketlinereader fails in bionic since openssl 1.1.1" [Undecided,New] https://launchpad.net/bugs/1842302
[11:02] <tarzeau> could i ask for ubuntu 19.10 gets rtl-433 from sid, since the official release version only differs very little from the git check out version. and comes with a proper manual page as well?
[11:06] <ginggs> tarzeau: 'requestsync rtl-433'
[11:07] <tarzeau> requestsync rtl-433
[11:07] <ginggs> tarzeau: in a terminal :)
[11:08] <ginggs> https://wiki.ubuntu.com/SyncRequestProcess
[11:08] <tarzeau> ginggs: gpg error was invalid ipc response
[11:14] <ginggs> tarzeau: you can also file the sync request bug in launchpad manually, but requestsync is easier
[11:15] <tarzeau> i try to get rid of kwalletd(kde-runtime)/kinit5(kinit) and retry
[11:15] <tarzeau> damn it keeps wanting to use that wallet crap i don't want
[11:15] <tarzeau> i'm giving it with -k the key to use, why does it try stuff i don't want it to? broken
[11:15] <tarzeau> where in launchpad?
[11:17] <ginggs> against the rtl-433 source package https://launchpad.net/ubuntu/+source/rtl-433
[11:17] <tarzeau> mighty complicated, i'll skip that i guess
[12:28] -queuebot:#ubuntu-release- New binary: probert [amd64] (eoan-proposed/main) [0.0.17] (no packageset)
[12:29] -queuebot:#ubuntu-release- New binary: probert [ppc64el] (eoan-proposed/main) [0.0.17] (no packageset)
[12:29] -queuebot:#ubuntu-release- New binary: probert [i386] (eoan-proposed/main) [0.0.17] (no packageset)
[12:29] -queuebot:#ubuntu-release- New binary: probert [s390x] (eoan-proposed/main) [0.0.17] (no packageset)
[12:29] -queuebot:#ubuntu-release- New binary: probert [armhf] (eoan-proposed/main) [0.0.17] (no packageset)
[12:30] -queuebot:#ubuntu-release- New binary: probert [arm64] (eoan-proposed/main) [0.0.17] (no packageset)
=== lotus|i5 is now known as lotuspsychje
[14:04] -queuebot:#ubuntu-release- New: accepted mpi4py [amd64] (eoan-proposed) [3.0.2-13]
[14:04] -queuebot:#ubuntu-release- New: accepted mpi4py [armhf] (eoan-proposed) [3.0.2-13]
[14:04] -queuebot:#ubuntu-release- New: accepted mpi4py [ppc64el] (eoan-proposed) [3.0.2-13]
[14:04] -queuebot:#ubuntu-release- New: accepted mpi4py [arm64] (eoan-proposed) [3.0.2-13]
[14:04] -queuebot:#ubuntu-release- New: accepted mpi4py [s390x] (eoan-proposed) [3.0.2-13]
[14:04] -queuebot:#ubuntu-release- New: accepted mpi4py [i386] (eoan-proposed) [3.0.2-13]
[14:08] -queuebot:#ubuntu-release- New: accepted probert [amd64] (eoan-proposed) [0.0.17]
[14:08] -queuebot:#ubuntu-release- New: accepted probert [armhf] (eoan-proposed) [0.0.17]
[14:08] -queuebot:#ubuntu-release- New: accepted probert [ppc64el] (eoan-proposed) [0.0.17]
[14:08] -queuebot:#ubuntu-release- New: accepted probert [arm64] (eoan-proposed) [0.0.17]
[14:08] -queuebot:#ubuntu-release- New: accepted probert [s390x] (eoan-proposed) [0.0.17]
[14:08] -queuebot:#ubuntu-release- New: accepted probert [i386] (eoan-proposed) [0.0.17]
[14:36] -queuebot:#ubuntu-release- Unapproved: dkms (bionic-proposed/main) [2.3-3ubuntu9.5 => 2.3-3ubuntu9.6] (kubuntu, ubuntu-desktop)
[14:37] -queuebot:#ubuntu-release- Unapproved: dkms (disco-proposed/main) [2.6.1-4ubuntu2.2 => 2.6.1-4ubuntu2.3] (ubuntu-desktop)
[15:08] -queuebot:#ubuntu-release- Unapproved: rejected apt [source] (disco-updates) [1.8.3]
[15:16] -queuebot:#ubuntu-release- Unapproved: accepted cloud-utils [source] (disco-proposed) [0.31-0ubuntu1.1]
[15:18] -queuebot:#ubuntu-release- Unapproved: apt (disco-proposed/main) [1.8.1 => 1.8.3] (core)
[15:30] <sil2100> coreycb: hey! The cinder that's currently in disco-proposed is blocking another cinder upload that's in the queue
[15:30] <sil2100> Could you verify the -proposed one so we can release it?
[15:30] <sil2100> coreycb: it's been in -proposed for 33 days already
[15:35] -queuebot:#ubuntu-release- Unapproved: accepted smc-tools [source] (disco-proposed) [1.2.0-0ubuntu1.1]
[15:36] -queuebot:#ubuntu-release- Unapproved: rejected gnome-initial-setup [source] (bionic-proposed) [3.28.0-2ubuntu6.16.04.5]
[15:36] <ahasenack> hi guys, on august 23rd, someone promoted all php7.3 packages from universe to main (https://launchpad.net/ubuntu/+source/php7.3/+publishinghistory), but not all of the 7.2 binary ones were in main before
[15:37] <ahasenack> this has caused php7.3 to get stuck in eoan proposed: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#php7.3
[15:37] <ahasenack> due to some dependencies being in universe only
[15:37] <ahasenack> for example, php7.2-imap was in eoan universe
[15:38] <ahasenack> but php7.3-imap 7.3.6 is in eoan/universe, whereas php7.3-imap 7.3.8 is in eoan-proposed/main
[15:43] <rbasak> ^ to resolve, I think an AA needs to demote a bunch of src:php7.3 binaries back to universe. The ones that match the src:php7.2 binaries, at least.
[15:43] -queuebot:#ubuntu-release- Unapproved: accepted gnome-initial-setup [source] (bionic-proposed) [3.28.0-2ubuntu6.16.04.6]
[15:43] <rbasak> (also I suspect the standing PHP MIR doesn't permit those packages in main anyway)
[15:58] -queuebot:#ubuntu-release- Unapproved: accepted apt [source] (disco-proposed) [1.8.3]
[16:12] <apw> rbasak, hmmm, nasty
[16:13] <vorlon> Laney: I cleaned up but haven't reported the bug yet, haven't had time to isolate the trigger
[16:17] <Laney> nod
[16:25] <apw> vorlon, the kernel version reported was a few back-rev, no idea of that is releveant
[16:29] <vorlon> that too
[16:29] <vorlon> since they've all now been rebooted, was going to wait and see if it happened again
[16:44] <apw> rbasak, ok overrides in progress
[16:58] <rbasak> Thanks!
[16:58] <ahasenack> apw: thanks
[17:39] <ahasenack> apw: php7.3 seems sorted, but I'm now seeing dep8 test results from august 8th showing up all of a sudden. It looks like the tests were run before the deps were sorted, is that expected?
[17:40] <ahasenack> that means they ran (and are green) with mysql 5.7, not mysql 8 which is what is in the archive now
[17:40] <ahasenack> in fact, the only red so far, armhf, is because that one picked up mysql 8
[17:40] <ahasenack> (in mediawiki)
[20:25] -queuebot:#ubuntu-release- New binary: llvm-toolchain-9 [armhf] (eoan-proposed/main) [1:9~+rc3-1~exp1] (no packageset)