[00:29] <vorlon> LocutusOfBorg: confirmed, firewalld hinted now
[01:50] <mwhudson> vorlon: http://michael.hudsondoyle.geek.nz/rcbuggy-problem-packages.html
[06:29] -queuebot:#ubuntu-release- New sync: taffybar (eoan-proposed/primary) [3.0.0-2]
[06:32] <LocutusOfBorg> vorlon, taffybar has been fixed ^^
[06:44] -queuebot:#ubuntu-release- New binary: ldc [i386] (eoan-proposed/universe) [1:1.17.0-2] (no packageset)
[06:45] -queuebot:#ubuntu-release- New binary: ldc [amd64] (eoan-proposed/universe) [1:1.17.0-2] (no packageset)
[07:03] -queuebot:#ubuntu-release- New: accepted freeipa [amd64] (eoan-proposed) [4.8.1-0ubuntu1]
[07:03] -queuebot:#ubuntu-release- New: accepted freeipa [armhf] (eoan-proposed) [4.8.1-0ubuntu1]
[07:03] -queuebot:#ubuntu-release- New: accepted freeipa [ppc64el] (eoan-proposed) [4.8.1-0ubuntu1]
[07:03] -queuebot:#ubuntu-release- New: accepted ldc [amd64] (eoan-proposed) [1:1.17.0-2]
[07:03] -queuebot:#ubuntu-release- New: accepted freeipa [arm64] (eoan-proposed) [4.8.1-0ubuntu1]
[07:03] -queuebot:#ubuntu-release- New: accepted freeipa [s390x] (eoan-proposed) [4.8.1-0ubuntu1]
[07:03] -queuebot:#ubuntu-release- New: accepted freeipa [i386] (eoan-proposed) [4.8.1-0ubuntu1]
[07:03] -queuebot:#ubuntu-release- New: accepted ldc [i386] (eoan-proposed) [1:1.17.0-2]
[07:09] -queuebot:#ubuntu-release- Unapproved: rejected net-snmp [source] (disco-proposed) [5.7.3+dfsg-5ubuntu1.2]
[07:25] -queuebot:#ubuntu-release- Unapproved: accepted net-snmp [source] (disco-proposed) [5.7.3+dfsg-5ubuntu1.2]
[07:37] -queuebot:#ubuntu-release- Unapproved: rejected net-snmp [source] (bionic-proposed) [5.7.3+dfsg-1.8ubuntu3.3]
[07:48] -queuebot:#ubuntu-release- Unapproved: accepted net-snmp [source] (bionic-proposed) [5.7.3+dfsg-1.8ubuntu3.3]
[08:04] -queuebot:#ubuntu-release- Unapproved: rejected net-snmp [source] (xenial-proposed) [5.7.3+dfsg-1ubuntu4.4]
[08:13] -queuebot:#ubuntu-release- Unapproved: accepted net-snmp [source] (xenial-proposed) [5.7.3+dfsg-1ubuntu4.4]
[09:15] <LocutusOfBorg> update output notest shows ghc as successful
[09:38] <doko> LocutusOfBorg: do you know which tests are blocking?
[09:40] <LocutusOfBorg> doko, yes
[09:40] <LocutusOfBorg> https://github.com/spatialaudio/nbsphinx/issues/317
[09:40] <gitbot> spatialaudio issue 317 in nbsphinx "pdf / svg generation issue with new pandoc" [Open]
[09:40] <LocutusOfBorg> only this one
[09:40] <LocutusOfBorg> I'm working on it
[09:42] <doko> ta
[09:42] <doko> too many rdepends to remove
[09:45] <LocutusOfBorg> I see, unfortunately
[09:47] <LocutusOfBorg> mmm I syncd antlr, dropping python-antlr, no reverse-dependencies, not shown on https://people.canonical.com/~ubuntu-archive/nbs.html but not migrating
[09:47] <LocutusOfBorg> anything wrong I did on my side?
[09:53] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.15.0-62.69~16.04.1]
[09:53] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (xenial-proposed) [4.15.0-62.69~16.04.1]
[09:54] <LocutusOfBorg> doko, you should probably sync stdx-allocator gir-to-d and after it dinstalls glib-d
[09:55] <LocutusOfBorg> can I do it?
[10:03] <doko> sure
[10:04] <LocutusOfBorg> they should make the build progress a little more
[10:37] <LocutusOfBorg> doko, gobject-introspection might be broken on armhf...
[10:37] <LocutusOfBorg> https://launchpad.net/ubuntu/+source/glib-d/2.1.0-1/+build/17743399
[10:38] <LocutusOfBorg> _DT20_D7gobject10TypeModule10TypeModule9__mixin1316completeTypeInfoMFE7gobject1c5types5GTypePS7gobject1c5types9GTypeInfoPS7gobject1c5types15GTypeValueTableZv
[10:38] <LocutusOfBorg> I can't demangle that symbol with c++filt
[10:38] <doko> Laney: ^^^
[10:40] <Laney> try asking ricotz
[10:40] <LocutusOfBorg> I don't even know where that symbol comes from, and why it comes double
[10:40] <LocutusOfBorg> oh... might be a gtk-d internal symbol
[10:40] <Laney> but some debugging first would be nice I guess
[10:40] <LocutusOfBorg> d language, why you so funny?
[10:43]  * LocutusOfBorg goes back to ghc
[10:50] <doko> Laney: duplicty wants to pull in python2 again into main, depending on python-lockfile ...
[10:51] <doko> Laney: duplicity also needs a MIR for libb2 via rsync
[11:00] <LocutusOfBorg> oh, libb2! that package uploaded only once on 2015 by a person who disappeared and a sponsor who disappeared, and I had to patch 6 times to make it suitable for stable...
[11:00] <LocutusOfBorg> it might be in a good shape now, but meh
[11:16] <tjaalton> did autopkgtests stop installing recommends?
[11:16] <tjaalton> in eoan
[11:18] <doko> did they ever install recommends?
[11:19] <doko> LocutusOfBorg: you did a libb2 team upload without changing the maintainer ...
[11:20] <tjaalton> doko: well, noticed because freeipa tests fail due to ssl-cert is not installed, and I assume it was previously pulled in by apache2
[11:20] <tjaalton> could be some other package relaxed the dep
[11:20] <doko> that sounds more plausible
[11:21] <LocutusOfBorg> doko, it wasn't a real team upload, it was a collab-maint package
[11:21] <LocutusOfBorg> anyway, I'm thinking to revert llvm-defaults to 8...
[11:21] <LocutusOfBorg> https://launchpadlibrarian.net/441260638/buildlog_ubuntu-eoan-amd64.meson_0.51.2-1_BUILDING.txt.gz
[11:21] <LocutusOfBorg> looks like llvm-9 is totally broken
[11:21] <tjaalton> sigh
[11:21] <tjaalton> and I'd need it for mesa
[11:21] <LocutusOfBorg> oh... wait
[11:21] <LocutusOfBorg> syncd from experimental
[11:22] <LocutusOfBorg> tjaalton, this might make you happy too
[11:22] <LocutusOfBorg> did you already try ~exp3?
[11:22] <tjaalton> no
[11:22] <LocutusOfBorg> we discussed that some days ago on #debian-llvm channel
[11:22] <tjaalton> yes
[11:22] <LocutusOfBorg> something bad is happening with gcc-9
[11:31] <tjaalton> mesa builds fine with exp3
[11:35] <LocutusOfBorg> lovely!
[11:38] <Laney> doko: you probably want to tell seb128, I've not been handling that one
[11:38] <Laney> or x_nox who was also looking into it
[11:39] <doko> seb128: ^^^
[11:39] <doko> Laney: I am abusing you as a messenger ;p
[11:40] <doko> xnox is away today
[11:40] <Laney> I do make a very nice secretary
[11:40] <doko> foundations is in need of secretaries ...
[11:46] <seb128> doko, duplicity is in universe why would it pull anything in main?
[11:47] <seb128> doko, I will have a look to the depends, but someone needs to sort out the ppc64el issue :/
[11:47] <doko> seb128: https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[11:48] <seb128> doko, speaking about MIR can we get the rygel one unblocked?
[11:48] <doko> seb128: looks incomplete according to the svg
[11:49] <seb128> doko, well it's blocked on the MIR team to do the review from what I know...
[11:51] <doko> seb128: well according to the svg a MIR for gupnp-av is missing. did you even look at the svg?
[11:51] <seb128> doko, gupnp-av is  bug #1785629 but it expired due to the MIR team process of marking incomplete things not for the current cycles, which got closed by launchpad expiration
[11:52] <seb128> doko, ^ it's there, just a process/tooling issue
[11:53] <doko> well, you changed it from expired to new a minute ago ... not a tooling issue
[11:54] <seb128> doko, well, it shouldn"'t have been closed in the first place, that process of marking incomplete things that are not incomplete is what did lead to have it expire
[11:55] <seb128> doko, anyway, next refresh will give you the right color on the svg now :)
[11:56] <seb128> doko, which bring back to the initial question, can we get the MIR team side unblocked? security team did ack those components and the first review comments were addressed, it should be good to og
[11:56] <doko> it's not just the svg, but an expired issue is just not seen by the MIR team
[11:56] <seb128> right
[11:56] <seb128> don't mark bugs incomplete when they are not was my suggestion to that problem
[11:56] <seb128> use a tag to skip-this-cycle or something instead maybe?
[11:56] <seb128> anyway
[11:57] <seb128> as said next refresh will have the correct status
[11:57] <seb128> can we get back to the main topic and get the reviews unblocked?
[11:58] <seb128> at least rygel and gupno-dlna got a +1 from security and I think just need MIR team to have another look but should be good to go
[13:04] <xnox> seb128:  a package in main, used to dynamically install all of that.
[13:04] <xnox> seb128:  the reason for it, in the past was python2, now that it is python3 it should be in main.
[13:05] <xnox> seb128:  i will check what else is missing, and yeah we might skip it for now, but we really ought to bring it into main....
[13:05] <xnox> and yes, at conference today
[13:05] <seb128> xnox, right, well first step would be to have someone debugging what is wrong on ppc64el
[13:06] <xnox> upstream is notified, in multiple bugs about ppc64el
[13:06] <xnox> no idea why they are not enabling all arches in their nightly ppa
[13:06] <xnox> they have regressed upstream arch support
[14:01] <seb128> xnox, they are, but they seem to either not care or not be able to debug (they probably don't have access to a ppc64el system)
[14:03] <doko> seb128: there is a recent thread on debian-private about access to that kind of hardware
[14:12] <seb128> doko, thx for the pointer, I can try to talk to them but my impression was just that they probably have 0 user on that arch and they have no interest in debugging an issue specific to it
[14:28] <seb128> doko, I don't understand that duplicity/python-lockfile reference on c-m-p
[14:28] <seb128> $ dpkg -I duplicity_0.8.03-0ubuntu1_amd64.deb | grep lockfile
[14:28] <seb128>  Depends: libc6 (>= 2.4), librsync2 (>= 1.0.0), python3 (<< 3.8), python3 (>= 3.7~), python3-fasteners, python3-future, python3:any (>= 3.5~), python3-lockfile, gnupg | gnupg1
[14:29] <seb128> the packaging/deb reference correctly to python3-lockfile
[14:45] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (disco-proposed) [3.6-1ubuntu2.1]
[14:47] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (bionic-proposed) [3.6-1ubuntu0.18.04.3]
[14:51] -queuebot:#ubuntu-release- Unapproved: accepted sosreport [source] (xenial-proposed) [3.6-1ubuntu0.16.04.3]
[14:57] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (disco-proposed/main) [1:19.04.16.6 => 1:19.04.16.7] (core)
[15:25] <xnox> seb128:  it's via doc package which is recommended by python3 package, and itself depends on the python2 package
[15:25] <xnox> doko:  ^ (same thing again)
[15:25] <seb128> xnox, ah, thx
[15:27] <xnox> seb128:  doko: excluded python-lockfile-doc from the seeds now. should go away on next report update.
[15:27] <seb128> xnox, thx!
[17:02] <LocutusOfBorg> please accept taffybar from eoan queue, it has been removed to fix haskell transition, but has been fixed in the meanwhile
[17:02] <LocutusOfBorg> vorlon, ^^
[17:02] <LocutusOfBorg> I'm uploading the last fix for haskell before migration
[17:28] <fossfreedom> Hi - is there anything awry with the daily builds?  Our last two daily builds haven't completed successfully.  Any thoughts? https://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-budgie/eoan/
[17:34] <RikMills> fossfreedom: I see a build for today here: http://cdimage.ubuntu.com/ubuntu-budgie/daily-live/current/
[17:36] <RikMills> yesterdays livefs build failed without a log
[17:37] <fossfreedom> thx. aarghhh... browser cache.  correct - all ok.  sorry for the noise
[18:38] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (disco-proposed/main) [5.0.0-1019.20] (core, kernel)
[19:51] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (disco-proposed) [5.0.0-1019.20]
[21:14] -queuebot:#ubuntu-release- Unapproved: rejected systemd [source] (bionic-proposed) [237-3ubuntu10.29]