[00:21] -queuebot:#ubuntu-release- New binary: openjdk-13 [amd64] (disco-proposed/universe) [13~12-1] (no packageset)
[05:09] <vorlon> Laney, juliank: heads up that triggering autopkgtests through the web api doesn't seem to be working; I haven't dug into it, I'm only noticing while trying to give back some perl-triggered tests
[05:12] <vorlon> seems to be hanging talking to rabbit; trying to restart rabbit
[05:12] <vorlon> ok that looks better
[06:29] <ginggs> vorlon: the single python-scipy/1.2.1-0ubuntu1 test failure I see locally is definitely caused by matplotlib >= 3.0.0 - I want to upload 1.2.1-0ubuntu2 to switch back to gcc 8 on s390x, should I skip this test in the same upload?
[08:55] <LocutusOfBorg> oSoMoN, hello, did you receive my messages?
[08:55] <oSoMoN> LocutusOfBorg, good morning, I don't think so, when were they sent?
[09:09] <LocutusOfBorg> [15:06:28] <LocutusOfBorg> anybody with an s390x or a bigger knowledge can help understanding why thunderbird is sad on s390x? (I see update output complaining wrt testsuite), new binary there
[09:09] <LocutusOfBorg> [15:07:20] <LocutusOfBorg> trying: thunderbird
[09:09] <LocutusOfBorg> [15:07:20] <LocutusOfBorg> skipped: thunderbird (6, 3, 2)
[09:09] <LocutusOfBorg> [15:07:20] <LocutusOfBorg>     got: 35+0: a-7:a-5:a-5:i-5:p-4:s-9
[09:09] <LocutusOfBorg> [15:07:20] <LocutusOfBorg>     * s390x: thunderbird-testsuite
[09:09] <LocutusOfBorg> [15:38:17] <jbicha> LocutusOfBorg: thunderbird-testsuite depends on gnome-session which depends on gnome-shell which isn't available on s390x
[09:09] <LocutusOfBorg> [15:39:03] <jbicha> maybe we shouldn't build thunderbird-testsuite on s390x…
[09:09] <LocutusOfBorg> oSoMoN, I send them with /msg command, not sure if you can read them now...
[09:10] <LocutusOfBorg> anyway ^^
[09:10] <LocutusOfBorg> we shouldn't build thunderbird-testsuite on s390x because it can't be installed?
[09:11] <oSoMoN> LocutusOfBorg, thunderbird used to fail to build on s390x, but Rico recently worked out some patches that make the build succeed there
[09:11] <oSoMoN> that would explain why this started to fail
[09:15] <oSoMoN> that package appears to be mostly empty on s390x
[09:16] <oSoMoN> oh, not just there, actually
[09:16] <oSoMoN> I wonder if that package could simply be removed?
[09:16] <oSoMoN> let me check
[09:18] <oSoMoN> I see the following commit on 2015-08-17:
[09:18] <oSoMoN> * Disable all of the testsuite related patches and don't install anything
[09:18] <oSoMoN>   in to the testsuite package for now. The patches have all bit-rotted,
[09:18] <oSoMoN>   we're not running any tests and nobody is driving that anymore
[09:19] <oSoMoN> it looks like the package can safely be removed
[09:19] <oSoMoN> chrisccoulson, what do you think? ^
[09:44] -queuebot:#ubuntu-release- New: accepted openjdk-13 [amd64] (disco-proposed) [13~12-1]
[09:44] <LocutusOfBorg> oSoMoN, debian removed the testsuite package too
[09:45] <LocutusOfBorg> (not sure if they ever had it)
[09:45] <LocutusOfBorg> and no reverse-deps, so it should be safe to go
[09:55] <LocutusOfBorg> please bump debci hint...
[10:03] <rbalint> seb128, juliank seb128: software-properties was a bit tricky because it could not be imported by git-remote-bzr to cross-check, but I committed the conversion script here: https://code.launchpad.net/~ubuntu-core-dev/+git/bzr-git-mass-convert/+ref/master
[10:04] <rbalint> how about swithing it to git on wednesday?
[10:04] <rbalint> master branch only, since older branches are out of date
[10:11] <seb128> wfm
[10:18] <jbicha> vorlon: some packages went missing when they were promoted from disco-proposed: I noticed epiphany-browser, ruby-pkg-config, simple-scan
[13:24] -queuebot:#ubuntu-release- Unapproved: accepted indicator-application [sync] (cosmic-proposed) [12.10.1+18.10.20190308.1-0ubuntu1]
[13:26] -queuebot:#ubuntu-release- Unapproved: accepted indicator-application [sync] (bionic-proposed) [12.10.1+18.04.20190308.1-0ubuntu1]
[13:36] -queuebot:#ubuntu-release- Unapproved: rejected ggcov [source] (cosmic-proposed) [0.9+20190314-0ubuntu0.3]
[13:47] -queuebot:#ubuntu-release- Unapproved: ggcov (bionic-proposed/universe) [0.9-20 => 0.9+20190314-0ubuntu0.1] (no packageset)
[13:47] -queuebot:#ubuntu-release- Unapproved: ggcov (cosmic-proposed/universe) [0.9-21 => 0.9+20190314-0ubuntu0.3] (no packageset)
[14:32] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (bionic-proposed/main) [4.18.0-17.18~18.04.1] (kernel)
[14:35] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (bionic-proposed/main) [4.18.0-17.18~18.04.1] (kernel)
[14:43] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (bionic-proposed) [4.18.0-17.18~18.04.1]
[14:43] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (bionic-proposed) [4.18.0-17.18~18.04.1]
[15:51] <seb128> sil2100, bug #1637988, I saw that you accepted gvfs without libnfs which means the gvfs-backends binary from main in the SRU depends on an universe library
[15:58] <infinity> seb128: What's the point of the no-change upload in the queue?
[15:58] <infinity> seb128: If the MIR is approved, we can just binary copy the one from release to updates and override it to main.
[15:58] <seb128> infinity, when I asked here last week someone replied that libnfs couldn't be moved from universe to main in the release pocket and such we needed an uplaod
[15:58] <seb128> ah
[15:59] <infinity> The first is true, the second is not.
[15:59] <seb128> then feel free to do that
[15:59] <seb128> k, makes sense
[15:59] <infinity> THe bug log implied the MIR was still in progress?
[15:59] <infinity> So, no, I don't feel free to do that.
[15:59] <seb128> which part?
[15:59] <seb128> https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598 was promoted in disco
[16:00] <infinity> YEs, and cosmic and disco have entirely different versions.  Committing to support from 3.0 onward doesn't retroactively apply to old ones.
[16:00] <infinity> As for "which part", comment #14 of the bug you poked sil2100 with. :P
[16:02] <seb128> ah, somewhat I did receive the email/see that comment
[16:03] <sil2100> seb128: yeah, as per my comment on the bug, I accepted cosmic prematurely, it wasn't supposed to be accepted
[16:03] <sil2100> seb128: since I was waiting for the MIR situation to be resolved
[16:03] <seb128> well, as long as nobody move it to updates by error
[16:03] <seb128> k
[16:03] <seb128> did you ping security about it?
[16:03] <infinity> Yeah, I'll reject the unnecessary rebuild from the queue.
[16:04] <sil2100> I poked the MIR team and I think slashd today reminded the security team about it
[16:04] <seb128> thx
[16:04] <seb128> k, good
[16:04] <infinity> And please, someone make sure that either 2.0 is MIRed for b/c, or if that fails, a solid argument for backporting 3.0 is made.
[16:04] <infinity> (The former preferred)
[16:04] -queuebot:#ubuntu-release- Unapproved: grub2 (cosmic-proposed/main) [2.02+dfsg1-5ubuntu8.2 => 2.02+dfsg1-5ubuntu8.3] (core)
[16:05] -queuebot:#ubuntu-release- Unapproved: rejected libnfs [source] (cosmic-proposed) [2.0.0-1~exp1ubuntu1]
[16:06] <infinity> Oh, 3.0 adds NFSv4 support. :/
[16:07] <infinity> If the argument for using libnfs in gvfs is wider interop, missing v4 kinda sucks.
[16:07] <infinity> But I guess it's better than no NFS at all.
[16:07] <infinity> And people who still run Solaris are probably used to living in the past.
[16:29] <vorlon> jbicha: missing packages> do you want to feed me version numbers or point to the log where they went missing?
[16:41] <seb128> vorlon, https://launchpad.net/ubuntu/+source/epiphany-browser/+publishinghistory for example?
[16:42] <seb128>  	3.32.0-1ubuntu1 was
[16:42] <seb128> Deleted on 2019-03-15 by Ubuntu Archive Robot
[16:42] <seb128> moved to release
[16:42] <seb128> but never made it there
[17:23] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.15.0-47.50~16.04.1] (kernel)
[17:23] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (xenial-proposed/main) [4.15.0-47.50~16.04.1] (kernel)
[17:34] <vorlon> seb128, jbicha: copied for the 3 packages mentioned
[17:44] <Eickmeyer> vorlon: Had a chance to look at carla yet?
[17:56] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.12 => 2.02-2ubuntu8.13] (core)
[18:19] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-47.50~16.04.1]
[18:19] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-47.50~16.04.1]
[18:19] -queuebot:#ubuntu-release- Unapproved: grub2-signed (cosmic-proposed/main) [1.110.2 => 1.110.3] (core)
[18:33] -queuebot:#ubuntu-release- Unapproved: grub2-signed (bionic-proposed/main) [1.93.13 => 1.93.14] (core)
[18:50] <slashd> sil2100, infinity : security team suggest to upgrade libnfs from 2.0.0 to 3.0.0 in B/C due to sec issues and nasty bugs. Wearing your SRU hat, would you be okay with the proposition before any work start in that regard ? https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598
[18:50] <slashd> 2.0.0 as-is will most likely be NACK by security team at first glance.
[18:51] <slashd> seb128, ^ fyi
[19:10] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (cosmic-proposed/main) [4.18.0-1014.14] (kernel)
[19:10] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (cosmic-proposed/main) [4.18.0-1008.9] (kernel)
[19:21] <seb128> slashd, thx
[19:57] -queuebot:#ubuntu-release- New binary: ubuntu-mate-artwork [amd64] (disco-proposed/universe) [19.04.0] (ubuntu-mate)
[20:15] -queuebot:#ubuntu-release- Unapproved: golang-1.6 (trusty-security/main) [1.6-0ubuntu1~14.04 => 1.6-0ubuntu1~14.04] (no packageset) (sync)
[20:15] -queuebot:#ubuntu-release- Unapproved: golang-1.6 (trusty-updates/main) [1.6-0ubuntu1~14.04 => 1.6-0ubuntu1~14.04] (no packageset) (sync)
[20:16] -queuebot:#ubuntu-release- Unapproved: accepted golang-1.6 [sync] (trusty-security) [1.6-0ubuntu1~14.04]
[20:17] -queuebot:#ubuntu-release- Unapproved: accepted golang-1.6 [sync] (trusty-updates) [1.6-0ubuntu1~14.04]
[20:24] -queuebot:#ubuntu-release- New sync: pdfchain (disco-proposed/primary) [1:0.4.4.2-1]
[20:25] <seb128> Could someone review ffe bug #1820259? It should basically be a no-op for disco since livepatch isn't used in that serie, but it's a pre-requirement for the bionic SRU
[20:27] <coreycb> hello, can an archive admin take a look at masakari-monitors in the disco NEW queue?
[21:05] -queuebot:#ubuntu-release- New: rejected pdfchain [sync] (disco-proposed) [1:0.4.4.2-1]
[21:05] -queuebot:#ubuntu-release- New: accepted ubuntu-mate-artwork [amd64] (disco-proposed) [19.04.0]