[00:17] <owh> Hiya, just lodged Bug #201237 for tasksel, but it applies to hardy alpha 6. How do I tell LP that?
[00:17] <ubotwo> Launchpad bug 201237 in tasksel "tasksel does not work if installed on a machine with no network" [Undecided,New] https://launchpad.net/bugs/201237
[00:19] <owh> One suggestion made was to lodge a new bug at: https://bugs.launchpad.net/ubuntu/hardy/+bugs, but that seems to imply that I need to close this bug and do it again. That doesn't make sense to me.
[00:19] <bdmurray> owh: A bug is assumed to apply to the latest version of the package which would be Hardy.
[00:19] <owh> bdmurray: Except that it doesn't show up in the hardy bug list, so it is unlikely to be dealt with prior to release.
[00:20] <owh> Or am I mistaken?
[00:21] <bdmurray> You could nominate it for the Hardy list then.  You can do this on the left hand side of the bug remote in the pink Actions menu.
[00:23] <owh> bdmurray: Hmm, well, LP shows it as nominated, but it still doesn't show in https://bugs.launchpad.net/ubuntu/hardy/+bugs - am I missing something?
[00:23] <bdmurray> owh: nominations need to be approved by an Ubuntu driver member
[00:24] <bdmurray> otherwise the Hardy list would be much longer. ;)
[00:24] <owh> bdmurray: Fair point. Well, in that case, I've done my part I think - thanks for the help.
[00:25] <bdmurray> owh: thank you for submitting the bug
[00:26] <owh> bdmurray: That's the easy part :) - I try to hold my end up with fixing and patching too :)
[02:10] <Pici> Hm.  Where would a bug regarding the gnome multimedia keys go? It doesnt appear to be specific to one application.
[02:10] <james_w> Pici: what's the problem?
[02:12] <Pici> james_w: The gnome multimedia keybindings don't appear to be working in Hardy (at least track forward and back). Exaile, Sonata (i think it supports it) and decible-audio-player are not working...
[02:12] <Pici> Although now someone says that quod-libet does (/me looks)
[02:13] <james_w> Pici: can you try rhythmbox?
[02:13] <Pici> james_w: sure, moment
[02:13] <james_w> Pici: also, are these special keys on your keyboard?
[02:14] <Pici> james_w: They are, and they appear to be working in Rhythmbox
[02:14] <james_w> I guess that they are bugs in the other apps then. If rhythmbox picks them up then they are working ok.
[02:14] <Pici> james_w: roger that
[02:15] <james_w> however if they are relying on something else to relay the messages then that may be at fault.
[02:16] <Pici> I'm going to do some looking around
[02:16] <RAOF> Pici: The problem is that there's a new mmkeys API.
[02:16] <Pici> RAOF: Aha.
[02:16] <RAOF> Pici: Rhythmbox will (should) work, everything else needs updating.
[02:17] <Pici> RAOF: Is it necessary to log a bug for each of them? or how does something like this work?
[02:18] <RAOF> Pici: What you'd want to do is to file a bug against one of them, and then go "also affects" all the others.
[02:18] <RAOF> It's essentially one-bug-per-package, but with the same bug number.
[02:20] <Pici> RAOF: Do you happen to know what version of python-mmkeys the api was changed in?
[02:20] <RAOF> Um, it's probably not python-mmkeys; it's gnome-settings-daemon which publishes the multi-media key info.
[02:21] <Pici> hmm
[02:21] <Pici> Okay
[02:22] <RAOF> So gnome-settings-daemon changed how it publishes the MMKeys information (again), and the non-Rhythmbox apps aren't looking in the right place.
[02:57] <jjesse> bdmurray: you around?
[03:01] <jjesse> need some help triaging bug #35605, as the bug references Mandrivia
[03:01] <ubotwo> Launchpad bug 35605 in kdeartwork "kpartsaver segfaults" [Medium,Fix released] https://launchpad.net/bugs/35605
[03:02] <jjesse> the bug is  marked as fix released in kdeartwork, do i assume its been fixed in mandrivia?
[03:02] <jjesse> and mark it the same?
[03:14] <bdmurray> jjesse: looking
[03:16] <bdmurray> I'd mark it Invalid as Mandriva doesn't use Launchpad, there isn't a remote Mandriva bug for the bug watch that we know of and because the Mandiva affects was probably added wrongly.
[03:25] <techno_freak> bdmurray, a general question. when a bug filed on a project which falls under a loco team in launch pad, who can unsubscribe the team from the bug?
[03:26] <techno_freak> i meant, the project was included the team's project list (which was again not known how)
[03:27] <bdmurray> Team admins can unsubscribe the team from a bug report.  Do you have a link for the issue you are talking about?
[03:27] <techno_freak> bdmurray, yes, one minute.
[03:28] <techno_freak> bdmurray, bug #183958 someone marked it as security issue thinking that it would stop mails from that bug.
[03:28] <ubotwo> techno_freak: Bug 183958 on http://launchpad.net/bugs/183958 is private
[03:29] <techno_freak> and as private too
[03:31] <bdmurray> I can't see that bug report, but as the Ubuntu Bugs team owner I have the ability to unsubscribe the team from bug reports like 35605 that was mentioned earlier.  Ubuntu Bugs shows up as a "direct" subscriber and when I click on Subscribe/Unsubscribe I see "Unsubscribe Ubuntu Bugs from this bug"
[03:32] <bdmurray> Does that help some?
[03:32] <techno_freak> bdmurray, i was able to see it, but when i was seeking help from people here some one made it a security issue after which it is not viewable at all
[03:33] <techno_freak> bdmurray, yes. i understood what you said. :)
[03:33] <bdmurray> jdstrand: can you see it?
[03:36] <bdmurray> techno_freak: what package was the bug about?
[03:36] <techno_freak> bdmurray, BBox if i remember it right
[03:40] <yuriy> hmm how do i add an upstream bug watch? looks like the interface has changed since i last did this
[03:40] <yuriy> i did also affects project but there isn't a place to put in a bug
[03:41] <bdmurray> +Project if it is far upstream
[03:41] <bdmurray> yuriy: for what package?
[03:41] <yuriy> bdmurray: bug 201281
[03:41]  * bdmurray waits for it
[03:42] <yuriy> heh, katapult, upstream bug here: http://bugs.kde.org/show_bug.cgi?id=140591
[03:42] <techno_freak> bug #201281
[03:42] <bdmurray> I was hoping ubotu or ubotwo would say something
[03:42] <tritium> The bots are having issues today, bdmurray
[03:42]  * yuriy notes taht ubotwo has quit^^
[03:43] <techno_freak> ubotu sometimes becomes too slow to respond, think it is overloaded too much
[03:44] <yuriy> in this case it's not here at all though
[03:44] <bdmurray> yuriy: your bug is really weird
[03:45] <bdmurray> So katapult doesn't use Launchpad for bugs?
[03:46] <yuriy> well it's a package in ubuntu, and it's a component of kde and has bugs on bugs.kde.org
[03:47] <bdmurray> Well, somebody setup a Katapult project in Launchpad and that is why this is behaving differently.
[03:47] <bdmurray> https://launchpad.net/katapult/
[03:47] <bdmurray> The Status shows them using Launchpad for bugs
[03:48]  * yuriy pings said someone to find out
[03:48] <bdmurray> The "driver" of the project are the katapult-dev team and there you can find the team owner.
[03:49] <yuriy> mhmm, i did
[03:52] <bdmurray> Well, so that's why you can't add a link to the kde bug report.
[06:17] <kkubasik> hey, can someone take a look at https://bugs.edge.launchpad.net/ubuntu/+source/firefox-3.0/+bug/193108
[06:17] <kkubasik> its been marked a low priority
[06:17] <kkubasik> but it makes firefox almost unusable for several users
[06:17] <kkubasik> https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/193108
[06:17] <kkubasik> sorry =/
[07:23] <savvas> does anyone know the package I should mention about this bug: http://pastebin.ca/raw/939393
[07:24] <savvas> I get such errors while transferring to/from a mobile phone using usb
[07:25] <savvas> (whose free space is about 100mb)
[07:45] <ogra> savvas,
[07:45] <ogra> [69854.011266]  sde: sde1
[07:45] <ogra> [69854.027239]  sde: p1 exceeds device capacity
[07:45] <ogra> your partition table is broken on the device
[07:46] <savvas> you mean the phone card is the problem?
[07:47] <savvas> hm give me a sec, i'll back my files and format it
[07:48] <ogra> write a proper partition table to it :)
[07:48] <ogra> cfdisk is your friend
[07:49] <savvas> FATAL ERROR: Bad primary partition 0: Partition ends after end-of-disk
[07:49] <savvas> heh
[07:49] <techno_freak> ah
[07:50] <savvas> ogra: it's a memory stick pro duo on sony ericsson w810i, think it matters?
[07:52] <ogra> no idea, i just saw the errormessage in your paste :)
[07:53] <savvas> i'll try format it with their software in the phone, i'll try it in about 20 minutes
[07:54] <savvas> remind me to hug you unofficially :P
[08:15] <savvas> ogra: do you happen what type should i use? I just formatted using the phone software and it's happening again :\
[08:17] <savvas> hm it says FAT16
[08:32] <savvas> ogra: every time I disconnect & reconnect the usb to my mobile phone, it says unallocated disk space in gparted
[08:32] <savvas> the weird thing is that the mobile phone internal memory seems ok
[11:03] <jdstrand> bdmurray: I don't have access to that bug either (which is a little odd actually)
[11:09] <techno_freak> jdstrand, it was marked as a security issue by some one thinking it would stop the bug mails being sent to all people in the team. even the team admin is not able to view it
[11:11] <pedro_> good morning!
[11:15] <jdstrand> techno_freak, bdmurray: sounds like an LP issue if noone can se it
[11:23] <techno_freak> jdstrand, any idea whom i should bug to get it solved? :)
[11:31] <pochu> jwendell: hi, I'm forwarding the change at bug 191716 to the debian maintainer, but he's asking me whether there's a backtrace of one somewhere... do you have one handy, or a way to trigger a crash due to that change?
[11:38] <jwendell> where's bugbot :'(
[11:38] <jwendell> pochu, link, plz
[11:55] <pochu> jwendell: http://launchpad.net/bugs/191716
[11:55] <pochu> jwendell: ubotu is lagging these days :)
[11:56] <jwendell> pochu, ah, anjuta... I've just replied there
[12:00] <pochu> jwendell: oh, I see. thank you :)
[12:01] <jdstrand> techno_freak: how about joing #launchpad and asking there?
[12:01] <jdstrand> (sorry for the delay, had to get my son ready for school)
[12:03] <Pici> Ubotu is not well these days... been trying to get in contact with Seveas to whip it back into shape, but no-go.  I'll see if I can get one of the backup bots in here.
[12:03] <techno_freak> jdstrand, sure, thanks
[12:03] <jdstrand> np
[12:36] <Iulian> Hi
[13:07] <primes2h> Is there someone in here having a laptop with ati chipset?
[13:09] <primes2h> bad news.
[13:09] <primes2h> 'ati' (radeon) driver is going to be blacklisted from compiz.
[13:10] <primes2h> So all people happily using compiz with this driver (open source) on a laptop won't be able to have compiz by default.
[13:10] <Pici> primes2h: link?
[13:11] <primes2h> bug #197135
[13:12] <primes2h> I opened a bug to whitelist my card (because I never had problem with compiz)
[13:12] <primes2h> Have a look #201330
[13:13] <Pici> I see that Travis Watkins (Amaranth) is looking at it, I trust he'll do the right thing.
[13:14] <primes2h> Probably there are other people that don't have problems with 'ati' driver and compiz, but it should be better to let it know.
[13:15] <primes2h> This choice (to blacklist completely 'ati' driver) would affect a lot of people...
[13:17] <primes2h> The real problem is that ati proprietary drivers don't support all chipset.
[13:19] <primes2h> so who (like me) has these chipset won't be able to use compiz by default.
[13:20] <primes2h> Even if it has been working very well until now.
[15:03] <MagicFab> hey
[15:03] <MagicFab> is there a way to make a bug " depend"  on another in LP ?
[15:07] <pedro_> something like bug 95419 ?
[15:07] <ubotwo> Launchpad bug 95419 in malone "Record dependencies between bugs" [Medium,Confirmed] https://launchpad.net/bugs/95419
[16:24] <qense> hello!
[16:25] <pedro_> hey hey
[16:33] <qense> got to go, bye
[17:25] <afflux> morning
[17:25] <bdmurray> Hello!
[17:25] <afflux> I came across another bug reported via apport but invisible for ubuntu-bugcontrol :(
[17:26] <afflux> I asked for the report in bug 183685, the new bug is bug 201071
[17:26] <ubotwo> Launchpad bug 183685 in compiz-fusion-plugins-main "compiz.real crashed with SIGSEGV" [Medium,Fix released] https://launchpad.net/bugs/183685
[17:26] <ubotwo> afflux: Bug 201071 on http://launchpad.net/bugs/201071 is private
[17:29] <bdmurray> afflux: you could ask Nikolai to subscribe to the bug to figure out what is going on
[17:31] <afflux> bdmurray: yes, but exactly the same happend some days ago with bug 199911, which was requested from me in bug 190428
[17:31] <ubotwo> Launchpad bug 199911 in emerald "emerald crashed with SIGSEGV in gdk_gc_new_with_values() (dup-of: 139877)" [Undecided,Confirmed] https://launchpad.net/bugs/199911
[17:31] <ubotwo> Launchpad bug 139877 in emerald "emerald crashed with SIGSEGV in gdk_gc_new_with_values()" [Unknown,Confirmed] https://launchpad.net/bugs/139877
[17:31] <ubotwo> Launchpad bug 190428 in emerald "emerald crashed on "alt-tab" windows switching" [Medium,Incomplete] https://launchpad.net/bugs/190428
[17:33] <qense> hello again
[17:33] <afflux> hi qense
[17:35] <bdmurray> afflux: it looks like the reporter added Crash bug triagers for universe as a subscriber manually.  Does that sound right to you?
[17:35] <afflux> bdmurray: I asked him to do that, because we had no access
[17:36] <afflux> bdmurray: I opened a crash bug myself lately, and it was only apport who was subscribed automatically. I think ubuntu-crashes-universe should be added automatically (I think that's how we used to did that)
[17:40] <bdmurray> afflux: How did you open the crash bug? via nautilus or was it reported automatically?
[17:41] <afflux> automatically, IIRC
[17:41] <afflux> or maybe apport-cli
[17:46] <secretlondon> this is supposed to be the pob with apport and gutsy?
[17:47] <bdmurray> afflux: I'm looking at the code now
[17:47] <secretlondon> pitti apparently stopped apport retracing gutsy bugs according to hhdgh
[17:47] <afflux> mine wasn't even gutsy :(
[17:48] <afflux> (in case that's correct, I think there should be some sort of announcement on the MLs)
[17:49] <secretlondon> yes, the story was that it was due to the age of some launchpad -python thing
[17:49] <secretlondon> in which case we should update the python..
[17:49] <afflux> right
[17:50] <secretlondon> but this is second hand..
[17:52] <afflux> ah, looking at my bug, it hasn't been retraced, either, but the need-i386-retrace tag has been removed
[17:53] <pedro_> number?
[17:53] <pedro_> hey afflux
[17:53] <afflux> hi pedro_
[17:53] <afflux> number is bug 199846
[17:53] <ubotwo> afflux: Bug 199846 on http://launchpad.net/bugs/199846 is private
[17:54] <afflux> should I open it?
[17:54] <pedro_> ouch forbidden
[17:54] <bdmurray> afflux: could you subscribe me to it?
[17:55] <afflux> bdmurray: huh, found two accounts for "brian murray". I suppose it's brian-murray?
[17:55] <bdmurray> yes, that's me
[17:55] <afflux> done
[18:00] <afflux> hi rockstar_
[18:01] <rockstar_> hi afflux
[18:01] <afflux> you can watch new bugs arriving in #ubuntu-bugs-announce , that's a good start for triaging
[18:02] <rockstar_> afflux, thanks.  I was kinda combing through, looking for dupes right now.  The dual monitor set up is helpful for that.
[18:02] <afflux> oh right. I changed one monitor to LCD, that doesn't really work well with a second CRT as dual setup ;)
[18:09] <bdmurray> afflux: I'm under the impression there was an issue with the retracer for a while.
[18:10] <afflux> ah, right
[18:10] <afflux> I'm reading -devel, btw ;)
[18:43] <lesshaste> hi
[18:44] <bdmurray> hello
[18:45] <bdmurray> pedro_: I'm looking at the Ubuntu Desktop test cases and was wondering if you could take a look at some of it.
[18:45] <pedro_> bdmurray: ok i'll take a look to them later
[18:46] <bdmurray> pedro_: okay, there are some "!!!" caveats I'm concerned about.  there's also a whole bit about installing brasero, we can remove that now right?
[18:48] <pedro_> yes that's now shipped by default so that part (the install) can be removed
[18:48] <bdmurray> right, okay I'll rip that out
[18:48] <askand> Slow flash performance when compiz is  activated, is that a known bug in hardy?
[18:49] <bdmurray> well or remove the testing bit
[18:49] <bdmurray> er install
[19:16] <calc> https://bugs.edge.launchpad.net/ubuntu/+source/openoffice.org/+bug/184887/comments/8 <- bug reporters with a sense of humor ;-)
[19:16] <ubotwo> Launchpad bug 184887 in openoffice.org "OpenOffice crashes when importing csv file into calc" [Undecided,Fix released]
[19:16] <qense> ...
[19:17] <qense> wow! another crash of OOo, do you think it has the same cause! :P
[19:17] <calc> look at the powerpoint file attached to the comment ;-)
[19:17] <calc> neither one crashes on hardy so i marked it fixed, but the file is funny ;-)
[19:17] <pedro_> hahaha
[19:18] <pedro_> i feel sorry for his cat :-P
[19:18] <qense> it did crash at my hardy
[19:18] <qense> amd64
[19:19] <calc> oh hmm /me runs over to his amd64 box
[19:20] <qense> I've got a .crash file
[19:20] <calc> ah need to upgrade my box first before testing, has ~ 400 packages to download
[19:21] <calc> qense: please reopen with the crash file
[19:21] <qense> oops
[19:21] <qense> another bug?
[19:21] <qense> and mark the one you marked as fixed as duplicate of mine?
[19:21] <calc> qense: oh i can reopen it and then you just attach to the same bug
[19:22] <calc> ok its new again
[19:22] <calc> in about 30m i can test up on my machine as well
[19:24] <qense> apport is already uploading the error logs
[19:28] <qense> it's bug 201524
[19:28] <ubotwo> qense: Bug 201524 on http://launchpad.net/bugs/201524 is private
[19:28] <calc> qense: ok thats fine
[19:28] <qense> you're in bugcontrol?
[19:29] <calc> hmm i don't have permission to view it yet
[19:29] <calc> bdmurray: can you assign that to openoffice?
[19:29] <calc> qense: apparently i just have rights to change bugs, etc not view private ones
[19:30] <qense> bugcontrol members should be able to view private apport bugs and look for private parts and remove that
[19:31] <qense> I can make the bug visible
[19:31] <qense> but it still needs retracing
[19:31] <calc> ok
[19:31] <qense> is the retracing for amd64 working?
[19:31]  * calc doesn't know
[19:31] <calc> hopefully :)
[19:32] <calc> amd64 and i386 are the two main platforms
[19:32] <alex-weej> can someone do a quick test for me please? just remove the GNOME notification area from your panel and re-add it
[19:32] <alex-weej> it comes back without any icons on my system
[19:33] <qense> anyway, I need to go
[19:33] <qense> bye
[19:34] <calc> brb, lunch
[19:34] <seb128> alex-weej: confirmed
[19:35] <alex-weej> seb128: do you know if there's an open bug for it? someone has one open on launchpad but it's not Incomplete, Low
[19:35] <alex-weej> *it IS Incomplete, Low
[19:35] <alex-weej> https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/195915
[19:35] <ubotwo> Launchpad bug 195915 in gnome-panel "removing notification area from the panel" [Low,Incomplete]
[19:35] <seb128> alex-weej: not that I know
[19:36] <seb128> alex-weej: in fact it's really broken, if you open an application using the notification area it doesn't add the icon there
[19:36] <alex-weej> yeah i noticed that too
[19:39] <alex-weej> seb128: killall gnome-panel
[19:39] <bdmurray> calc: I don't have permission to view that bug either
[19:39] <alex-weej> it comes back to life, (albeit without n-m... groan)
[21:01] <afflux> Is there a special reason why the upstream project for hardy's source package "emerald" has been set to "beryl"?
[21:04] <afflux> I'll change it back to "emerald" if noone raises any objections
[21:06] <bdmurray> afflux: is the upstream watch in bug 147529 right?
[21:07] <afflux> bdmurray: it's emerald, not beryl. I clicked "next" and didn't check because I forwarded an emerald bug some days ago where the project was correct
[21:07] <afflux> bdmurray: I invalidated the beryl task and added emerald
[21:10] <bdmurray> afflux: okay, my concern is there isn't a relationship between the "emerald" project and its bug tracker
[21:11] <bdmurray> so if someone tries to add also affects project emerald they won't see information about which bug tracker to use
[21:11] <afflux> do you mean the LP project or the upstream?
[21:11] <afflux> ah, LP
[21:11] <bdmurray> the lp project
[21:13] <bdmurray> if you look at https://launchpad.net/linux/ you can see which bug tracker the kernel uses
[21:13] <afflux> right
[21:13] <afflux> I think mvo can change this
[21:13] <bdmurray> I actually have the power to do it
[21:14] <afflux> ah
[21:14] <bdmurray> opencomposting.org is the right url for them?
[21:15] <afflux> yes. They don't really have an own website, it seems to be distributed along with compizfusion
[21:18] <bdmurray> afflux: okay, I updated the project.  It should be easier to add upstream bug watches now.  At least thats the theory
[21:19] <afflux> why "theory"?
[21:19] <bdmurray> s/theory/my understanding/ ?
[21:19] <afflux> right
[21:20] <afflux> okay, you still have to paste an url, but the "also affects project" page now lists the used bug tracker
[21:20] <bdmurray> yeah, it'd be neat if you could just put a # there if the tracker is known
[21:21] <afflux> indeed
[21:21] <afflux> okay, I'm going to bed. good night!
[21:21] <bdmurray> good night!
[22:45] <Gnine> can't login - blank screen | 8.04 2.6.24-11-generic x86_64 | after update on 3.10.2008
[23:14] <phoenix24> When does the HUG Day Start ?
[23:15] <bdmurray> phoenix24: probably now in Europe somewhere
[23:15] <rockstar_> HUG day?
[23:16] <bdmurray> http://wiki.ubuntu.com/UbuntuBugDay
[23:16] <rockstar_> BUG day makes more sense...
[23:17] <cudjoe> hi everyone!
[23:17] <bdmurray> It's been traditionally called Hug Day
[23:17] <cudjoe> I've just submitted a debdiff, changed the status to Fix Released.
[23:18] <cudjoe> but did get really well the Sponsoring Queue
[23:18] <cudjoe> someone could tell me please ?
[23:18] <bdmurray> cudjoe: Fix Released should be used if the fixed package is available in the archive
[23:19] <cudjoe> bdmurray: oops. I was following "the 5 a day" tutorial :) that's my first one !
[23:19] <bdmurray> it's easy to change back
[23:19] <cudjoe> I change it back.
[23:20] <cudjoe> how could I submit it ?
[23:20] <cudjoe> like I mean push it in the queue
[23:21] <bdmurray> what package is the bug about?
[23:21] <cudjoe> exaile. here it is :https://bugs.launchpad.net/ubuntu/+source/exaile/+bug/95860
[23:21] <greg-g> hmmm, getting error when trying to add some bug numbers to my 5-a-day file: "'190092' has already been added today" even though I don't see it in my file online
[23:22] <bdmurray> greg-g: is it in someone elses?
[23:24] <greg-g> bdmurray: oh, it is in my local copy of my file
[23:24] <bdmurray> heh
[23:24] <cudjoe> state changed to "Fixed commited" in Exaile (ubuntu)
[23:25] <cudjoe> In the tutorial it says > "Add it to the sponsoring queue or upload it yourself"
[23:26] <greg-g> bdmurray: in that case all I would need to do is do a bzr commit in my 5-a-day-data dir later right (since there is still a lock on the branch)
[23:26] <greg-g> that is a question
[23:26] <bdmurray> cudjoe: take a look at https://wiki.ubuntu.com/SponsorshipProcess
[23:26] <bdmurray> I believe you are supposed to subscribe a team to the bug
[23:26] <bdmurray> Then it will get on their radar
[23:27] <cudjoe> Ok. I did not get that when reading the page.
[23:27] <bdmurray> cudjoe: which tutorial were you reading?
[23:28] <cudjoe> this one : https://wiki.ubuntu.com/5-A-Day
[23:29] <cudjoe> Should I do "subscribe someone else" and select "ubuntu-main-sponsors"
[23:29] <bdmurray> greg-g: I'm not sure how the 5-a-day bzr branch is setup.  normally with bzr branches I do a pull, commit, push.  In this case I'd just add another bug.
[23:29] <bdmurray> exaile is a universe package though so it would be uubuntu-universe-sponsors
[23:30] <greg-g> bdmurray: yeah, just thought of that too :)  good excuse to keeping triaging
[23:32] <cudjoe> bdmurray: ok done. thanks for helping. I was almost there :) Next ones are going to be easier.
[23:33] <bdmurray> cudjoe: lokoing at your patch the debian/changelog file has an issue
[23:34] <cudjoe> really ? ...oh.
[23:35] <bdmurray> to get the bug automatically closed the format should be (LP: #95860)
[23:35] <phoenix24> Anyone Triaging Totem Bugs (help here) ?
[23:36] <cudjoe> bdmurray: I saw the "Closes" format in the previous entries of the changelog...Should I rebuild it ?
[23:37] <bdmurray> cudjoe: the closes format may have been specific to a different bug tracking system
[23:38] <bdmurray> and yes rebuilding it would be best, I imagine a sponsor would say something
[23:41] <blueyed> Should the KDE bug day also mention #ubuntu-bugs? (https://wiki.ubuntu.com/UbuntuBugDay/20080313/KDE)
[23:42] <cudjoe> bdmurray: done. Regarding the page, I had read it, but it's pretty confusing (for non native speaker maybe)
[23:42] <bdmurray> cudjoe: The sponsorship page?  I agree and have contacted someone about it.
[23:42] <blueyed> ..or even the main page (-"/KDE")?
[23:43] <cudjoe> It should mention that SponsorshipProcess consists in subscribing the team to the bug :)
[23:43] <cudjoe> thanks everyone. I hope not to have to bother anymore.