[00:24] <valorin> Can someone give this bug some loving? It's really annoying and I'd like to get it seen by the right people: https://bugs.launchpad.net/unity/+bug/834248
[00:25] <valorin> It's been present since Natty: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/755842
[00:25] <micahg> valorin: that's the upstream unity project, we don't deal with that here.  #ayatana would be the place to ask
[00:25] <valorin> Cool, thanks :)
[10:05] <Andy80> hi
[10:05] <Andy80> how is it called the package in Ubuntu that contains the installer?
[10:06] <jtaylor> ubiquity
[10:08] <Andy80> thanks
[11:09] <htorque> hi all! should i set an expired bug to "invalid" if it's no longer reproducible?
[11:09] <htorque> bug 805808
[11:09] <htorque> https://bugs.launchpad.net/bugs/805808
[16:26] <nigelb> pedro_: Heya!
[16:50] <bdmurray> charlie-tca: could you peek at bug 840094?
[16:51] <charlie-tca> sure
[16:59] <charlie-tca> bdmurray: it's correct, when "install xubuntu" is chosen from the menu. I haven't tried with Ubuntu, and don't know if it is the same
[17:01] <bdmurray> charlie-tca: so confirmed then?
[17:01] <charlie-tca> Yeah, confirmed
[17:46] <bkerensa> bdmurray: I need to reapply to control someday :P
[18:51] <bdmurray> yofel: around?
[18:52] <yofel> bdmurray: yes, but need to go in a minute
[18:53] <bdmurray> yofel: do you know what provides kpushbutton?
[18:53] <bdmurray> bug 815645
[18:54] <yofel> KPushButton should be from kdelibs (I think)
[18:54] <yofel> kde4libs as package
[18:54] <bdmurray> okay thanks
[19:35] <andersk_> Can someone set bug 824255 to importance High (network-manager-openconnect doesn’t work at all in oneiric)?
[19:57] <pabelanger> Afternoon... I was hoping to get some help triaging a backport request: https://bugs.launchpad.net/lucid-backports/+bug/638213
[20:00] <micahg> pabelanger: you want #ubuntu-motu for that
[20:01] <pabelanger> micahg: thank up
[20:01] <pabelanger> err
[20:01] <pabelanger> thank you
[20:01] <micahg> pabelanger: backports is run by the devs as a separate project
[21:34] <RedSingularity> bdmurray: Can i upload any corrections directly to ubuntu-bugpatterns in launchpad?
[21:35] <bdmurray> RedSingularity: Yes as a member of bug control you could however, I'd prefer you setup a merge proposal first.
[21:35] <RedSingularity> bdmurray: thats how I will go about it then.  The "propose for merging" link?
[21:36] <bdmurray> RedSingularity: yes after pushing to ~redsingularity then propose for merge
[21:36] <RedSingularity> bdmurray: I assume I will need to register a ssh key then?
[21:37] <bdmurray> RedSingularity: probably... its been a long time since I did that ;-)
[21:38] <RedSingularity> bdmurray: ok doing that now.  Thanks.
[21:43] <ashams> Hello guys, I need your opinion here
[21:43] <ashams> In this wiki page : https://wiki.ubuntu.com/Bugs/Status?highlight=%28Upstream%20bug%20task:%20a%20release%20tarball%20was%20announced%20and%20is%20publicly%20available%29
[21:44] <ashams> The phrase "Upstream bug task: a release tarball was announced and is publicly available"
[21:44] <ashams> is listed under "Fix Released"
[21:44] <ashams> I think it should be listed under "Fix Committed
[21:45] <bdmurray> ashams: then what would be Fix Released for the upstream bug task?
[21:45] <ashams> because an upstream dev has announced a tarball somewhere, doesn't mean that Ubuntu users can use it immediately
[21:46] <ashams> It's not clear to me
[21:46] <greg-g> ashams: that is why there is a difference between an upstream task and an ubuntu task
[21:46] <ashams> greg-g, would you explain a bit further
[21:46] <greg-g> You know when there is a link in LP to the upstream bug? WHen that is fixed upstream, then that task goes to "Fix Released" even if Ubuntu users never see it.
[21:47] <greg-g> There Ubuntu task is still at Triaged until the fix is uploaded to the Ubuntu servers
[21:47] <ashams> that what I'm asking for
[21:48] <greg-g> ashams: bascially, the first you you need to understand is that each bug can have multiple "tasks" Each one is for a different group. One is usually for Ubuntu (but not always), one can be for upstream, one for another distribution, etc
[21:49] <greg-g> So, each bug can have multiple states, depending on which perspective you are currently taking: Ubuntu or the upstream projects (eg: Rhythmbox)
[21:49] <greg-g> For Rhythmbox, the bug is Fix Released when they release a tarball, their work is done
[21:49] <ashams> yes
[21:49] <greg-g> for Ubuntu, it is still "Triaged" until that fix is merged into Ubuntu version
[21:50] <greg-g> does that help?
[21:51] <ashams> greg-g, yeah, but it's not uploaded to an ubuntu repo yet!
[21:51] <greg-g> ashams: right, which is why ther eare two DIFFERENT tasks
[21:52]  * micahg thought we made that clear on the status page a while back///
[21:52] <greg-g> an example might be helpful here
[21:52] <greg-g> https://bugs.edge.launchpad.net/ubuntu/+source/rhythmbox/+bug/665168
[21:53] <ashams> greg-g, thanks
[21:53] <micahg> or maybe a definition of Ubuntu task vs upstream task
[21:53] <greg-g> this is a complex one, but it has the needed parts
[21:53] <RedSingularity> bdmurray: what did you mean by "push to RedSingularity"?  How can I do that in launchpad?
[21:53] <paultag> ohai RedSingularity
[21:53] <RedSingularity> paultag: ohhh look at that!
[21:53] <RedSingularity> paultag: pm me
[21:54] <greg-g> ashams: there are two main "tasks" there, one called "Rhythmbox" and the other "Rhythmbox (Ubuntu)" (the 3 ubuntu distro names are all subtasks of the "Rhythmbox (Ubuntu)" task)
[21:54] <greg-g> see how the top one doesn't say "(Ubuntu)"? And notice how it has a link to the upstream bug report?
[21:55] <ashams> greg-g, yeah \o/
[21:55] <ashams> greg-g, I got it, Thank you
[21:55] <greg-g> So, that bug is in Rhytmbox, software not written by Ubuntu developers but by the good people in GNOME. When they fix the bug, their bug is rightly marked as Fix Released, and thus, the ......
[21:55] <greg-g> awesome
[21:55] <ashams> Oh! finally I understood
[21:55] <greg-g> you're welcome
[21:55] <ashams> greg-g, Thank you very much :D
[21:55] <greg-g> :) no worries
[21:56] <bdmurray> greg-g: thanks
[21:57] <bdmurray> RedSingularity: something like bzr push lp:~redsingularity/apport/ubuntu-bugpatterns/my-new-pattern
[21:57] <greg-g> bdmurray: no problem man :) What I haven't been contributing in actually triage work lately I like to give back in knowledge every now and then ;)
[23:29] <RedSingularity> bdmurray: I downloaded the whole bugpatterns.xml file.  Should I make the edit to that file and upload the whole thing to my branch?  I made an addition to software-properties.
[23:30] <RedSingularity> bdmurray: just not sure if I am supposed to make the edit to the whole .xml file....
[23:31] <bdmurray> RedSingularity: yes it should be to the whole xml file
[23:34] <RedSingularity> bdmurray: And do you suggest I make a comment (bzr commit -m) as to what I changed in it?
[23:40] <jtaylor> yes always document your changes, bzr commit will open a text editor for you
[23:40] <RedSingularity> jtaylor: thanks :)