[01:55] -queuebot:#ubuntu-release- New binary: flang [ppc64el] (disco-proposed/universe) [20181226-1] (no packageset)
[02:05] -queuebot:#ubuntu-release- New binary: clickhouse [amd64] (disco-proposed/universe) [18.16.1+ds-1] (no packageset)
[06:24] -queuebot:#ubuntu-release- New: accepted bcbio [amd64] (disco-proposed) [1.1.2-3]
[06:24] -queuebot:#ubuntu-release- New: accepted clickhouse [amd64] (disco-proposed) [18.16.1+ds-1]
[06:24] -queuebot:#ubuntu-release- New: accepted nbsphinx0.3 [amd64] (disco-proposed) [0.4.1+zero.3.5+ds-1]
[06:24] -queuebot:#ubuntu-release- New: accepted python-django-simple-history [amd64] (disco-proposed) [2.7.0-1]
[06:24] -queuebot:#ubuntu-release- New: accepted cava [amd64] (disco-proposed) [0.6.0-1]
[06:24] -queuebot:#ubuntu-release- New: accepted opam [amd64] (disco-proposed) [2.0.1-1]
[06:24] -queuebot:#ubuntu-release- New: accepted dfvfs [amd64] (disco-proposed) [20190122-1]
[06:30] -queuebot:#ubuntu-release- New: accepted flang [ppc64el] (disco-proposed) [20181226-1]
[07:00] <doko> jbicha: missing symbol in zlib???
[08:05] -queuebot:#ubuntu-release- New binary: intel-media-driver-non-free [amd64] (disco-proposed/multiverse) [18.3.0+ds1-2ubuntu1] (no packageset)
[08:10] -queuebot:#ubuntu-release- New binary: intel-media-driver-non-free [i386] (disco-proposed/multiverse) [18.3.0+ds1-2ubuntu1] (no packageset)
[09:02] -queuebot:#ubuntu-release- New sync: gcc-8-cross-mipsen (disco-proposed/primary) [1~c1]
[09:09] -queuebot:#ubuntu-release- New: accepted gcc-8-cross-mipsen [sync] (disco-proposed) [1~c1]
[09:09] -queuebot:#ubuntu-release- New: accepted intel-media-driver-non-free [i386] (disco-proposed) [18.3.0+ds1-2ubuntu1]
[09:10] -queuebot:#ubuntu-release- New: accepted intel-media-driver-non-free [amd64] (disco-proposed) [18.3.0+ds1-2ubuntu1]
[09:11] -queuebot:#ubuntu-release- New binary: node-istanbul [amd64] (disco-proposed/universe) [0.4.5+ds-4ubuntu1] (no packageset)
[09:29] -queuebot:#ubuntu-release- New: accepted node-istanbul [amd64] (disco-proposed) [0.4.5+ds-4ubuntu1]
[10:03]  * sil2100 uploads bionic langpack updates to -proposed
[10:11] -queuebot:#ubuntu-release- New binary: node-opencv [amd64] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:11] -queuebot:#ubuntu-release- New binary: node-opencv [s390x] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:11] -queuebot:#ubuntu-release- New binary: node-opencv [i386] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:12] -queuebot:#ubuntu-release- New binary: node-opencv [ppc64el] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:18] -queuebot:#ubuntu-release- New binary: node-opencv [armhf] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
[10:20] -queuebot:#ubuntu-release- New binary: node-opencv [arm64] (disco-proposed/universe) [6.0.0+git20180416.cfc96ba0-1] (no packageset)
=== cpaelzer__ is now known as cpaelzer
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [amd64] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [armhf] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [ppc64el] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [arm64] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [s390x] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:38] -queuebot:#ubuntu-release- New: accepted node-opencv [i386] (disco-proposed) [6.0.0+git20180416.cfc96ba0-1]
[10:40] -queuebot:#ubuntu-release- Unapproved: fwts (cosmic-proposed/universe) [18.09.00-0ubuntu1 => 18.09.00-0ubuntu2] (no packageset)
[10:46] -queuebot:#ubuntu-release- Unapproved: fwts (bionic-proposed/universe) [18.03.00-0ubuntu3 => 18.03.00-0ubuntu4] (no packageset)
[11:03] -queuebot:#ubuntu-release- Unapproved: fwts (xenial-proposed/universe) [16.03.00-0ubuntu1.2 => 16.03.00-0ubuntu1.3] (no packageset)
[12:17] <doko> apw, sforshee: now nearly everything hangs on linux migrating, or ignoring the failing autopkg tests. binutils is waiting for 40 days now
[12:17] <doko> xnox: besides a few systemd failures. some were fixed however
[12:25] <xnox> doko, yes. but not all. I'm currently pending to figure out udisks2 & systemd on ppc64el
[12:26] <xnox> apw, sforshee: re:kernel. I see that it is ignored on amd64,i386,ppc64el. "passing" on armhf. But it is a regression on arm64 & s390x. Can we please apply/bump the same "ignored failure" onto arm64 and s390x?
[12:26] <xnox> apw, sforshee cause it is affecting migration of userspace packages.
[12:28] <tjaalton> doko: bug 1813155
[12:28] <ubot5> bug 1813155 in resteasy3.0 (Ubuntu) "remove from disco-proposed, Dogtag doesn't support TLS 1.3/Java 11 yet" [Undecided,New] https://launchpad.net/bugs/1813155
[12:48] <sforshee> doko, xnox: it should be fine to ignore the current failures for promoting other packages, I know I've said this at least once before already
[12:48] <sforshee> but I don't have the power to make it happen
[12:48] <xnox> horum.
[12:49] <doko> well apw has ...
[12:52] <tjaalton> doko: did you add freeipa to the bug above? there's no version in proposed
[12:54] <doko> yes
[12:54] <doko> demoting
[12:55] <apw> doko, just been investigating ...
[12:56] <doko> tjaalton: jss cannot be removed, has more rdeps
[12:58] <tjaalton> doko: which ones?
[12:58] <doko> * libidm-console-framework-java  (for libjss-java)
[12:58] <doko> * libldap-java                  (for libjss-java)
[12:58] <doko> * libsymkey-java                (for libjss-java)
[12:58] <doko> * libtomcatjss-java             (for libjss-java)
[12:58] <doko> * pki-base-java                 (for libjss-java)
[12:58] <doko> * pki-console                   (for libjss-java)
[12:58] <doko> * ldapjdk                       (for libjss-java)
[12:59] <tjaalton> where are you removing these from?
[12:59] <tjaalton> the ones in disco should be fine, ones in proposed should be removed
[12:59] <sforshee> apw: let me know if you have questions. I've just retried the failing ones as we have fixes for some of the selftest failures in autotests, and tyhicks has confirmed that the apparmor failures are because the tests need updating after the /usr merge
[13:00] <doko> disco
[13:00] <doko> no, that doesn't help. if it's broken, it needs to be removed in the release pocket, not the proposed pocket
[13:01] <tjaalton> bah
[13:01] <tjaalton> start from freeipa, then dogtag-pki, tomcatjss...
[13:01] <tjaalton> ldapjdk
[13:04] -queuebot:#ubuntu-release- New binary: gcc-8-cross-mipsen [i386] (disco-proposed/universe) [1~c1] (no packageset)
[13:16] <tjaalton> doko: now with freeipa/dogtag gone, jss and the others should not cause issues
[13:27] <doko> yes, exactly
[13:28] <doko> now these test failures block readline: gsequencer coyote idlastro mothur ngraph-gtk redmine
[13:28] <doko> ahh, and gap-io
[13:41] <LocutusOfBorg> oSoMoN, https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+build/16316513
[13:41] <LocutusOfBorg> looks like using llvm-6 instead of llvm-7 works...
[13:42] <LocutusOfBorg> maybe we can switch to that one for now?
[13:42] <LocutusOfBorg> btw firefox failed for some reason I don't get, it doens't fail locally :/ github network error
[13:44] <doko> LocutusOfBorg: better check forward with 8
[13:55] <LocutusOfBorg> doko, llvm-6 is not going to disappear for cosmic, so I care about making llvm-4 disappear right now
[14:00] <doko> and mir is getting in the way again ...
[14:02] -queuebot:#ubuntu-release- New binary: linux-signed-azure-edge [amd64] (xenial-proposed/universe) [4.18.0-1008.8~16.04.2] (no packageset)
[14:12] <LocutusOfBorg> doko, llvm-7 and llvm-8 are both making firefox sad
[14:12] <LocutusOfBorg> before mir-ing you should try some no change rebuilds :)
[14:15] -queuebot:#ubuntu-release- New: accepted linux-signed-azure-edge [amd64] (xenial-proposed) [4.18.0-1008.8~16.04.2]
[14:20] <doko> no, the package mir ...
[14:22] <LocutusOfBorg> ok, but shouldn't this mean that something should go out from main?
[14:23] <LocutusOfBorg> oh we have only llvm-7 in main right now, nice
[14:23] <LocutusOfBorg> btw I'm syncing llvm-8 from experimental when its picked up
[14:24] <doko> you are too late
[14:30] -queuebot:#ubuntu-release- Unapproved: vulkan (bionic-proposed/universe) [1.1.70+dfsg1-1 => 1.1.73+dfsg-0ubuntu0.18.04.1] (kubuntu)
[14:31] -queuebot:#ubuntu-release- Unapproved: rejected vulkan [source] (bionic-proposed) [1.1.73+dfsg-0ubuntu0.18.04.1]
[14:34] -queuebot:#ubuntu-release- Unapproved: vulkan (bionic-proposed/universe) [1.1.70+dfsg1-1 => 1.1.73+dfsg-0ubuntu0.18.04.1] (kubuntu)
[14:42] <LocutusOfBorg> doko, I don't think so :)
[14:42] <doko> https://launchpad.net/ubuntu/+source/llvm-toolchain-8/1:8~svn351401-1~exp1
[14:42] <LocutusOfBorg> oSoMoN, thunderbird with llvm-6 -> good, llvm-7 -> bad, llvm-8 -> bad
[14:43] <doko> ahh, you mean the next one
[14:43] <LocutusOfBorg> :)
[14:43] <LocutusOfBorg> rc1!
[14:53] <oSoMoN> LocutusOfBorg, ack, so we should go with llvm-6
[14:53] <oSoMoN> I'm seeing the same github connection error when doing unrelated builds of firefox, btw
[14:54] <oSoMoN> LocutusOfBorg, would you mind commenting on the bug report with your findings about llvm versions?
[15:00] <doko> ginggs: fyi, trilinos ftbfs
[15:00] <ginggs> doko: thanks
[15:02] <ginggs> doko: ah no, that's fine - only 32-bit ftbfs
[15:13] <LocutusOfBorg> sure oSoMoN !
[15:13] <oSoMoN> thanks
[15:15] <LocutusOfBorg> done
[15:15] <LocutusOfBorg> btw, lots of the third_party applications are already in the archive, so maybe miring them would be nice instead of using bundled old versions?
[15:26] <oSoMoN> looks like the firefox github network error might be caused by the new version of cargo
[16:04] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (cosmic-proposed) [2.02+dfsg1-5ubuntu8.1]
[16:04] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (cosmic-proposed) [2.02+dfsg1-5ubuntu8.1]
[16:22] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.14.10 => 18.04.14.11] (core)
[16:33] -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [source] (bionic-proposed) [0.130ubuntu3.7]
[16:52] -queuebot:#ubuntu-release- Unapproved: accepted apport [source] (cosmic-proposed) [2.20.10-0ubuntu13.2]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (bionic-proposed) [2.02-2ubuntu8.10]
[16:59] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (bionic-proposed) [2.02-2ubuntu8.10]
[17:11] <Ark74> Hi guys!
[17:12] <Ark74> Do you know if apache2 (2.4.34) shipped on disco already has http2 support?
[17:13] <teward> Ark74: probably an #ubuntu-server question but I can find out
[17:14] <Ark74> Oh, cool!
[17:14] <teward> Ark74: I believe it does, because there's HTTP/2 patches being applied.  let me double check the package itself
[17:14] <Ark74> teward, should I go there?
[17:14] <teward> nah you can wait here
[17:15] <Ark74> very appreciated!
[17:15] <Ark74> tnaks
[17:15] <Ark74> *thanks
[17:16] <teward> Ark74: I believe it's available, but not enabled by default, in Disco.  But it's been that way for a while, possibly even Bionic (untested, unconfirmed)
[17:17] <Ark74> I have build (backport) from disco to xenial, and it seems it doesn't
[17:17] <Ark74> seems only by using PPAs is possible to get it
[17:17] <Ark74> I'll hang on #ubuntu-server and ask further
[17:17] <Ark74> there
[17:17] <Ark74> thanks
[18:19] <vorlon> anyone want to dig into the breakage in protobuf that causes mir to FTBFS?
[18:20] <vorlon> I got as far as fixing the first build failure locally and that turned up further bugs, which look to all be on the protobuf side
[18:25] <ahasenack>  /bin/sh: 1: /usr/lib/bin/capnp: not found <-- which failure is that, the one you fixed, or one of the new ones?
[18:26] <vorlon> ahasenack: that's the one I hacked around locally (by editing the cmake templates to use the correct path to /usr/bin/capnp)
[18:27] <vorlon> ahasenack: after fixing that, I get another error with invalid arguments to the command; all of which originates from those same cmake templates in the protobuf package
[18:57] <LocutusOfBorg> vorlon, interesting but the -4 version, that was in proposed before your upload, has been built with the protobuf that is currently in release...
[18:57] <LocutusOfBorg> Preparing to unpack .../266-libprotobuf-lite17_3.6.1.3-1_amd64.deb ...
[18:59] <vorlon> LocutusOfBorg: sorry, I meant capnproto, not protobuf
[18:59] <vorlon> ahasenack: ^^
[19:00] <LocutusOfBorg> ok this makes sense now :)
[19:11] -queuebot:#ubuntu-release- Unapproved: rejected vulkan [source] (bionic-proposed) [1.1.73+dfsg-0ubuntu0.18.04.1]
[23:10] <bdmurray> Why is the apt in -proposed greater than the one in updates and security but older?
[23:12] <tsimonq2> ahasenack, vorlon: capnproto> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920230
[23:12] <ubot5> Debian bug 920230 in capnproto "capnproto: executable installed in directory which breaks rdeps" [Normal,Open]
[23:12] <tsimonq2> I ran into it when packaging Mir for Debian.
[23:12] <tsimonq2> The upstream GitHub issue shows a potential solution but I'm just about as stumped.
[23:13] <vorlon> tsimonq2: well, I don't think the binary's location is wrong (that's where it was previously), but that the cmake templates it itself provides look for it in the wrong place.  And when I hack the templates for this, other things fail
[23:13] <tsimonq2> When I had some spare time (which I do tonight) I was going to look at a recently removed CMake-related patch in the packaging.
[23:13] <vorlon> ok
[23:13] <tsimonq2> vorlon: Please do reply to the bug if you believe it's wrong. :)
[23:14] <tsimonq2> vorlon: https://github.com/thomaslee/capnproto-debian/blob/e29449fdef45ec460e02dbe0d870914faf8efa50/debian/patches/01_cmake-debian.patch - how fitting does this look?
[23:14] <tsimonq2> (That's the patch I was looking at.)
[23:15] <vorlon> ENOCLUE
[23:15] <tsimonq2> Alright. I'll poke at it.
[23:17] -queuebot:#ubuntu-release- New binary: jupyter-sphinx-theme [amd64] (disco-proposed/universe) [0.0.6+ds1-5] (no packageset)