[09:06] <jamespage> xnox: morning
[09:07] <jamespage> xnox: quick q for you - which boost version are we going to default for artful?
[10:43] <jamespage> if there is an archive-admin around - please could vine be promoted to main (approved under bug 1688091)
[10:43] <jamespage> that will help with unblocking the proposed migration of openstack pike1 updates before I start on pike2 this week
[10:59] <ogra> since when is this channel +r ? thats quite annoying
[11:12] <cjwatson> ogra_: spammers ruin things for everyone, probably
[11:13] <ogra_> yeah
[11:13] <cjwatson> we had a *lot* of junk over the last few days
[11:23] <ogra_> i noticed and i guess i'll live with +r ... just annoying
[11:35] <mdeslaur> is there a way to make hexchat wait until after identification before trying to join?
[11:37] <Laney> you can authenticate during connection
[11:37] <Laney> https://freenode.net/kb/answer/hexchat
[11:51] <mdeslaur> Laney: oh! cool, thanks
[11:54] <mdeslaur> Laney: that worked, thanks
[11:54] <Laney> mdeslaur: ♥
[13:06] <juliank> OK, so I opened both bug 1694702 and bug 1694697 for tracking the issue slangasek reported yesterday. We can SRU both, but validation might get a bit complicated because the patch for apt also works around the off-by-one problem in python-apt
[13:08] <juliank> That is, you'll have to test python-apt without the coming proposed apt, otherwise you don't see the issue at all
[13:12] <mdeslaur> cpaelzer: hi! think you could merge strongswan to get the security fixes?
[13:32] <cpaelzer> mdeslaur: hi did they update Debian - let me check
[13:34] <cpaelzer> mdeslaur: you don't mean the 5.5.2-1 in experimental but the 5.5.1-4 in unstable right?
[13:34] <mdeslaur> right, -4 in unstable has the security fixes
[13:39] <cpaelzer> yeah I can look at it mdeslaur
[13:39] <mdeslaur> cpaelzer: thanks!
[13:39] <cpaelzer> next time when libvirt is compiling an hour ...
[13:40] <Laney> sword fight time
[13:42] <cpaelzer> Laney: https://xkcd.com/303/ ?
[13:43]  * Laney nod
[13:43] <Laney> :)
[13:47] <Laney> infinity: Stealing the debhelper/exp merge
[14:10] <cpaelzer> mdeslaur: the cve patches are not the nicest
[14:11] <cpaelzer> mdeslaur: would this cause you any headache http://paste.ubuntu.com/24726825/ ?
[14:11] <cpaelzer> I mean buildpkg is happy, yet I wanted to ask you at least
[14:13] <mdeslaur> I don't mind if that's how they are in the debian package
[14:13] <mdeslaur> cpaelzer: ^
[16:23] <bmw> rbasak: I just wanted to check on the status of certbot packages
[16:23] <bmw> do you know if Peter submitted the documents you need?
[16:24] <rbasak> bmw: o/
[16:24] <rbasak> bmw: not that I know about
[16:24] <bmw> hmm okay
[16:24] <bmw> he'll be somewhat MIA for the next week or two, but I'll get a hold of him and ask him to do it or write it up myself
[16:24] <rbasak> bmw: I've started pushing SRU branches to alioth. So far I've done python-acme for all three stable Ubuntu releases, and the special python-letsencrypt to cover the rename in Xenial.
[16:24] <rbasak> bmw: thanks!
[16:27] <bmw> is the document from Peter a blocker for pushing the SRU packages live or just necessary for updates in the future?
[16:32] <rbasak> Good question.
[16:32] <rbasak> It's not technically a blocker, but it will duplicate work I think - because we'd have to lay out our justifications twice.
[16:33] <bmw> ah that makes sense
[16:34] <bmw> we'll get it written up to avoid duplicating work
[16:34] <bmw> the other thing from my end is finding someone to build the packages in the future
[16:34] <bmw> I've gotten some interest from coworkers, but no commitment yet
[16:35] <bmw> I'll keep badgering people and I'm sure we'll find someone to do it
[16:44] <rbasak> Thanks!
[17:25] <infinity> Laney: Given the changelog, I didn't have a lot of confidence in debhelper/experimental...
[18:08] <nacc> rbasak: hrm, something is wrong with the import of python-acme that you pushed, i think
[18:10] <nacc> rbasak: i think true for src:gosa as well -- it's like you weren't current to launchpad
[18:30] <nacc> rbasak: we should sync up on this, as something is funky. your gosa import is really weird. the tags exist, but the branches weren't moved for later versions
[18:35] <nacc> rbasak: yeah, python-acme is fubar. It would appear you pushed / committed the queue syncs? e.g. https://git.launchpad.net/~racb/ubuntu/+source/python-acme/commit/?id=2de942f7a60d7a04900eedacbf68d8e736fd9b1a
[18:35] <nacc> bah, nm, that's me looking in the wrong repo!
[18:36] <nacc> https://git.launchpad.net/~usd-import-team/ubuntu/+source/python-acme/commit/?h=debian/experimental&id=cc8febe8e4f44e9d582fed976cace9c1d26c8358 seems odd, though, there's no tag for that version
[18:37] <nacc> which then breaks the patches-applied import
[19:36] <rbasak> nacc: got to run, but if it helps, http://paste.ubuntu.com/24729486/ is my gosa tag list in my local tree from the importer run.
[21:11] <jdstrand> tyhicks: hey, curious on your thoughts about click-apparmor and apparmor-easyprof-ubuntu in artful
[21:11] <jdstrand> tyhicks: they used to be in main and have been demoted to universe this cycle
[21:12] <jdstrand> tyhicks: the security team is listed as the maintainers. the only thing keeping them is a recommends from click. my preference would be to remove them or somehow get them off our plate
[21:13] <cjwatson> it may make sense to remove click
[21:13] <jdstrand> tyhicks: so removal or move to another owner. motu?
[21:15] <jbicha> why would anyone use click in 18.04?
[21:15] <tyhicks> jdstrand: good question - I'd think that click could go away
[21:15] <jdstrand> jbicha: precisely. I just don't know if someone is going to do a unity8 flavor or something
[21:16] <jbicha> is click needed for unity8?
[21:16] <jdstrand> aiui, there is an open click store and other projects (free phone?) are using it. but I don't know if they're built from the archive
[21:16] <jdstrand> jbicha: not strictly. but that's where the apps are
[21:17] <jdstrand> I mean, I'm fine with removing click and click-apparmor. they aren't used in Ubuntu by anything I know of and there is nothing saying that a flavor couldn't bring them back
[21:17] <jbicha> I believe unity8 stuff is being removed from Ubuntu, but they could be reintroduced if someone steps up to maintain them
[21:18] <tyhicks> that'd be my preference
[21:18] <tyhicks> remove it and then allow anyone else to jump in and restore the package
[21:18] <jdstrand> I just know that if it is in the archive, regardless of universe or main, we'll feel obligated to fix issues, but that isn't the best use of our time
[21:19] <tyhicks> agreed
[21:19] <jdstrand> cjwatson: what are your thoughts on that? ^
[21:20] <cjwatson> I agree
[21:20] <cjwatson> I guess I'd say that it can be removed together with unity8, if and when it is removed
[21:21] <jdstrand> that probably makes the most sense. I'll talk to the desktop team about their plans
[21:23] <jdstrand> tyhicks: in the meantime, I'm going to adjust LP to show the upstream projects are not active and break the link from the ubuntu project to the upstream
[21:23] <tyhicks> jdstrand: good idea
[21:24] <tyhicks> jdstrand: think we should do an upload to update the Maintainer? IMO, that's not needed unless someone else takes over maintenance and/or the package is to remain in the archive for 17.10
[21:25] <jdstrand> tyhicks: I could probably do a quick upload. I'll talk to the desktop team and get more details
[21:27] <tyhicks> thanks
[23:02] <nacc> rbasak: ah interesting -- so i was able to import gosa, but the empty directory fix makes `git ubuntu merge` not work -- let's sync up on it tmrw
[23:15] <nacc> rbasak: also, could you peek at LP: #1693954  -- is /etc/mysql/debian.cnf a generated file normally? I can't tell if it's a configuration issue (apt-file doesn't indicate it's owned by the package)