[00:00] -queuebot:#ubuntu-release- New: accepted jawn [amd64] (disco-proposed) [0.11.1-1]
[00:00] -queuebot:#ubuntu-release- New: accepted sbt-test-interface [amd64] (disco-proposed) [1.0+repack-1]
[00:25] <vorlon> doko: icu and protobuf transitions entangled too
[00:26] <doko> yes, seen that
[00:27] <doko> and icu doesn't look well despite the analysis of the debian maintainer
[00:28] <teward> doko: any chance the python 3.6 -> 3.7 transition has exploded calamares?  wxl indicated that something within calamares was still looking for the python 3.6 .so files.
[00:28] <teward> (I was doing some digging in other things, it showed up on my list of things to inquire about, you TIL)
[00:29] <wxl> see -devel logs
[00:29] <teward> and earlier xnox provided me some insights into the Python 3.6->3.7 hell that was unleashed by the transition
[00:29] <teward> wxl: error none available, pastebin them for me :P
[00:29]  * wxl facepalms
[00:29] <teward> wxl: my bouncer decided to do a derp so I don't have scrollback
[00:29] <teward> i'll go hunting for logs
[00:29] <wxl> yes you do
[00:29] <teward> wxl: not here at least
[00:30]  * teward doesn't have a scrollback queue after a connection flakes
[00:30] <wxl> https://irclogs.ubuntu.com/2018/11/13/%23ubuntu-devel.html
[00:30] <wxl> yes you do :)\
[00:30] <teward> *drags wxl into dependency hell for other reasons*
[00:30] <doko> teward: not according to the build log and the dependencies. it picked up 3.7
[00:31] <teward> doko: yeah that's what local sbuild suggested, too.
[00:31] <teward> but wxl's tests suggested otherwise heh
[00:31] <teward> *shrugs*
[00:31] <wxl> all i'm seeing is it fail to start because it's looking for the 3.6 libboost-python
[00:31] <teward> maybe it's Boost related?
[00:33] <wxl> like maybe the loading of a boost library somehow is calling a 3.6-dependent version? that seems.. unlikely
[00:33] <doko> vorlon, infinity: tell me something that doesn't entangle with icu :-(
[00:34] <mwhudson> need to find the binary that has DT_NEEDED on the 3.6 so
[00:34] <vorlon> doko: "everything that was allowed to migrate before icu was uploaded"?
[00:34] <vorlon> doko: also, cfitsio
[00:34] <doko> well, if it would have been allowed, why didn't it migrate?
[00:34] <vorlon> which may just be entangled with its own bugginess
[00:35] <doko> always nice to see packages not merged for a year or so ...
[00:36] <mwhudson> seems to be libcalamares.so.3.2.2
[00:36] <vorlon> qtbase5-dev/amd64 unsatisfiable Depends: libvulkan-dev
[00:36] <vorlon> uuuhm?
[00:40] <tsimonq2> Oh yeah.
[00:41] <tsimonq2> vorlon: For now I'll revert that, but long term a Vulkan MIR would be cool.
[00:41] <mwhudson> wxl: i think calamares just needs a rebuild against a newer libboost-python1.67-dev
[00:41] <wxl> looking at the build logs of calamares
[00:41] <tsimonq2> vorlon: (That's following Debian.)
[00:42] <mwhudson> wxl: it built against libboost-python1.67-dev 1.67.0-7
[00:42] <mwhudson> in which libboost_python3 is a symlink to libboost_python36
[00:42] <tsimonq2> Doing.
[00:42] <mwhudson> current devel has libboost-python1.67-dev 1.67.0-10
[00:42] <wxl> oh!
[00:42] <mwhudson> wxl: it built against libboost-python1.67-dev 1.67.0-10
[00:42] <mwhudson> er
[00:42] <wxl> i know what you mean :)
[00:42] <mwhudson> ignore that last line
[00:42] <vorlon> tsimonq2: no, don't
[00:43] <mwhudson> in which libboost_python3 is a symlink to libboost_python37
[00:43] <tsimonq2> Cancelled.
[00:43] <tsimonq2> vorlon: er, rebuild or MIR?
[00:43] <tsimonq2> (Cancelled the former just in case.)
[00:43] <vorlon> bdmurray, gaughen: ^^ it is expedient for us to drop the Qt stack out of main sooner rather than later
[00:43] <wxl> @tsimonq2: wanna NCR cala then? (mwhudson fixed it for you otherwise) :)
[00:43] <tsimonq2> vorlon: ohh, vulkan... continuing with the no-change rebuild then...
[00:43] <tsimonq2> :)
[00:43] <vorlon> tsimonq2: no
[00:43] <mwhudson> something somewhere is busted in all this that you can get the failed to find libs at runtime rather than have dpkg complain at you
[00:44] <wxl> i was mistakenly looking at libboost-python the depend rather than the build-depend
[00:44] <tsimonq2> vorlon: You're being ambiguous ;)
[00:44] <vorlon> tsimonq2: don't revert
[00:44] <tsimonq2> vorlon: ack
[00:44] <wxl> mwhudson: something somewhere in boost you mean?
[00:45] <vorlon> tsimonq2: I'm going to demote these packages to get them to go through; that's going to give us a component-mismatch on a recommends, which it'll be up to the Desktop Team to sort out
[00:45] <mwhudson> wxl: i guess?
[00:45] <wxl> :)
[00:45] <tsimonq2> vorlon: Understood.
[00:45] <mwhudson> and well, definitely not calamares
[00:45] <wxl> mwhudson: well, at the very least it shouldn't be calamares
[00:45] <mwhudson> wxl: jinx!
[00:45] <wxl> :)
[00:45] <mwhudson> i need lunch
[00:45] <mwhudson> biab
[00:45] <wxl> you owe me a coke :)
[00:46] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (bionic-proposed) [2.02-2ubuntu8.9]
[00:46] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (bionic-proposed) [2.02-2ubuntu8.9]
[00:46] <tsimonq2> wxl: https://launchpad.net/ubuntu/+source/calamares/3.2.2-0ubuntu3
[00:46] <tsimonq2> *grabs coke*
[00:47] <wxl> thx
[00:48] <tsimonq2>  sbuild-build-depends-calamares-dummy : Depends: libpythonqt-qt5-python3-dev but it is not going to be installed
[00:48] <tsimonq2>                                         Depends: libpythonqt-qtall-qt5-python3-dev but it is not going to be installed
[00:48] <tsimonq2> yuuup
[00:48] <tsimonq2> It's gonna be a bit. :)
[00:48] <wxl> siiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiigh
[00:49] <tsimonq2> Shush, you :)
[00:49] <wxl> hey you're the one that brought up this whole subject :)
[00:49] <doko> tsimonq2: could you have a look at https://launchpad.net/ubuntu/+source/qtwebengine-opensource-src/5.11.2+dfsg-2build1/+build/15658039 ?
[00:50] <tsimonq2> doko: Looking.
[00:50] <doko> other archs are still building
[00:51] <tsimonq2> doko: Might be this: https://launchpad.net/ubuntu/+source/qtwebengine-opensource-src/5.11.1+dfsg-2ubuntu4
[00:51] <tsimonq2> er
[00:51] <tsimonq2> no
[00:53] <tsimonq2> /usr/bin/ld: warning: libicui18n.so.60, needed by /usr/lib/gcc/i686-linux-gnu/8/../../../i386-linux-gnu/libQt5Core.so, may conflict with libicui18n.so.63
[00:53] <tsimonq2> /usr/bin/ld: warning: libicuuc.so.60, needed by /usr/lib/gcc/i686-linux-gnu/8/../../../i386-linux-gnu/libQt5Core.so, may conflict with libicuuc.so.63
[00:53] <tsimonq2> collect2: error: ld returned 1 exit status
[00:53] <tsimonq2> wat
[00:54] <vorlon> sounds like qtwebengine-opensource-src needs to be rebuilt strictly after qtbase-opensource-src
[00:54] <tsimonq2> right
[00:54] <vorlon> which it can be now on !i386
[00:55] <tsimonq2> I concur.
[01:00] <doko> http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg doesn't look too well either
[01:04] <vorlon> pff who's the knob that hard-coded a dependency on libtirpc1 in nfs-utils debian/control instead of using shlibs.local? oh it was me
[01:07] <vorlon> doko: the python-markdown tree could be pruned if libgirepository1.0-dev was fixed not to pull it in; doesn't seem particularly relevant to the reason we use that binary package (dh_girepository)
[01:07] <vorlon> doko: sorry, "that binary package" == "gobject-introspection"
[01:15] <vorlon> and protobuf appears to break something wrt python bindings; caffe and ola fail their tests the same way
[01:16] <vorlon> ah; requires python-protobuf from the matching version of protobuf, but has no versioned dependency that says this
[05:18] -queuebot:#ubuntu-release- New binary: sbt-launcher-interface [amd64] (disco-proposed/universe) [1.0.1-1] (no packageset)
=== andrewc is now known as Guest67430
[06:58] <ginggs> would someone please 'force-badtest dask/0.17.5-2/amd64' ?  it has regressed in release since cloudpickle 0.5.6-1 migrated
[07:12] -queuebot:#ubuntu-release- New: accepted sbt-launcher-interface [amd64] (disco-proposed) [1.0.1-1]
[08:01] <doko> component_mismatches isn't update since about six hours ...
[10:09] -queuebot:#ubuntu-release- New binary: ros-rviz [i386] (disco-proposed/universe) [1.13.1+dfsg-1] (no packageset)
[10:10] -queuebot:#ubuntu-release- New binary: ros-rviz [amd64] (disco-proposed/universe) [1.13.1+dfsg-1] (no packageset)
[10:39] -queuebot:#ubuntu-release- New binary: ros-rviz [armhf] (disco-proposed/universe) [1.13.1+dfsg-1] (no packageset)
[10:55] -queuebot:#ubuntu-release- New binary: ros-rviz [arm64] (disco-proposed/universe) [1.13.1+dfsg-1] (no packageset)
[12:46] -queuebot:#ubuntu-release- New source: python-oslo.upgradecheck (disco-proposed/primary) [0.1.1-0ubuntu1]
[12:50] -queuebot:#ubuntu-release- New: accepted python-oslo.upgradecheck [source] (disco-proposed) [0.1.1-0ubuntu1]
[12:50] -queuebot:#ubuntu-release- New: accepted ros-rviz [arm64] (disco-proposed) [1.13.1+dfsg-1]
[12:50] -queuebot:#ubuntu-release- New: accepted ros-rviz [i386] (disco-proposed) [1.13.1+dfsg-1]
[12:50] -queuebot:#ubuntu-release- New: accepted ros-rviz [amd64] (disco-proposed) [1.13.1+dfsg-1]
[12:50] -queuebot:#ubuntu-release- New: accepted ros-rviz [armhf] (disco-proposed) [1.13.1+dfsg-1]
[12:53] -queuebot:#ubuntu-release- New binary: python-oslo.upgradecheck [amd64] (disco-proposed/none) [0.1.1-0ubuntu1] (no packageset)
[13:01] -queuebot:#ubuntu-release- New: accepted python-oslo.upgradecheck [amd64] (disco-proposed) [0.1.1-0ubuntu1]
=== chrisccoulson_ is now known as chrisccoulson
[14:33] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (bionic-proposed/main) [4.15.0-1032.33] (kernel)
[14:37] <rbalint> rbasak, if you have some time could you please take a look at u-u in unapproved?
[14:38] <rbalint> (bb and cc)
[14:40] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [4.15.0-1032.33]
[14:42] <rbasak> rbalint: I'll see, but looks like that's going to take a long time to review :-/
[15:08] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (trusty-proposed/main) [4.15.0-1032.33~14.04.2] (kernel)
[15:09] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (trusty-proposed) [4.15.0-1032.33~14.04.2]
[15:09] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1032.33~16.04.1] (kernel)
[15:10] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1032.33~16.04.1]
[15:41] -queuebot:#ubuntu-release- Unapproved: sosreport (cosmic-proposed/main) [3.5-1ubuntu4 => 3.6-1ubuntu0.18.10.1] (ubuntu-desktop, ubuntu-server)
[15:42] -queuebot:#ubuntu-release- Unapproved: sosreport (bionic-proposed/main) [3.5-1ubuntu3.18.04.1 => 3.6-1ubuntu0.18.04.1] (ubuntu-desktop, ubuntu-server)
[15:42] -queuebot:#ubuntu-release- Unapproved: sosreport (xenial-proposed/main) [3.5-1~ubuntu16.04.3 => 3.6-1ubuntu0.16.04.1] (ubuntu-desktop, ubuntu-server)
[16:11] <slashd> bdmurray, rbasak or any SRU vanguard, I mis-understood bdmurray's message on bug 1775195, and assumed he rejected the upload, but in fact, he didn't. I have re-upload a fixed version of sosreport ^ in the upload queues for X,B,C and then realized there is 2 sosreport in each. Can you reject the uploads of "2018-11-12", and keep the today's ones ? thanks in advance and sorry for the inconvenient.
[16:11] <ubot5> bug 1775195 in sosreport (Ubuntu Cosmic) "[sync][sru]sosreport v3.6" [Wishlist,In progress] https://launchpad.net/bugs/1775195
[16:13] <bdmurray> slashd: I can do that
[16:13] <slashd> bdmurray, thanks
[16:14] -queuebot:#ubuntu-release- Unapproved: rejected sosreport [source] (bionic-proposed) [3.6-1ubuntu18.04.1]
[16:14] -queuebot:#ubuntu-release- Unapproved: rejected sosreport [source] (cosmic-proposed) [3.6-1ubuntu18.10.1]
[16:15] -queuebot:#ubuntu-release- Unapproved: rejected sosreport [source] (xenial-proposed) [3.6-1ubuntu16.04.1]
[16:42] -queuebot:#ubuntu-release- New binary: python-pyftpdlib [amd64] (disco-proposed/universe) [1.5.4-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: scala-pickling [amd64] (disco-proposed/none) [0.10.1+repack-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: sbt-template-resolver [amd64] (disco-proposed/none) [0.1+repack-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: scopt [amd64] (disco-proposed/none) [3.5.0+repack-1] (no packageset)
[17:38] -queuebot:#ubuntu-release- New: accepted sbt-template-resolver [amd64] (disco-proposed) [0.1+repack-1]
[17:38] -queuebot:#ubuntu-release- New: accepted scopt [amd64] (disco-proposed) [3.5.0+repack-1]
[17:39] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [amd64] (disco-proposed) [0.4.0-1]
[17:39] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [armhf] (disco-proposed) [0.4.0-1]
[17:39] -queuebot:#ubuntu-release- New: accepted python-pyftpdlib [amd64] (disco-proposed) [1.5.4-1]
[17:39] -queuebot:#ubuntu-release- New: accepted ukui-biometric-manager [amd64] (disco-proposed) [1.0.0-2]
[17:39] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [arm64] (disco-proposed) [0.4.0-1]
[17:39] -queuebot:#ubuntu-release- New: accepted scala-pickling [amd64] (disco-proposed) [0.10.1+repack-1]
[17:39] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [i386] (disco-proposed) [0.4.0-1]
[17:39] -queuebot:#ubuntu-release- New: accepted ukui-biometric-manager [arm64] (disco-proposed) [1.0.0-2]
[17:39] -queuebot:#ubuntu-release- New: accepted linphone [amd64] (disco-proposed) [3.12.0-3]
[17:39] -queuebot:#ubuntu-release- New: accepted prometheus-process-exporter [s390x] (disco-proposed) [0.4.0-1]
[17:39] -queuebot:#ubuntu-release- New: accepted linphone [i386] (disco-proposed) [3.12.0-3]
[17:46] -queuebot:#ubuntu-release- Unapproved: accepted ghostscript [source] (trusty-proposed) [9.25~dfsg+1-0ubuntu0.14.04.3]
[17:57] -queuebot:#ubuntu-release- New binary: kopanocore [amd64] (disco-proposed/universe) [8.6.5-1ubuntu1] (no packageset)
[17:59] <doko> Package: glance-api
[17:59] <doko> Depends: python-glance (= 2:18.0.0~b1~git20181108.97dac0f3-0ubuntu1) | python3-glance (= 2:18.0.0~b1~git20181108.97dac0f3-0ubuntu1)
[17:59] <doko> python-glance is in main, but britney complains about
[18:00] <doko> glance-api/amd64 unsatisfiable Depends: python3-glance (= 2:18.0.0~b1~git2018111404.d2e62d43-0ubuntu1)
[18:00] <doko> Not considered
[18:00] <doko> which is in universe. why?
[18:03] <doko> anyway, now promoted
[18:06] <cjwatson> doko: exactly because britney is aware of permitted inter-component dependencies
[18:07] <cjwatson> oh, you mean the alternative
[18:08] <cjwatson> that seems a little odd, not sure why
[18:09] <doko> yes, the alternative was in universe
[18:12] -queuebot:#ubuntu-release- New binary: kopanocore [amd64] (disco-proposed/universe) [8.6.5-1ubuntu2] (no packageset)
[18:13] -queuebot:#ubuntu-release- Unapproved: stress-ng (bionic-proposed/universe) [0.09.25-1 => 0.09.25-1ubuntu1] (no packageset)
[18:14] -queuebot:#ubuntu-release- Unapproved: stress-ng (cosmic-proposed/universe) [0.09.42-1 => 0.09.42-1ubuntu1] (no packageset)
[18:16] -queuebot:#ubuntu-release- New: accepted kopanocore [amd64] (disco-proposed) [8.6.5-1ubuntu1]
[18:16] -queuebot:#ubuntu-release- New: accepted kopanocore [amd64] (disco-proposed) [8.6.5-1ubuntu2]
[18:31] <infinity> doko: python-glance was dropped in proposed, only python3-glance remains.
[18:32] <infinity> doko: Which explains britney's concern there.
[18:32] <doko> ahh, ok
[18:42] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (xenial-proposed/main) [0.90ubuntu0.9 => 1.1ubuntu1.18.04.7~16.04.0] (desktop-core, ubuntu-server)
[18:55] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-40.43] (core, kernel)
[18:55] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-40.43] (core, kernel)
[19:04] <doko> vorlon: added python-markdown-doc to extra-excludes now to get it out of component mismatches
[19:04] <vorlon> oh, was it docs-only? ok
[19:15] <vorlon> cfitsio and icu transitions also entangled via qt, well then
[19:18] <vorlon> anyone here have insight into the libreoffice test failures and how to unstick them? I don't want to throw a bunch of those back at the wall for obvious reasons, but they're blocking both icu and qt
[19:18] <teward> vorlon: qt, icu, and python all have such heavy integration migrations of them break everything >.>
[19:18] <doko> jbicha: mozc still pulls in qt* into main
[19:19] <vorlon> doko: as discussed on #ubuntu-devel, seb128 will be following up on that demotion
[19:19] <doko> well, python and perl are done, but I'm only down to three ftbfs with icu: http://people.canonical.com/~ubuntu-archive/transitions/html/icu.html
[19:20] <doko> and postgresql-11 is involved as well of course
[19:20] <vorlon> plus 12 other libraries
[19:20] <doko> r-cran-stringi, mozjs60, nodejs
[19:20] <vorlon> nodejs> nuke it, no problem
[19:21] <vorlon> s390x-specific?  maybe xnox needs something to do
[19:22] <xnox> hm
[19:22] <doko> pinged desktop about mozjs
[19:23] <xnox> nodejs s390x i see
[19:23] <xnox> vorlon, i've seen not ok 560 parallel/test-fs-realpath-pipe fail in disco, on all releases. locally and in a ppa.
[19:24] <xnox> e.g. https://launchpad.net/~xnox/+archive/ubuntu/nonvirt/+packages?field.name_filter=nodejs&field.status_filter=published&field.series_filter=disco
[19:24] <xnox> vorlon, i guess you don't want me to start nodejs v10 transition out of the blue
[19:26] <vorlon> xnox: I will revert it instantly if you do
[19:27] <vorlon> so feel free ;)
[19:27] <doko> still in debian new ;p
[19:27] <vorlon> in fact, maybe we should turn off autosyncs for a bit right now
[19:28] <doko> +1
=== vorlon changed the topic of #ubuntu-release to: Released: Bionic 18.04.1, Cosmic 18.10 | Archive: Open; autosyncs disabled | Disco Release Coordination | Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | We accept payment in cash, check or beer | melius malum quod cognoscis.
[19:51] <infinity> doko: That r-cran-stringi failure on s390x is pretty suspicious.
[19:53] <infinity> ppc64el:
[19:53] <infinity> checking whether we may compile src/icu61/common/putil.cpp... yes
[19:53] <infinity> checking whether we can fetch icudt... icudt already downloaded
[19:53] <infinity> s390x:
[19:53] <infinity> checking whether we may compile src/icu61/common/putil.cpp... yes
[19:53] <infinity> checking whether we can fetch icudt... downloading the ICU data library (icudt)
[19:53] <xnox> *** The available ICU4C cannot be used
[19:53] <infinity> (And then it obviously explodes because it can't download)
[19:53] <infinity> xnox: That's the same on all arches.
[19:53] <xnox> hm
[19:55] <infinity> xnox: Though that's also different from building against the previous ICU.
[19:55] <infinity> checking for ICU4C >= 52... yes
[19:56] <xnox> ./src/icu61/data/icudt61l.zip
[19:56] <xnox> it has a predownloaded copy of icudt for little endian.
[19:56] <xnox> and seems to use that everywhere, instead of using the system icu63....
[19:57] <xnox> and it doesn't have a big one predownloaded in the package.
[19:57] <infinity> Ahh, gross.
[19:57] <infinity> We don't want that at all.
[19:57] <xnox> *** The available ICU4C cannot be used is imho bad....
[19:58] <infinity> Should probably be built with --disable-icu-bundle to force not using the bundled one on rebuilds.
[19:58] <xnox> so need to run this and check the bugs in their conftest
[19:59] <infinity> Hrm, it uses pkg-config.  Did we lose the pkg-config file again?
[20:00] <xnox> checking with pkg-config for the system ICU4C... 63.1
[20:00] <xnox> no that was fine
[20:00] <xnox> U_CHARSET_IS_UTF8==0... no is where it bombs then?
[20:01] <xnox> The available ICU4C cannot be used is like the same string mentioned multiple times
[20:01] <infinity> It bombs on a complile test.
[20:01] <infinity> Which looks pretty simple.
[20:17] <jbicha> infinity: could you update the hints? https://paste.debian.net/1051531
[20:17] <jbicha> pgagent's autopkgtests are still a problem though
[20:29] <ginggs> xnox, infinity: see #913626
[20:37] <xnox> omg
[20:37] <xnox> whatever.
[20:45] <acheronuk> klinkstatus FTBFS with rebuild against libtidy5deb1 so I think we can go ahead with removing from disco LP: #1757699
[20:45] <ubot5> Launchpad bug 1757699 in klinkstatus (Ubuntu) "Please port your package away from Qt 4" [Undecided,New] https://launchpad.net/bugs/1757699
[20:45] <acheronuk> tsimonq2: ^^
[21:01] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (cosmic-proposed) [3.6-1ubuntu0.18.10.1]
[21:03] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1027.32] (kernel)
[21:05] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (bionic-proposed) [3.6-1ubuntu0.18.04.1]
[21:09] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (xenial-proposed) [3.6-1ubuntu0.16.04.1]
[21:48] <vorlon> jamespage, coreycb: it would appear that rabbitmq-server 3.7.8-4 in disco-proposed is entirely failing to start on install, causing all autopkgtests for its revdeps to fail and blocking an erlang transition
[22:30] <coreycb> vorlon: ok we'll take a look
[23:33] <vorlon> doko: fwiw I think you've triggered reruns of libreoffice autopkgtests that were already in the queue (for icu)
[23:38] <doko> mehh, doesn't matter as long as launchpad isn't stable long enough to build qtwebengine-opensource-src on armhf. it's restarted again
[23:39] <vorlon> doko: it matters that it's wasting runner time on our slowest archs for a 3h+ test...
[23:41] <doko> is http://autopkgtest.ubuntu.com/packages/libr/libreoffice/disco/s390x given back too?
[23:42] <vorlon> doko: yes, your test was a duplicate of rik's that was already running
[23:42] <vorlon> (and passed)
[23:43] <doko> ugh, libproxy again depends on libmozjs-52-0, which is in universe?
[23:44] <doko> now time for pcre2 in main? libpam-mount depends on libpcre2-8-0
[23:45] <doko> no, demote libproxy1-plugin-mozjs
[23:46] <jbicha> doko: that libproxy binary package can be demoted to universe but I suggested that Debian remove that binary package anyway in Debian bug 912940
[23:46] <ubot5> Debian bug 912940 in libproxy1-plugin-mozjs "libproxy1-plugin-mozjs: Depends on mozjs52 which is unmaintained upstream" [Important,Open] http://bugs.debian.org/912940
[23:47] <jbicha> if you're doing demotions, please demote libblockdev-vdo-dev libblockdev-vdo2 udisks2-bcache udisks2-vdo udisks2-zram
[23:47] <jbicha> so that udisks2 can migrate
[23:49] <jbicha> if you're open to pcre2 going in to main, I guess we just have to convince Jamie now. See his recent-ish comment on bug 1636666
[23:49] <ubot5> bug 1636666 in pcre2 (Ubuntu) "[MIR] pcre2" [Undecided,Confirmed] https://launchpad.net/bugs/1636666
[23:49] <jbicha> php7.3 is a big motivator for pcre2
[23:50] <teward> jbicha: can you provide some insights on why nginx is blocked by exim4?  Is it because exim tests on httpd or something?  (I ask because if nginx can't build on pcre2 you'd still need pcre3 in main if it's a build blocker/dependency)
[23:50] <teward> (I'm a little unclear how it's blocked)
[23:51] <jbicha> sadly, pcre3 is going to be around in main for a while, see bug 1792544
[23:51] <ubot5> bug 1792544 in vte2.91 (Ubuntu) "demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)" [Undecided,Triaged] https://launchpad.net/bugs/1792544
[23:51] <teward> jbicha: right, but i'm looking at comment 33 from jdstrand -1'ing the inclusion of both
[23:52] <teward> so unless something's changed?
[23:53] <jbicha> it's being more uncomfortable to try to keep pcre2 out of main
[23:54] <jbicha> when it was only vte/gnome-terminal/gnome-builder, it wasn't causing many people pain, but php…
[23:54] <teward> ack.
[23:58] <doko> isn't the new php only supporting that?