[06:54] <gnomefreak> if anyone is here, for some reason i cant add upstream bug link to LP bug #234029
[06:55] <gnomefreak> it shows on the left side menus under Remote bug watches but i should beable to add it to the packages area but project nor distribution/package wont allow me to add upstream bug link
[07:02] <gnomefreak> i got it. it seems that the project wasnt there as it normally is already present but i was able to add it
[08:35] <spiv> Does anyone ever use the "Best Fix Available" state rather than just "Fix Available" when linking a branch to a bug?
[08:35] <spiv> I don't think I've ever seen the former get used...
[08:35] <RAOF> I don't think I've ever used it.
[08:36] <spiv> I might ask thumper what he thinks.
[08:37] <RAOF> You're considering just removing it?
[08:40] <cody-somerville> I've used it
[08:40] <spiv> RAOF: it's not up to me, I'm just wondering out loud.
[08:40] <RAOF> cody-somerville: How do you know that its' the _best_ fix?
[08:40] <spiv> Maybe it's just that I've very rarely seen multiple branches linked to one bug.
[08:40] <cody-somerville> RAOF, because I decided it was
[08:41] <RAOF> cody-somerville: :)
[08:41] <cody-somerville> What would happen is that sometimes developers would have different ideas about how to address a bug
[08:41] <spiv> I know many of my fixes are the best, because they're often the *only* fix available when I write them ;)
[08:41] <cody-somerville> or a quick fix be provided at first
[08:42] <RAOF> spiv: Aaah.  Whereas I read that as 'it's not possible to write a better fix for this issue"
[08:42] <cody-somerville> so we use the best fix available to designate the one we've decided to use in our mainline
[08:43] <spiv> cody-somerville: ah, so that's actually happened?  Cool.  I was starting to wonder if it was just a theoretical situation...
[08:43] <cody-somerville> spiv: http://launchpad.net/sapidlib
[08:44] <cody-somerville> One thing that I find annoying is that when you merge a branch that is marked as a fix for a bug into the mainline, it gets carried over to the mainline
[08:45]  * cody-somerville hopes someone is working on the branches stuff because there are some pretty cool ideas in there
[08:45]  * rexbron wonders if it will be possible to file bugs against packages in PPAs
[08:45] <spiv> cody-somerville: post to the launchpad-users list
[08:45] <cody-somerville> spiv, What would you like me to post?
[08:46] <spiv> cody-somerville: there are definitely guys on the launchpad team working on the branch management stuff
[08:46] <spiv> cody-somerville: your ideas :)
[08:46] <cody-somerville> spiv, I'll just chat with the launchpad folks here at UDS :)
[08:46] <spiv> cody-somerville: Oh, even better!
[08:46]  * cody-somerville grins.
[08:46] <stub> lifeless: Can you go to https://lists.ubuntu.com/mailman/admin/launchpad-reviews and unblock my review request post? The other admin besides you is at UDS
[08:47] <spiv> stub: he is too, I think?
[08:47] <stub> is? bugger.
[08:47] <lifeless> stub: I am
[08:48] <lifeless> , but I have forgotten the passord
[08:48] <lifeless> okk, got it
[08:49] <stub> ta
[09:19] <thumper> lifeless: can you make barry an admin of the launchpad-reviews list please?
[09:21] <thumper> cody-somerville: I think I have fixed the bzr --fixes propagation bug
[09:21] <cody-somerville> thumper, awesome :)
[11:58] <lifeless> jtv: ping
[12:00] <jtv> lifeless: pong
[12:03] <Ziroday> Hi, I am getting errors about PKG_CONFIG (http://launchpadlibrarian.net/14665648/buildlog_ubuntu-hardy-i386.lxpanel_0.3.6-2~lxde_FAILEDTOBUILD.txt.gz)
[12:07] <lifeless> jtv: I mailed a query to lp about roestta branding in messages, was just following up
[12:08] <jtv> lifeless: I'm a bit behind on my mailing lists... Let me look.
[12:10] <jtv> lifeless: that's a bug, thanks.
[12:19] <Ziroday-laptop> anyone?
[12:34] <lifeless> thumper: want me to file it ?
[12:35] <lifeless> Ziroday-laptop: #ubuntu-motu is a better channel for that question
[12:37] <Ziroday-laptop> lifeless: okay
[12:38] <lifeless> thumper: nvm, mt
[12:38] <lifeless> jtv: want me to file it?
[12:38] <jtv> lifeless: already done, thanks.
[14:41] <emgent> hello there
[14:41] <emgent> some idea about Bug #34031 ?
[14:41] <emgent> oh no, answer not bug..
[14:41] <emgent> https://answers.edge.launchpad.net/launchpad/+question/34031
[14:41] <emgent> this :)
[19:52] <foka> Hi!  Is there a way to "Unsubscribe someone else" whom I accidentally subscribed to a bug report?
[21:36] <Rinchen> foka, nope 
[21:36] <Rinchen> foka, painful isn't it :-)  
[21:37] <Rinchen> foka, I often send "oops, I'm sorry" emails.
[21:37] <Rinchen> foka, there is a bug about that.  We'll get to it at some point I'm sure.
[21:39] <foka> Rinchen, Thanks for letting me know!  :-)
[21:40] <Rinchen> I fat-finger LP ids a lot. :-)
[23:23] <beuno> [reed], you want to search in commit messages?
[23:23] <[reed]> no, the actual branches
[23:23] <[reed]> like LXR
[23:23] <[reed]> but for bzr branches
[23:23] <beuno> [reed], well, that's outside bzr's scope I suppose
[23:23] <beuno> searching in files
[23:24] <[reed]> hmm
[23:24] <[reed]> ok, what about searching commit messages for multiple branches?
[23:24] <beuno> you may be able to write a plugin that goes through the whole tree, and back in revisions though
[23:24] <beuno> you can't search revisions at all
[23:24] <[reed]> no, I only care about the current tip revision
[23:24] <beuno> well, why would bzr do something that is perfectly doable with grep?
[23:25] <[reed]> because I don't want to check out all these (20+) bzr repos just to search for one phrase
[23:26] <beuno> right, well, bzr doesn't have anything like that currently, or planned even. You may have to build a custom tool
[23:26] <[reed]> ok, so, is there a way to search commit messages for multiple branches?
[23:26] <beuno> maybe a plugin using the smart server, but I still think it's a tremendous overkill for bzr to do it
[23:27] <[reed]> if they are all under the same project
[23:27] <beuno> [reed], no, no way to search commit messages either currently  :/
[23:27] <beuno> that might be something useful and doable in Launchpad though, may be worth opening a bug requesting it
[23:28] <[reed]> ok
[23:28] <[reed]> thanks!
[23:30] <beuno> np  :)