[12:25] <rbasak> popey: please could you add Skuggen to ~ubuntu-wiki-editors? His LP ID is lars-tangvald.
[12:26] <rbasak> popey: also while you're there please also add ~nryeng.
[14:36] <doko> coreycb, jamespage, rbasak: could I have feedback on https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1735372 ?
[15:44] <gQuigs> seems to be going more towards a NAK for my Ubuntu Monthly Update Cadence Proposal but more comments always welcome!  https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2018-February/thread.html#17875
[15:44] <gQuigs> To me, this is also the perfect couple of months to make proposals like this. So if you want to make a different proposal, please do :)
[18:35] <popey> rbasak: sorry only just saw this. Will do.
[18:36] <rbasak> popey: np, thanks!
[19:31] <popey> rbasak: done
[20:01] <phibs> Anyone know if launchpad is having issues? I'm trying to upload my GPG key and getting timeout errors.
[20:08] <cjwatson> That's an isolated problem, though a known one
[20:08] <cjwatson> https://bugs.launchpad.net/launchpad/+bug/1753019
[20:09] <phibs> oh man
[20:09] <phibs> 2 weeks ????
[20:12] <cjwatson> wgrant: Do you think you could review https://code.launchpad.net/~cjwatson/launchpad/gpg-timeline/+merge/340554, please?  I'd like to have some hope of being able to debug this
[20:13] <cjwatson> Yeah, I mean it's probably not going to go away by itself and the current instrumentation isn't enough to debug it (or I'm missing something).
[20:13] <cjwatson> Though somewhat mysterious why it appeared in the first place.
[20:17] <phibs> cjwatson: thanks for the info
[21:18] <ahasenack> hi, who maintains gvfs in ubuntu? I'm tempted to bump this timeout[1] to see if the gvfs tests[2] become less flaky
[21:19] <ahasenack> (hm, just a sec, I should have had the urls ready)
[21:19] <ahasenack> 2. http://autopkgtest.ubuntu.com/packages/g/gvfs/bionic/ppc64el
[21:19] <ahasenack> 1. https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1713098/comments/4
[21:20] <ahasenack> and https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1713098/comments/5
[21:21] <ahasenack> https://git.gnome.org/browse/gvfs/tree/test/gvfs-test#n264 for the code
[21:22] <ahasenack> alternatively, I was wondering about using Gio.MountUnmountFlags.FORCE instead of NONE
[21:23] <ahasenack> but if there is a real bug there, FORCE might hide it
[21:26] <jbicha> ahasenack: I know that Laney has a gvfs upload in progress :)
[21:27] <ahasenack> reason I'm interested in fixing this is because my samba uploads always have a hard time with this flaky gvfs test :)
[21:28] <ahasenack> jbicha: is it in excuses already, do you know?
[21:28] <ahasenack> doesn't look like it
[21:28] <ahasenack> also not in lp yet
[21:29] <jbicha> there is a 1.36.0 upstream release, he hasn't uploaded his work to bionic yet
[21:30] <ahasenack> I checked git and that particular test hasn't changed
[21:30] <jbicha> right, I only mentioned it because you wanted to know who to talk to ;)
[21:30] <ahasenack> nor has unmount_api(), which is what times out
[21:30] <ahasenack> right
[21:31] <jbicha> I think upstream was a bit surprised we used their tests, lol
[21:31] <ahasenack> seb128 seems to have done a lot of uploads
[21:31] <ahasenack> jbicha: I'm actually hovering over "submit bug" on https://bugzilla.gnome.org/enter_bug.cgi?product=gvfs, I have it filled out alreayd
[21:33] <ahasenack> Laney: if you see this later/tomorrow/monday, would you be willing to "sneak in" a timeout change in https://git.gnome.org/browse/gvfs/tree/test/gvfs-test#n264 from 5 to, say, 10s, to see if the gvfs tests pass more frequently? (bug #1713098)
[21:37] <ahasenack> or perhaps use Gio.MountUnmountFlags.FORCE instead of NONE in that unmount_api() call
[21:37] <ahasenack> ok, have a great weekend everyone :)