[00:36] <barry> dannf, nacc, rbalint emacs25_25.1+1-3ubuntu4 uploaded, awaiting approval.  i'm eod.  crossing fingers :)
[01:42] <nacc> barry: nice one
[08:05] <rbasak> @pilot in
[08:07] <rbasak> http://pad.ubuntu.com/sponsorship-party
[08:08] <rbasak> Sponsors who can help today: please join me there.
[08:09] <Unit193> Have fun!
[08:10] <seb128> hey rbasak, I'm going to try to help a bit
[08:14] <rbasak> Thanks!
[08:15] <seb128> yw, thanks for organizing that sponsoring day
[08:32] <rbasak> cyphermox: could you help with https://code.launchpad.net/~noorez-kassam/ubuntu/trusty/initramfs-tools/fix-for-1317437/+merge/288981 please? It's a wubi/installer patch. Not sure who else might be able to help?
[08:44] <rbasak> LocutusOfBorg: is bug 1608200 still relevant please?
[08:45] <rbasak> What's our general plan for openssl at the moment? Does anyone know?
[08:47] <seb128> rbasak, https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039680.html
[08:47] <seb128> rbasak, but that merge is on the 1.0 serie so still relevent I guess
[08:57] <seb128> happyaron, is bug #1578193 something you could look at (it's in the sponsoring queue)?
[09:01] <seb128> Laney, do you have cycles to review bug #1641915 from fle_xiondotorg (it's a css change which doesn't look too big)?
[09:04] <Laney> Not immediately, but if the status is correct and it's Fix Released, then someone could check it's a straight backport?
[09:04] <rbasak> seb128: thanks
[09:05] <rbasak> xnox: could you take a look at bug 1608200 please?
[09:05] <rbasak> xnox: do you want it? Defer to next cycle? Or definitely don't want it? Just want to know wrt. the sponsorship queue.
[09:06] <seb128> Laney, gtk versions are not the same so it's always tricky to know if a straight-backport is right, but I guess it's a "if it looks like, it's fine" and don't need somebody who understand if the css makes sense then?
[09:07]  * seb128 doesn't like much SRU things he doesn't understand how they work just because they seem to work
[09:07] <seb128> but if that's what is recommended with css then alright
[09:07] <Laney> The gtk-3.0 directories in ubuntu-themes for zesty should be updated too
[09:07] <Laney> I am not saying that blind uploading is recommended
[09:08] <Laney> I'm saying that *I* don't have time *right now* to look
[09:08] <seb128> right
[09:08] <seb128> let's see, doesn't need to be soon in any case
[09:08] <seb128> that's not an important issue
[09:08] <Laney> If you want to work out how the containers work to determine whether this is right, feel free
[09:08] <Laney> that's what I would have to do anyway
[09:09] <Laney> and the SRU is waiting for a response to questions from bd_murray too
[09:10] <LocutusOfBorg> rbasak, I can handle it by myself now, nevermind and thanks
[09:11] <rbasak> LocutusOfBorg: thanks. I'll unsubscribe ~ubuntu-sponsors then? :)
[09:11] <LocutusOfBorg> sure ta
[09:12] <LocutusOfBorg> I'll merge from openssl1.0 into openssl
[09:13] <rbasak> Thanks!
[09:13]  * rbasak takes a break
[09:15] <seb128> Laney, k, thanks
[09:17] <seb128> rbasak, how do you recommend handling/marking items where somebody-who-is-probably-right-for-review got pinged (like happyaron on the n-m-strongswan one) but didn't reply/said he would look at it? would be nice to record that but it shouldn't block other reviewers to deal with it if they feel like they can get it done
[09:19] <seb128> happyaron, bug #1666912 as well
[09:20] <Laney> seb128: meh, I started looking after all
[09:20] <seb128> Laney, thanks :-)
[09:21] <Laney> easily distracted
[09:23] <sil2100> Hey! Just wanted to know: is anyone looking into the systemd upload that's blocked in -proposed due to autopkgtest regressions?
[09:25] <seb128> sil2100, you? ;-)
[09:26] <sil2100> seb128: ;) Yeah, looking at it, but didn't want to step on someone else's toes
[09:26] <seb128> sil2100, check with xnox and slangasek I guess, they are the ones most likely to be looking at that one
[09:27] <LocutusOfBorg> xnox uploaded it yesterday
[09:27] <sil2100> Eh
[09:27] <sil2100> Another upload on top
[09:41] <xnox> hm?
[09:41] <Laney> seb128: ok, so it was Needs Fixing :P
[09:43] <xnox> rbasak, we probably do want to update the 1.0.x series point release. we are not taking 1.1 series yet.
[09:43] <xnox> (somehow did not receive highlight)
[09:43] <xnox> sil2100, yeah it is stuck and there are bugs open about it. There is an unxplained hang on zesty userspace.
[09:45] <sil2100> xnox: yeah, I see it's hanging on TEST-12-ISSUE-3171 from the systemd upstream tests
[09:45] <sil2100> xnox: you remember if there's a bug for that handy?
[09:47] <xnox> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672542
[09:48] <rbasak> seb128: I've been marking those as BLOCKED with an additional list at the top with more details
[09:49] <rbasak> By BLOCKED I mean from a sponsorship process perspective, as opposed to not-ready-for-sponsorship. For the latter I've been unsubscribing ~ubuntu-sponsors with an explanation and a request to resubscribe when ready.
[09:49] <rbasak> From a sponsorship process perspective, I agree with the idea that anyone feeling confident can take it and I encourage other sponsors to look at stuff marked BLOCKED still.
[09:56] <zyga> cyphermox: I'm looking for someone that could troubleshoot a modem-manager + network-manager on 16.04 issue; DNS from mobile connection is not propagated to the system and while all the connectivity is OK name resolution always fails
[09:57] <zyga> cyphermox: ara suggested that you may be the right person
[10:04] <GunnarHj> rbasak: Hi Robie, it would be great if you could sponsor bug #1655782 during your piloting shift today.
[10:05] <rbasak> sil2100: I'm looking at bug 1562308. You had commented and the contributor has replied. I wonder if you'd be happy to sponsor now, or would you prefer that I looked at it?
[10:06] <rbasak> GunnarHj: trying to hit everything in the sponsorship queue today: https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039714.html
[10:06] <rbasak> GunnarHj: that bug is in the list :)
[10:07] <rbasak> http://pad.ubuntu.com/sponsorship-party
[10:07] <rbasak> Sponsors who can help today: please join me there.
[10:07] <rbasak> seb128: are you marking the bugs you're looking at / have looked at?
[10:10] <Unit193> flexiondotorg⋮ Uhh, for LP 1559249 you fixed it on Unity, that bug is specifically about != Unity, sooo problem very much still remains...
[10:10] <Unit193> non-Unity == Xfce, LXDE, etc, etc.
[10:23] <sil2100> rbasak: hey! Thanks for for the poke, let me take care of it in that case :)
[10:23] <rbasak> sil2100: thank you!
[10:24] <Laney> Unit193: How did this indicator work before?
[10:25] <Unit193> Laney⋮ It hasn't for a while, there's been workarounds to get it to at least show a tray icon.  However,  XDG_CURRENT_DESKTOP=Unity dropbox start  brings back the indicator in Xfce too.
[10:26] <Unit193> (Otherwise it shows a 'missing icon' in the tray, with a non-functional menu.)
[10:26] <GunnarHj> rbasak: Ok, thanks, crossing my fingers.
[10:30] <Laney> Unit193: Is that how it decides whether to show the indicator or not, or something?
[10:30] <Laney> I can imagine that setting it to Unity all the time would be a problem
[10:31] <Unit193> That's how it decides to show it in a functional state, at least.  Yeah.
[10:32] <Laney> What if you are on gnome-shell or something?
[10:32] <Unit193> No idea.  I'd be interested if you ran tint2, set that env, then started DB.
[10:33] <Laney> Dunno what that is, but that's the kind of concern I have. :)
[10:33] <Laney> Feel free to investigate and propose a new patch
[10:34] <Unit193> (Tint2 is a common panel for openbox type desktops, no indicator support.)
[10:36] <rbasak> seb128: do you have an opinion on bug 1132063 please?
[10:36] <rbasak> Not really sure what "upstream" that should probably land in first.
[10:37] <Unit193> Laney⋮ Removed the indicator plugin in Xfce, forced 'Unity', started, and it opened with the tray icon.  I have no idea why it even checks that env var.
[10:37] <Unit193> bluesabre⋮ ↑
[10:39] <rbasak> Laney: who looks after ubuntu-dev-tools? Looking for an opinion on https://code.launchpad.net/~nacc/ubuntu-dev-tools/update-vcs/+merge/308871 as it's in the queue.
[10:39] <rbasak> Is that any core dev?
[10:41] <Laney> rbasak: Yeah, but in the past it's been mainly t_umbleweed and b_drung
[10:41] <Laney> If you can't get them then I think it's OK for anyone to review, assuming they do actually review. :)
[10:41] <rbasak> tumbleweed or bdrung: please could you review https://code.launchpad.net/~nacc/ubuntu-dev-tools/update-vcs/+merge/308871 ? It's been languishing for a while.
[10:42] <Laney> It's uploaded to Debian and then synced, so ping your friendly local DD for an upload when you want one
[10:42] <rbasak> IMHO, if tumbleweed or bdrung have no opinion, perhaps nacc could send it to ubuntu-devel@ since it would change the flow a bit. And if no objection, then we should just upload.
[10:45] <rbasak> tyhicks or mdeslaur: in trying to get the sponsorship queue to zero, do you have an opinion on removing bug 1639372 from the security sponsorship queue given that there's currently nothing to sponsor?
[11:01] <mdeslaur> rbasak: one sec, looking
[11:02] <mdeslaur> rbasak: unsubscribed, thanks
[11:03] <rbasak> Thank you!
[11:32] <rbasak> http://pad.ubuntu.com/sponsorship-party
[11:32] <rbasak> Sponsors who can help today: please join me there.
[11:56] <seb128> Laney, thanks for the theme review!
[11:57] <Laney> np!
[11:57] <seb128> rbasak, sorry I was at lunch, agreed on what you said about "blocked" items that can still be reviewed and I had a look at that u-c-c issue/L_aney had a go at it in the past as well, it's a bit tricky because I don't have hardware to trigger the problem
[11:57] <seb128> I can try to poke a bit upstream to see if they changed something though and if the change should be forwarded there
[11:58] <seb128> oh, and yeah I'm going to edit the pag
[11:58] <seb128> pad
[11:58] <rbasak> OK. Thanks!
[11:59] <rbasak> seb128: FWIW, for that sort of thing I think it might be fine to say "no hardware, get it upstream first". IMHO the only thing there then is to set expecations - to make it clear what the next steps should be, and to take it out of sponsorship queue explicitly.
[11:59] <seb128> right
[13:20] <tinoco> rbasak: could u publish LP: #1317491 for me, pls ?
[13:32] <rbasak> tinoco: the pending-sru still flags bug 1483071 and bug 1511830. I suspect they're no longer relevant, but could you summarise what's going on there please?
[13:32] <tinoco> rbasak: sure, an end user told me that one snapshot method was broken in Trusty.
[13:32] <cpaelzer> rbasak: those two are dropped because nobody verified them
[13:33] <cpaelzer> rbasak: dropped in like november 2016
[13:33] <tinoco> rbasak: I reviewed it, described the method and why it was broken and saw that 2 commits (for the affected file) after Trusty release, this "feature" was "blocked" from "virsh".
[13:33] <tinoco> rbasak: So feasible SRU was to block the feature instead of looping endlessly.
[13:33] <cpaelzer> tinoco: you are describing the issue you fixed, I'm not 100% that was what he asked - was it rbasak?
[13:34] <rbasak> Right cpaelzer. But I think you got it, thanks :)
[13:34] <tinoco> rbasak: is this enough ?
[13:35] <rbasak> I think so. Let me just check a diff of 17->20 to make sure that my understanding of what is happening is correct.
[13:35] <tinoco> rbasak: tku
[13:35] <rbasak> Hmm. libvirt has never been imported before? :-/
[13:36] <cpaelzer> rbasak: it had a good git based dev before the importer
[13:36] <cpaelzer> rbasak:  we still use that
[13:36] <cpaelzer> rbasak: should be in the VCS I hope
[13:36] <cpaelzer> d/control tag
[13:36] <cpaelzer> rbasak: let me know if not
[13:36] <rbasak> cpaelzer: understood. The importer is still useful to match against the actual archive though.
[13:36] <cpaelzer> well maybe not on trusty
[13:36] <cpaelzer> rbasak: oh yeah, for sure
[13:36] <cpaelzer> rbasak: but due to working on the repo I never cared/checked if it was imported
[13:37] <rbasak> Yeah that makes sense :)
[14:02] <rbasak> http://pad.ubuntu.com/sponsorship-party
[14:02] <rbasak> Sponsors who can help today: please join me there.
[14:09] <mterry> @pilot in
[14:26] <cyphermox> zyga: please file a bug, that way happyaron, who is now maintaining NetworkManager, can look too
[14:41] <bdmurray> xnox: What's the status on bug 1651623?
[14:47] <xnox> *sigh*
[15:37] <seb128> tyhicks, hey, could you unsubscribe the security sponsors from bug #1662164 so it drops from the sponsoring queue until the submitter does the changes you requested at least?
[15:42] <tyhicks> seb128: hi - done!
[15:43] <seb128> tyhicks, thanks!
[15:46] <GunnarHj> mterry: Thanks for sponsoring xkeyboard-config!
[15:47] <mterry> GunnarHj: you're welcome!  Would be nice to squeeze it into zesty
[15:49] <GunnarHj> mterry: Yeah, it's FFe'ed so probably it will make it.
[16:04] <sil2100> seb128: hey! Just out of curiosity - are you looking getting updated zesty language-packs?
[16:04] <sil2100> *looking into
[17:13] <seb128> sil2100, yes, we just got a first launchpad export a few days ago, I started looked that generating the deb from it today but it's probably going to be continued tomorrow now since I got sidetracked helping on the sponsoring
[17:27] <sil2100> seb128: ok, great, good to know! If you'd need any help then just give me a ping, I have limited experience (touch packs only) but yeah
[17:27] <sil2100> seb128: thanks!
[17:27] <seb128> sil2100, k, thanks, and yw!
[17:28] <dobey> sil2100: can we get updated -touch langpacks for xenial-overlay?
[17:32] <rbasak> @pilot out
[17:32] <rbasak> I'm EOD now. Thanks mterry and seb128!
[17:32] <rbasak> seb128: I'd call "unsubscribed sponsors" DONE FWIW.
[17:32] <seb128> rbasak, thanks to you for leading the effort!
[17:32] <mterry> rbasak: :)  I'll keep working a bit, but I don't think we'll get to 0  :)
[17:33] <seb128> rbasak, k, fair enough
[17:33] <mterry> rbasak: and yeah thanks for spearheading it
[17:33] <rbasak> mterry: no. But I think we're making a bit dent. Thanks!
[17:33] <seb128> yeah, I might do a bit more tonight
[17:33] <seb128> and maybe some u.s based people join still as well
[17:33] <rbasak> We could do this another couple of times and we'd clear it I reckon.
[17:39] <nacc> @pilot in
[17:39] <nacc> are we coordinating somewhere?
[17:43] <mterry> nacc: http://pad.ubuntu.com/sponsorship-party
[17:44] <nacc> mterry: thanks
[17:58] <Unit193> cyphermox⋮ Re: 1673625.  The other has more logs, sure, but I'm not really talking about upgrade errors, I'm simply trying to say that the override file itself should be in nplan, it only makes sense to have it there since it's only useful there.
[18:09] <cyphermox> Unit193: I understand that, but I disagree, this belongs in NM and NM is supposed to make sure that it doesn't break things (which is why there is a bug for upgrade). nplan is in standard and on all systems, whereas NM doesn't normally exist on servers. The intent here is to make sure that NM behaves the right way given that nplan is on all systems, and that it does so following whether netplan is in use or not
[18:27] <cyphermox> Unit193: so; I've deduped it and commented/updated the bug to make things clearer. I'm sorry I didn't quite handle this very well; hopefully it makes more sense now.
[19:38] <Unit193> cyphermox⋮ Ok, thanks.  That's some reasoning at least, and thanks very much for putting it in the bug report!  It's more clear, I just don't happen to agree.
[20:07] <mterry> @sponsor out
[20:07] <udevbot> Error: "sponsor" is not a valid command.
[20:07] <mterry> @pilot out
[21:51] <nacc> coreycb: re: LP: #1664203 -- is there actually something to sponsor there?
[23:04] <bdrung> rbasak, I looked at https://code.launchpad.net/~nacc/ubuntu-dev-tools/update-vcs/+merge/308871 and commented it
[23:06] <nacc> bdrung: thanks!
[23:06] <bdrung> nacc, besides my comments, having this functionality in update-maintainers seems useful to me
[23:07] <nacc> bdrung: yeah, we use it relatively commonly (but by hand) in our server team merge flow
[23:07] <bdrung> nacc, you get bonus points for test cases ;)
[23:07] <nacc> bdrung: being able to script it would be a win for us :)
[23:07] <nacc> bdrung: good call! :)
[23:08] <bdrung> tests should be relatively easy, but i do not remember if we have any yet
[23:08] <bdrung> this python code is quite old and my python foo enhanced since then
[23:10] <nacc> bdrung: i see a tests :)
[23:11] <bdrung> and flake8 and pylint checks?
[23:11] <nacc> err, test-data and ubuntutools/test/
[23:11] <nacc> there is a test_pylint
[23:11] <nacc> but it seems like we should run those during pkg build
[23:22] <nacc> @pilot out
[23:27] <rbasak> smb: is https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1648143/comments/26 correct? Wrong bug?
[23:28] <rbasak> bdrung: thanks!
[23:28] <stgraber> yeah, looked odd to me to, I don't see the link between that security fix and this bug
[23:29] <rbasak> Let's reopen for now. If it's wrong, smb can re-close it perhaps?
[23:29] <sbeattie> rbasak, stgraber: yeah, they all need to be re-opened.