[03:28] <kees> uhm, http://changelogs.ubuntu.com/meta-release-lts <- shouldn't xenial be listed here?
[03:30] <Unit193> Likely when it hits its first point release, yes.
[03:30] <kees> oh right, I always forget that
[07:29] <Unit193> slangasek: You missed #824943 with your upload to NEW.
[07:29] <Unit193> *May have, don't remember all the different parts. >_>
[09:49] <mcphail> mhall119: wrt http://mhall119.com/2016/03/help-make-gnome-software-beautiful/ , are you simply looking for new icons (and edits to the upstream .desktop files) or full, new appdata.xml files?
[11:25] <elbrus> infinity: any luck on looking into the fpc with glibc on powerpc issue yet (LP 1562480)
[11:26] <elbrus> I am getting multiple bug reports because we miss a feature from 3.0.0+dfsg-3
[11:26] <elbrus> s/feature/bug fix/
[14:18] <halvors1> Hi. Systemd version 230 came out yesterday with a lot of bug fixes, will you guys update systemd to this for Ubuntu 16.04?
[14:21] <rbasak> halvors1: see https://wiki.ubuntu.com/StableReleaseUpdates. Seems unlikely to me that a new systemd upstream version would be suitable, but I don't know the details.
[14:31] <halvors1> rbasak: Hmm. Because i'm hitting a really annoying bug with 229 :(
[14:32] <halvors1> But at least it should be updated for yakkety ;)
[14:33] <rbasak> halvors1: I'm sure Yakkety will be updated as appropriate. If there's a bug, please ensure a bug exists for it in Launchpad. Bugs in 16.04 can be fixed, just not necessarily by updating wholesale to a new upstream version.
[14:44] <mhall119> mcphail: bad icons accounted for the bulk of the bad/missing appstream data, so we focused on that
[14:45] <mhall119> but if you want to provide more, that would certainly be welcome :)
[14:46] <mcphail> mhall119: :) - so a proper icon is OK with a tweaked .desktop file? Would probably be a bit much to expect upstream to package a metafile as well...
[16:08] <teward> I"m seeing a ton of hook errors in Apport bugs as of late, and it prevents my apport hooks in nginx from running.  The traceback on the bugs points back to the 'general' apport hooks for any bug, who do I report this to for fixing?
[16:08] <teward> this is in Xenial, and with apport hooks failing completely, there's no way to do debugging on those bugs (this extends to Yakkety, I believe, as well)
[16:22] <rbasak> teward: a bug against apport might be appropriate there maybe? Do you have an example?
[16:50] <halvors> rbasak: I did. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1584491
[16:51] <halvors> ifupdown should really be replaced with systemd-networkd soon :)
[16:51] <teward> rbasak: pick any of the latest 4 nginx bugs
[16:51]  * teward grabs numbers
[16:53] <teward> rbasak: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1581864 actually is a prime example, any foreign charsets (i.e. not english) choke the script, in rare cases the nginx hooks run, in others, it just fails.
[16:54] <teward> rbasak: this is not "new" but it's new in so much that it's breaking *my* hooks when it tries to run
[16:54] <teward> rbasak: it also makes it headachey to triage - i have to rely on the users to provide their data :/
[16:55] <teward> rbasak: thankfully that person *attached* their data from the error logs that the hooks pull in
[16:55] <teward> but there's other closed ones which are similar
[16:55] <teward> and it's not confined to Xenial
[16:55] <teward> perhaps the hooks need updated for international scripts?
[16:58] <teward> hmm, maybe not that one
[16:58] <teward> rbasak: it's probably buried under Expired
[16:58] <teward> but let me grab the hook errors
[16:58] <teward> here's one with International: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1584468
[16:58] <teward> and it looks like this is a more general error too - https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1582954
[16:58] <teward> both have hook errors
[16:58] <teward> let me make a test bug...
[17:04] <rbasak> teward: I think that's a bug that needs filing against apport.
[17:04] <teward> ack
[17:04] <rbasak> halvors: thank you for filing that.
[17:12] <halvors> rbasak: It's probatly easy to do a backport of the commit that fixed that issue to 229 if that is desirable instead of upgrading the whole systemd package to 230 :)
[17:28] <rbasak> halvors: if you're volunteering to do the backport, it'd be helpful to make that clear in the bug :)
[20:10] <Unit193> LocutusOfBorg: Did you see PM a day or so ago?
[20:10] <LocutusOfBorg> looking at it right now
[20:10] <LocutusOfBorg> no anyway
[20:11] <LocutusOfBorg> if it is about sponsoring, I'll look at it
[20:12] <Unit193> \o/
[20:13] <LocutusOfBorg> I'm gonna do it now
[20:13] <LocutusOfBorg> making VCS-git in https
[20:13] <Unit193> Eh...  I kind of intentionally left that one, but oh well.
[20:14] <LocutusOfBorg> ok then
[20:16] <LocutusOfBorg> done
[20:18] <LocutusOfBorg> and pushed
[20:20] <LocutusOfBorg> Unit193, can I sync it on ubuntu when it gets available?
[20:48] <Unit193> LocutusOfBorg: Thanks.  And yeah, I was going to do that.