=== yikoru_ is now known as yikoru === yikoru_ is now known as yikoru [07:46] sil2100: will look but it'll probably have to be next week (sorry for the delayed reply) [07:48] Laney: no worries o/ [07:48] :> [07:55] tdaitx, LO 6.0.7 built successfully against openjdk-11 in https://launchpad.net/~osomon/+archive/ubuntu/lo-bionic-openjdk11/+packages [07:55] so it looks like that patch is all that was needed [07:56] I'll do some smoke testing in a VM to verify that the basic functionality that relies on the JVM works === Laney changed the topic of #ubuntu-devel to: Archive: FF, DIF | 18.10 Released! | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Trusty-Cosmic | If you can't send messages here, authenticate to NickServ first | Patch Pilots: [08:17] rbalint: Here is how gdb is called and the issue I'm seeing - https://pastebin.ubuntu.com/p/Dv5p54XPYt/ [08:25] bdmurray, seems like this one https://sourceware.org/bugzilla/show_bug.cgi?id=10542 [08:25] sourceware.org bug 10542 in symtab "'set debug-file-directory' has no effect" [Normal,Unconfirmed] [08:26] bdmurray, or it seems to be fixed only partially [08:44] tdaitx, smoke testing didn't uncover any obvious regressions, and I confirm that the crash on i386 is gone === cpaelzer_ is now known as cpaelzer [08:50] 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] 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] RAOF: I suspect what's wrong is that colord is a flaming heap. [10:23] 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] (whichis kinda fucked since it breaks EVERYTHING) [10:37] 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] 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] and here's the excuses page http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#iptables [10:44] ok thanks! [10:50] Laney: Is it expected for me to no longer have a dock? [10:55] Laney: Nevermind, seb128 got me sorted out. [12:00] RAOF: before this week, the failing colord test was just skipped 🤷 [12:11] Huh! I wonder what caused it to start not being skipped. [12:13] RAOF: it looked like the dpkg update might have triggered the failure but I don't understand why… [12:14] 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] jbicha: Blaming dpkg for colord is surely a red herring. [12:52] infinity: perhaps but the evidence does point to dpkg being the trigger https://ci.debian.net/packages/c/colord/testing/amd64/ [12:52] does anyone has an idea what makes libhsqldb1.8.0-java uninstallable in disco builders? [12:55] jbicha: Oh. Does it use start-stop-daemon, perchance? [12:59] jbicha: There's https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921557 maybe? [12:59] Debian bug 921557 in dpkg "start-stop-daemon: behavior change on "matching only on non-root pidfile /run/exim4/exim.pid is insecure" not fully documented" [Important,Open] [13:02] infinity: it doesn't look to me like it uses start-stop-daemon [13:14] seb128, libhsqldb1.8.0-java depends on libservlet3.1-java, which depends on libjsp-api-java, which doesn't exist [13:14] oSoMoN: I just NEWed it [13:15] cjwatson, thanks [13:15] oSoMoN, cjwatson, thx [13:15] (after bootstrapping it, at doko's request) [13:15] 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] yep [13:15] Your pbuilder may just not have had -proposed enabled [13:20] 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] seb128: Oh yeah, the local proxy will very probably ruin your day [13:27] :) [13:27] At least if you wanted to have a view that does more than pretend to be a little bit current [13:27] right, that's my bet on why I didn't reproduce the issue === grumble is now known as `-_-`grumble === `-_-`grumble is now known as grumble