[07:46] <Laney> sil2100: will look but it'll probably have to be next week (sorry for the delayed reply)
[07:48] <sil2100> Laney: no worries o/
[07:48] <Laney> :>
[07:55] <oSoMoN> tdaitx, LO 6.0.7 built successfully against openjdk-11 in https://launchpad.net/~osomon/+archive/ubuntu/lo-bionic-openjdk11/+packages
[07:55] <oSoMoN> so it looks like that patch is all that was needed
[07:56] <oSoMoN> I'll do some smoke testing in a VM to verify that the basic functionality that relies on the JVM works
[08:17] <bdmurray> rbalint: Here is how gdb is called and the issue I'm seeing - https://pastebin.ubuntu.com/p/Dv5p54XPYt/
[08:25] <rbalint> bdmurray, seems like this one https://sourceware.org/bugzilla/show_bug.cgi?id=10542
[08:26] <rbalint> bdmurray, or it seems to be fixed only partially
[08:44] <oSoMoN> tdaitx, smoke testing didn't uncover any obvious regressions, and I confirm that the crash on i386 is gone
[08:50] <oSoMoN> tdaitx, and I've pushed the patch to the libreoffice source package VCS: https://code.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/+git/libreoffice-debian-pkg/+ref/ubuntu-bionic-6.0
[09:14] <RAOF> jbicha: I have not forgotten colord. I don't know why it's failing, but it fails in a local autopkgtest run and *appears* to be an actual test failure, but I have absolutely no idea what's wrong.
[10:01] <infinity> RAOF: I suspect what's wrong is that colord is a flaming heap.
[10:23] <LtWorf> what's ubuntu going to do about iptables nft? Debian basically replaced iptables to use nft and called the normal iptables "iptables-legacy"
[10:26] <LtWorf> (whichis kinda fucked since it breaks EVERYTHING)
[10:37] <sarnold> LtWorf: we're apparently getting that when this clears -proposed https://launchpad.net/ubuntu/+source/iptables/1.8.2-3ubuntu1 -- I don't know when that is, but it's coming
[10:38] <sarnold> LtWorf: ufw can manage with the netfilter backend to the 'new' iptables; libvirt's got an issue (I don't know what) with the 'new' iptables
[10:40] <sarnold> and here's the excuses page http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#iptables
[10:44] <LtWorf> ok thanks!
[10:50] <infinity> Laney: Is it expected for me to no longer have a dock?
[10:55] <infinity> Laney: Nevermind, seb128 got me sorted out.
[12:00] <jbicha> RAOF: before this week, the failing colord test was just skipped 🤷
[12:11] <RAOF> <freenode_jbi "RAOF: before this week, the fail"> Huh! I wonder what caused it to start not being skipped.
[12:13] <jbicha> RAOF: it looked like the dpkg update might have triggered the failure but I don't understand why…
[12:14] <jbicha> https://ci.debian.net/packages/c/colord/unstable/amd64/ is kind of special: I managed to get colord to pass once (Jan 22)
[12:38] <infinity> jbicha: Blaming dpkg for colord is surely a red herring.
[12:52] <jbicha> infinity: perhaps but the evidence does point to dpkg being the trigger https://ci.debian.net/packages/c/colord/testing/amd64/
[12:52] <seb128> does anyone has an idea what makes libhsqldb1.8.0-java uninstallable in disco builders?
[12:55] <infinity> jbicha: Oh.  Does it use start-stop-daemon, perchance?
[12:59] <infinity> jbicha: There's https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921557 maybe?
[13:02] <jbicha> infinity: it doesn't look to me like it uses start-stop-daemon
[13:14] <oSoMoN> seb128, libhsqldb1.8.0-java depends on libservlet3.1-java, which depends on libjsp-api-java, which doesn't exist
[13:14] <cjwatson> oSoMoN: I just NEWed it
[13:15] <oSoMoN> cjwatson, thanks
[13:15] <seb128> oSoMoN, cjwatson, thx
[13:15] <cjwatson> (after bootstrapping it, at doko's request)
[13:15] <seb128> oSoMoN, I tried in a pbuilder and it didn't hit the error unsure why, but good it's fixed, we can retry libreoffice in a bit then
[13:15] <oSoMoN> yep
[13:15] <cjwatson> Your pbuilder may just not have had -proposed enabled
[13:20] <seb128> I did enable proposed, maybe I hit the local proxy or something? or maybe I screwed up... anyway doesn't matter much if it's resolved
[13:27] <cjwatson> seb128: Oh yeah, the local proxy will very probably ruin your day
[13:27] <seb128> :)
[13:27] <cjwatson> At least if you wanted to have a view that does more than pretend to be a little bit current
[13:27] <seb128> right, that's my bet on why I didn't reproduce the issue