[02:16] <karstensrage> infinity, hope everything is well, maybe we could pick up next week?
[02:16] <karstensrage> if you need time, i totally understand though
[06:42] <ginggs> kirkland: hi! calc-stats FTBFS https://launchpad.net/ubuntu/+source/calc-stats/1.4-0ubuntu1 and the README file seems to relate to a different package
[06:49] <LocutusOfBorg> ricotz, what is the rationale for that ca-certificates-java patch?
[06:49] <LocutusOfBorg> as said on -release some days ago, the "fix" would be to not have postinsts for circular dependencies
[06:49] <LocutusOfBorg> and/or to merge the two packages into a single one
[07:05] <ricotz> LocutusOfBorg, hi, the rationale is obviously to fix its installation on armhf and therefore fixing builds of its rdepends like rustc on artful
[07:06] <ricotz> LocutusOfBorg, I don't care about a better fix, just about it to be fixed and this did the trick here
[07:07] <ricotz> e.g. this requires to be built, but fails due to this problem -- https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/rust-updates/+build/13512402
[07:44] <LocutusOfBorg> problem is that I don't get it, I think I can sponsor if you make me understand that change
[07:44] <LocutusOfBorg>  maybe just for artful, we'll see
[07:48] <ricotz> LocutusOfBorg, the problem is due to a openjdk-8 change the installation paths on armhf are different from other archs, ca-certificates-java mimics the jvm-*.cfg to work with a half-installed openjdk
[07:48] <LocutusOfBorg> ok but does that temp_jvm_cfg file gets removed after?
[07:48] <LocutusOfBorg> why is armhf different?
[07:48] <ricotz> it will be overwritten by the real one
[07:48] <LocutusOfBorg> why did this happen only on the last nmu?
[07:49] <ricotz> LocutusOfBorg, don't ask me, ask the openjdk maintainer
[07:49] <LocutusOfBorg> ok, can this change make the nmu1 reverted?
[07:49] <LocutusOfBorg> e.g. switching again to openjdk8
[07:49] <ricotz> this is not related to the nmu
[07:49] <LocutusOfBorg> ack
[07:51] <ricotz> openjdk being the cause is the reason I pinged d*oko about it
[07:51] <ricotz> I will be back in a few hours
[07:51] <LocutusOfBorg> I'm sponsoring it
[07:52] <LocutusOfBorg> with some changelog changes
[10:38] <ricotz> LocutusOfBorg, thanks
[10:41] <LocutusOfBorg> ricotz, uploaded in debian
[13:48] <soc> hey
[13:48] <soc> is there a reason why wwidgets is still compiled against Gtk2 as a backend instead of Gtk3?
[13:55] <jbicha> soc: it's a lot of work, there was some discussion on https://bugs.debian.org/790222
[14:07] <soc> jbicha: thanks, just read the messages
[14:07] <soc> so the old webkit dep is dropped, wxwidgets can use gtk3, but they haven't ported their webkit dep yet?
[14:10] <jbicha> webkit is not the problem, it's making sure that everything wxwidgets works fine with gtk3
[14:11] <soc> ah, so wxwidgets could be built with gtk3, but people aren't sure if that wouldn't introduce bugs in applications using wxwidgets?
[14:13] <soc> jbicha: another, related question: gksu still depends on Gtk2, is there a Gtk3 replacement?
[14:14] <soc> it looks like MATE ported gksu to gtk3 ..
[14:14] <jbicha> apps should use PolicyKit
[14:15] <soc> jbicha: what's the recommendation for launching apps with root privs?
[14:15] <soc> e.g. gksu synaptic?
[14:15] <jbicha> the recommendation is don't do it ;)
[14:15] <soc> I beleive synaptic wont work any other way
[14:16] <jbicha> you can try gnome-packagekit as an alternative to synaptic
[14:17] <soc> uargh, caja-gksu depends on gksu?
[14:18] <soc> just tried gnome-packagekit, that's sadly not what I want to use
[14:28] <soc> jfc: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842184
[14:28] <jbicha> Ubuntu MATE 17.10 uses caja-admin instead of caja-gksu by default
[14:30] <soc> I'm not sure caja-admin is what I want, it also pulls in a lot of dependencies
[14:35] <soc> pkexec with those fixes mentioned in the bug report works!
[14:35] <soc> just got rid of gksu
[14:35] <soc> thanks!
[14:59] <jdstrand> cyphermox: hey-- curious if you saw my comment https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1697730/comments/32
[15:10] <cyphermox> jdstrand: there was an issue with systemd to begin with, xnox was fixing this week
[15:10] <cyphermox> but otherwise, yes, networkd should always be running, just not doing anything if it doesn't have configuration to deal with (and it should not have any on a desktop)
[15:11] <cyphermox> the missing NM file sounds like an upgrade bug maybe?
[15:40] <seb128> slangasek, bdmurray, is anyone from foundations coming in that stucked updates meeting?
[15:41] <bdmurray> seb128: I'm not in NYC but could join a hangout.
[16:29] <slangasek> seb128, bdmurray: sorry, I got pulled into another meeting, how did that phased-updates discussion go?
[16:30] <bdmurray> slangasek: It was good althought I'd still like to discuss what to do with halted updates e.g. expiration
[16:30]  * slangasek nods
[17:48] <jdstrand> cyphermox: I talked to xnox, thanks
[17:53] <xnox> juliank, is there a way to check that I am not racing with in progress apt at all?
[17:54] <xnox> juliank, for example, apt-get check succeeds, even when apt-get update is in-flight
[17:54] <xnox> =/
[18:11] <kalikiana_> o/
[18:22] <xnox> jdstrand, i think with libvirt however, there is a release-regression w.r.t. .libvirt machines
[18:23] <xnox> jdstrand, .lxd is explicitely disabled.
[18:23] <xnox> jdstrand, also stgraber says enabling .lxd resolution on the host will break things; and may not be possible with lxd-as-a-snap-only.
[18:38] <cyphermox> jdstrand: cool
[18:38] <kirkland> ginggs: fixed!  build successful now, thanks ;-)
[18:52] <ginggs> kirkland: \o/
[18:54] <Odd_Bloke> Laney: Someone just pointed me at https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1530366 which refers to a packaging decision made because of having 4GB of RAM; I've just learned that we now have 8GB of RAM on the builders, so I'm wondering if the decision could be revisited?
[18:54] <Odd_Bloke> Laney: (Apologies if my "pick a random desktop person to ping" hasn't resulted in me talking to the correct person. :p)
[19:02] <jbicha> Odd_Bloke: oSoMoN is the primary chromium-browser packager in Ubuntu now
[19:05] <Odd_Bloke> oSoMoN: o/ What are your thoughts?
[19:05] <Odd_Bloke> jbicha: Thanks. :)
[19:07] <oSoMoN> Odd_Bloke, starting with chromium 61 we are now building with is_component_build=false (finally), so that issue should be fixed
[19:08] <Odd_Bloke> Faux: ^
[19:25] <Faux> :D
[20:03] <xorpad> Hi
[20:04] <xorpad> Who is in charge of the windows linux subsystem, does MS manage that or is it a FOSS project?
[20:04] <nacc> !ubuwin | xorpad
[20:04] <nacc> xorpad: afaik, it's Microsoft
[20:05] <xorpad> Oh okay
[20:05] <xorpad> I wanted to contribute to it, but MS doesn't like me
[20:06] <xorpad> well not that they don't like me but they won't hire me
[20:06] <xorpad> they liked me just fine for a job till I told them I never finished grade 5
[20:06]  * xorpad shrugs
[23:17] <ScottK> rbasak: You almost certainly want to sync the postfix I uploaded to Debian yesterday even though it's close to release.  Among other things, multi-instance should work now.