[03:07] <karstensrage> any ubuntu-backport'ers in here?
[03:26] <micahg> yes
[03:31] <karstensrage> hi micahg are you a backporter?
[03:33] <micahg> yes :)
[03:33] <karstensrage> would you be willing to backport #1561837 and #1562434
[03:34] <micahg> karstensrage: I can, but likely not tonight, is this urgent?
[03:34] <karstensrage> no not at all
[03:34] <karstensrage> but anything i can do to help or assist
[03:35] <karstensrage> they both have been very well tested on trusty and precise
[03:35] <micahg> ok, I should have some time wed evening for backports, it looks like you did all the requisite testing for that, thanks!
[03:35] <micahg> if I forget, please ping me
[03:35] <karstensrage> all my initial launchpad efforts were with ppa installs and it was realy well tested
[03:35] <karstensrage> ok sure
[03:36] <karstensrage> thank you
[03:36] <karstensrage> is it evening now btw for you?
[03:41] <micahg> yes
[03:41] <micahg> and still working :(
[04:07] <Unit193> Fun...
[05:07] <karstensrage> im sorry, maybe some soothing music ?? https://soundcloud.com/whitemorning/eddies-song
[06:43] <dholbach> good morning
[11:28] <TRJD> hello
[11:29] <TRJD> where can I request a program to be added ?
[12:16] <Rhonda> I've uploaded irssi 0.8.19 to xenial, is there something more that I would/could/should need add somewhere so it helps to get it approved?  I have PPU for irssi, and 0.8.19 is a bugfix release for 0.8.18 currently in xenial.
[14:53] <jbayfield> Hi, I'm getting started with this whole MOTU business, I wanted to give back to the community. I was looking at working on a bug (In LP it's #1442873) and I wanted to ask a few questions. When working on a bug, do you carry out the fix on all of the separate branches (ie: Precise & Trusty) or am I overlooking something? The other thing is whether I should set myself as an assignee for the packages or something el
[14:54] <dholbach> welcome jbayfield - looks like your question got cut off
[14:54] <dholbach> if the fix is important enough, you might want to backport it
[14:54] <dholbach> http://wiki.ubuntu.com/StableReleaseUpdates has some guidance on that
[14:54] <jbayfield> Hi dholbach, sorry about that. Where did the question get cut off?
[14:54] <dholbach> "whether I should set myself as an assignee for the packages or something e..."
[14:55] <jbayfield> "The other thing is whether I should set myself as an assignee for the packages or something else. Sorry for the (probably) stupid questions."
[14:55] <dholbach> just assign the one bug to you
[14:55] <dholbach> no need to sign up for all the bugs of the given package
[14:55] <dholbach> and feel free to ask more questions
[14:55] <dholbach> they weren't stupid at all
[14:55] <jbayfield> Alright.
[14:57] <jbayfield> So you work on the particular bug one distro release at a time, and then create a separate merge proposal for each affected release?
[14:57] <dholbach> yes, if the bug is important enough
[14:58] <jbayfield> And how are bugs considered "important enough"? At what point does a bug go from "not important" to "important"?
[14:59] <dholbach> have a look at the link I posted earlier
[14:59] <dholbach> it has some decision making help
[14:59] <jbayfield> ah. Okay, thanks.
[15:39] <jbayfield> Thought I'd ask - am I meant to be working on the package in "trusty" or "trusty-proposed"?
[15:40] <jbayfield> Looks like trusty - sorry about that
[16:45] <jbayfield> Hello again - when running bzr lp-propose, what should be left in the text editor that opens? A changelog?
[16:49] <jbayfield> I'm hoping this is all correct: https://code.launchpad.net/~jbayfield/ubuntu/trusty/gnome-do-plugins/bug-1442873/+merge/290337
[16:58] <jbayfield> Looking at it, I think I might have issued a merge request to the wrong place
[17:00] <jbayfield> Is it supposed to merge into trusty-proposed or trusty?
[21:43] <sney> hexchat 2.12.0-1 ftbfs on xenial. using pbuilder with variant=buildd. http://paste.debian.net/422634/ error at line 104.
[21:44] <sney> it's fine on debian testing/sid and also on wily
[22:14] <sney> bah m4/glib-gettext.m4 isn't even in my source tree, the build system installs it and then gripes that it's trying to overwrite macros. explicitly delete it via d/rules and now we build normally.
[22:44] <Unit193> That sounds just fantastic...
[22:45] <sney> it is wonderful