[00:54] <mtaylor> feature request... "Lee Bieber has proposed merging ~kalebral/drizzle/drizzle-clean-code into Drizzle Active Development Branch." ... anyway that lp: could be prefixed there, or a full lp:~blah/blah could go in the email?
[00:54] <mtaylor> it makes it easier to cut and paste if I don't have to type lp: :)
[00:55] <Rinchen> jml, ^^
[00:55] <jml> mtaylor: yeah, that's a great idea -- I *think* we already have a bug open for that one. Let me check.
[00:56] <mtaylor> jml: it's, of course, not killing me or anything
[00:56] <jml> (actually, there might even be a branch that fixes it...)
[00:56] <jml> https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/249227
[00:58] <jml> spiv: hello
[00:58] <jml> spiv: have you anything more to say on https://bugs.edge.launchpad.net/launchpad-bazaar/+bug/121193 ?
[00:59]  * spiv looks
[01:01] <spiv> jml: well, I still think that the ideal test for that bug is getting a new user to try perform that task
[01:02] <spiv> jml: although finding new users willing to be guinea pigs is easier said that done, not to mention explaining to a new user what this task actually is in a way that doesn't invalidate the results :)
[01:02] <jml> spiv: right.
[01:02] <spiv> (Which is a problem in itself, but not really one in the scope of the bug...)
[01:03] <spiv> So, I'll take another look at staging now.
[01:03] <jml> spiv: thanks.
[01:04] <spiv> Huh, the big search box on the front page no longer leads me to a way to register a project if there are no hits for my search.
[01:05] <spiv> Ok, merely registering a project is now harder to find than it used to be, but I'm now over that hurdle.
[01:06] <spiv> Whoops, not quite.
[01:06] <spiv> Man, I've already filed a bug about this.
[01:06] <spiv> Pardon me while I go make cranky noises on that other bug.
[01:28] <spiv> jml: Ok, I'm done venting in https://bugs.launchpad.net/launchpad-foundations/+bug/246442, back to your bug
[01:29] <jml> spiv: :D
[01:32] <spiv> Ok, registered a test project.
[01:32] <spiv> Now I'm at an ambiguous point, wrt to the bug.
[01:33] <spiv> Which comes first: the desire for lp:myproject, or the branch that will become lp:myproject? :)
[01:33] <Hobbsee> cody-somerville: You sent me a contentless ping.  This is a contentless pong.  Please provide a bit of information about what you want and I will respond when I am around.
[01:33] <spiv> jml: so, here's some thinking out loud:
[01:34] <spiv> jml: if there's no code for this project, a note about that on the overview page for that project (i.e. lp.net/foo) is probably appropriate
[01:35] <spiv> jml: similarly, if there is at least one branch, but no development focus, the project is (typically) only partially configured.  So a nag to the proj adminstrator on the overview page (or via email?) seems appropriate?
[01:36] <spiv> Email's a bit much, I think; savvy users will set dev focusses fairly promptly, and don't need an email that will be out of date by the time they receive it.
[01:37] <Hobbsee> cody-somerville: pong?
[01:37] <spiv> Branch registration time would be another good place to nag/prompt for "and is this branch the dev focus?", except that many new branches arrive via "bzr push".
[01:38] <spiv> jml: I wonder, how common is it that the development focus is *not* the first branch registered?
[01:38] <spiv> jml: maybe launchpad should JFDI, and let users change it later if they want it set differently?
[01:38] <jml> spiv: lifeless and I were discussing this on #bzr yesterday
[01:39] <spiv> I imagine we can actually get some stats out of the DB to approximately answer that second-last question, btw.
[01:39] <jml> spiv: I think there's a lot to be said for that.
[01:40] <jml> spiv: I think the two other interesting cases are: projects that have code imports (e.g. Twisted) and projects that only have random branches from people.
[01:41] <spiv> Right.  Basically, projects where the active code development by the project's official team isn't taking place in Launchpad.
[01:41] <spiv> Idea: Disabling "lp:proj" altogether for a project is approximately equal to setting "Does not use Code" flag?
[01:44] <jml> spiv: I think so.
[01:45] <jml> spiv: but thumper disagrees.
[01:45] <spiv> I wonder what use cases he has in mind?
[01:46] <spiv> I know that theoretically some projects might not want a single development focus at all, but I'm not sure it's worth penalising everyone else for that.
[01:47] <spiv> (And so long as those hypothetical projects can set lp:foo/focusA, lp:foo/focusB, etc, they probably wouldn't care about lp:foo)
[01:48] <spiv> A slightly more restricted version of auto-setting lp:foo would be "the first branch in that project registered by a project owner".
[01:48] <spiv> I don't see any harm in that.
[01:48] <jml> spiv: the use cases are projects like Twisted, I think.
[01:48] <jml> spiv: there should be *something* that says they don't use Launchpad for codehosting
[01:49] <jml> spiv: but people should still be able to do 'bzr branch lp:twisted'
[01:49] <spiv> Worst case a project can always upload a trivial branch for lp:foo that has a single file, README, that says "The real source repo is svn://..." or whatever.
[01:50] <spiv> jml: right, and so long as a bzr branch of Twisted trunk exists somewhere, LP already allows the project owners to make that work.  So I'm not sure what the issue is?
[01:51] <spiv> That there might be projects with bzr branches owned by project owners, but none of those branches are trunk?
 Idea: Disabling "lp:proj" altogether for a project is approximately equal to setting "Does not use Code" flag?
[01:51] <jml> that's what we're talking about, right?
[01:52] <spiv> Oh, right.  Well, that was more an idea of a way to think about things, rather than a concrete suggestion :)
[01:52] <spiv> I didn't exactly try thinking it through carefully :)
[01:53] <jml> spiv: so what proposition did you think we were discussing?
[01:53] <spiv> Auto-setting lp:foo to be the first branch registered (by a project owner).
[01:54]  * jml reads scrollback in this new light
[01:55] <jml> spiv: ok.
[01:55] <jml> spiv: so, one possible danger is that default stacking is tied to the development focus
[01:55] <jml> "danger" is too strong..
[01:55] <spiv> Ooh, stacking provides yet another wrinkle.  Exciting!
[01:56] <spiv> So branching and then tracking an immature project is likely to cause inconvenience.
[01:57] <jml> spiv: perhaps.
[01:57] <spiv> I think that's going to be true anyway; young projects rapidly and radically change processes, tools, etc, relative to mature projects.
[01:58] <spiv> And I suspect that the first branch is still likely to be the right branch for lp:foo.
[01:58] <jml> spiv: I mean, if you create a dev focus automatically, then new branches will stack on that, if the dev focus changes, the branches stacked on the old dev focus will still work
[01:59] <spiv> Ok.  But then you're tracking a branch that isn't the dev focus, possibly without realising?
[02:00] <jml> spiv: what do you mean by "tracking a branch" here?
[02:00] <spiv> jml: something intentionally vague ;)
[02:01] <spiv> jml: either regularly mirroring via pull, or regularly merging into a branch that was branched off it.
[02:01] <spiv> And perhaps other things; whatever users of source code tend to do with projects they are interested in?
[02:07] <jml> oh right, so orthogonal to stacking
[02:08] <spiv> Right.
[02:08] <jml> spiv: ok, for a minute there I thought you were responding to something I said :P
[02:08] <spiv> You wish ;)
[02:08] <leonel> in my ppa  there's a  copy packages
[02:09] <leonel> I've made a hardy package
[02:09] <jml> spiv: so, one wouldn't be tracking a non-trunk branch, lp:foo would always point to trunk, the issue is that the trunk branch would be a different one.
[02:09] <leonel> if I copy to gutsy  the package will get builded for gutsy  automagically ???
[02:09] <spiv> jml: So, I think the best solution probably is more automatic than the status quo.  For this bug, I'll add a branch to this test project and then see how it looks.
[02:09] <jml> spiv: cool.
[02:10] <spiv> jml: well, it depends on if the bzr client will always remember "lp:foo" or the thing that lp:foo resolves to...
[02:10] <jml> spiv: if you don't find anything terrible, I think I'll close off this bug and file another.
[02:10] <jml> spiv: yeah, that wacky bzr client :P
[02:10] <cprov> leonel: no, you can't rebuild the same source in another distroseries (because it will generate the same binary versions with different contents).
[02:10] <leonel> cprov: so what is that copy for ??
[02:10] <spiv> jml: either way might be problematic in some situations.  (I suspect the current behaviour is remembering "lp:foo", and I think that's probably the least bad option)
[02:11] <cprov> leonel: copying source + binaries will work, but copying binaries backward is risky
[02:11] <jml> spiv: yes.
[02:11] <leonel> cprov:  Ok I can do it for gutsy and copy to hardy  in the public  apt source  right ??
[02:12] <cprov> leonel: for copying stuff between PPAs, propagating source & binaries forward, etc
[02:12] <leonel> cprov: ok thank you
[02:13] <cprov> leonel: you don't need to mess with the client apt sources_list, copy source & binaries from gutsy to hardy.
[02:15] <leonel> cprov: I won't copy I just understood that my ppa packages with that copy will be rebuilded for other ubuntu version
[02:15] <leonel> cprov: thank you
[02:21] <spiv> jml: So, I just registered a branch (a remote one, for the sake of trying something new and also to avoid LP trying to mirror something that doesn't exist).  That dumps me at the page for that newly-created branch, which a) has several high links suggesting merging this into other branches, although none exist yet (which I think is ok, actually, just marginally surprising), b) doesn't mention to me the lack of development focus.
[02:25] <spiv> jml: If I think take the link back to the project page (either via the big code tab button, or via the project name in the branch details) I'm taken to the code overview page, with a reasonably prominent "set it now" message about the development focus.
[02:25] <spiv> jml: which seems pretty good.
[02:25] <spiv> jml: So I'm happy to consider my original bug closed.
[02:25] <spiv> jml: good work :)
[02:25] <jml> spiv: cool. thanks.
[02:25]  * jml closes that one and files some more.
[02:27] <jml> spiv: can you mark the remote branch as the dev focus?
[02:31] <spiv> jml: I just closed that bug myself, actually :P
[02:31] <spiv> jml: yes, I can mark it as a dev focus
[02:33] <jml> spiv: hmm. that has dubious utility.
[02:34] <spiv> jml: proprietary code?
[02:35] <spiv> jml: anyway, that's a separate problem, and one I don't care about :)
[02:35] <jml> spiv: hmm, I guess we do resolve lp:foo for remote branches.
[02:35]  * jml is satisfied.
[02:35] <jml> spiv: thanks for the help.
[02:35] <spiv> You're welcome.  At least someone paid attention to that bug report, unlike some others I've filed ;)
[04:06] <emgent> uhm.. some launchpad people around ?
[04:07] <emgent> i dont understand why all user have permission to set maps location in the user that dont set it yet.
[04:07] <emgent> example: https://launchpad.net/~darksun88/+editlocation
[04:07] <beuno> emgent, there's a bug open for that
[04:07] <beuno> but it was done on purpose
[04:08] <emgent> ah ok.
[04:08] <emgent> cool.
[05:16] <kirkland> where can i find my openid string in my launchpad account page?
[05:16] <kirkland> i know i've seen it before, but i can't put my finger on it now
[05:16] <beuno> kirkland, on your user page
[05:17] <kirkland> beuno: thank you... where?
[05:17] <beuno> kirkland, under SSH keys
[05:17] <beuno> you may need to log into edge
[05:18] <kirkland> beuno: hmm, let me try that
[05:18] <beuno> kirkland, are you in the launchpad beta team?
[05:19] <kirkland> beuno: i was at one time....
[05:19] <beuno> that's probably where you saw it, if you're not anymore
[05:19] <kirkland> beuno: hmm, i'm still not seeing it
[05:19] <beuno> I can add you again
[05:19] <kirkland> thanks
[05:19] <beuno> openid is only for beta users AFAIK
[05:20] <kirkland> i'm logged in through edge
[05:20] <kirkland> beuno: is that going to be opened up, at some point?
[05:20] <beuno> kirkland, yes, although I don't know what it's blocked on
[05:20] <beuno> kirkland, refresh (or maybe log out and back in again)
[05:22] <kirkland> beuno: ah, there it is
[05:22] <kirkland> beuno: thanks
[05:23] <beuno> kirkland, :)
[05:43] <persia> beuno, I'm not a beta user, and I use LP openID daily.
[05:43] <kirkland> persia: but do you know your OpenID url?
[05:43] <persia> No.
[05:43]  * persia looks
[05:45] <persia> I'd need to trace network traffic.  REVU and w.u.c both know my OpenID url (or one that works for me)
[05:45] <kirkland> persia: right
[05:45] <kirkland> persia: Launchpad can tell you your OpenID url
[05:46] <kirkland> persia: but evidently you have to be in the beta testers team to see it
[05:46] <persia> Ah, but it only tells edge users.  Now I get it.  I still think it's inaccurate to claim "openid is only for beta users" when so many of us non-beta users rely on it.
[05:46] <beuno> persia, right, everyone has one, but only beta testers see it
[05:47] <Ursinha> beuno, didn't know that
[05:47] <beuno> Ursinha, hi. What are you doing up!?
[05:48] <Ursinha> hahaha same as you, and you don't have the "hey, i'm in NZ" excuse anymore :P
[05:48] <beuno> persia, I think there are some decisions left to be made with OpenID, so they're keeping it in beta
[05:48] <wgrant> The URL changed in RF recently, IIRC.
[05:48] <persia> beuno, but it's *not* in beta if I can use it.  That's my point.  it's a false claim.
[05:49] <beuno> Ursinha, I had tons of work I needed to finish before tomorrow (london) morning. That's my excuse!
[05:49] <wgrant> Because the old URLs are very broken.
[05:49] <Ursinha> beuno, ok ok :)
[05:49] <beuno> :p
[05:49] <beuno> Ursinha, are you on the night shift, or just sleepless?
[05:49] <spm> Ursinha: sounds to me like beuno is clutching at very very vague straws :-)
[05:49] <beuno> hahah
[05:50] <spm> I just wish the pair of you would admit you prefer talking to us aussies.... :-P
[05:50]  * beuno is starting to wonder if he has Ursinha and beuno on highlight
[05:50] <wgrant> Oh dear. It's an Australian.
[05:50] <Ursinha> hahahaha
[05:50] <beuno> spm, we like to talk to people from the future
[05:50] <beuno> so we're well informed of what's going to happen
[05:51] <Ursinha> spm, yes, that's that beuno said
[05:51] <spm> beuno: lol!
[05:51]  * beuno sold all his stock before everything went down hill thanks to it
[05:52]  * wgrant will be travelling to the past in December.
[05:52] <Ursinha> hahahaha
[05:52] <wgrant> Who broke the PPA buildd master?
[05:52] <Ursinha> beuno, my night shift ended 3 hours ago
[05:52] <spm> wgrant: when?
[05:53] <wgrant> spm: All PPA buildds are idle, and I've had builds with 19 seconds until start for several minutes now.
[05:53]  * ajmitch wonders what can be done about having so many australians around
[05:53] <wgrant> I suppose with all the new buildds the slave-scanner could take a while, but not this long.
[05:53]  * wgrant moves ajmitch to .au too.
[05:53] <beuno> hey ajmitch
[05:53]  * wgrant crashes .nz into .au.
[05:53] <ajmitch> that certainly wouldn't make me australian
[05:54] <ajmitch> hello
[05:54] <beuno> ajmitch, never bumped in to eachother again, but it nice to meet you
[05:54] <beuno> always cool to put a face on a nickname
[05:54] <ajmitch> yes, it's good to meet random LP people :)
[05:55] <jml> LP is world famous in New Zealand
[05:55] <ajmitch> groan
[05:55] <spm> jml: ???? care to rephrase that? :-)
[05:55] <beuno> well, doesn't like 10% of the population work on LP?
[05:55] <jml> ajmitch: sorry. I had to try that at least once :)
[05:55]  * beuno ducks
[05:55] <Ursinha> beuno, lol
[05:55] <Ursinha> hauhauah
[05:55] <jml> spm: http://en.wikipedia.org/wiki/L%26P
[05:55] <wgrant> Does Canonical employ sheep?
[05:55] <ajmitch> jml: once is enough :)
[05:56] <jml> ajmitch: heh heh
[05:56] <spm> jml: oh gawd. it's an advertsing slogan. no wonder it doesn't make sense. :-D
[05:58] <beuno> ok, I'm off to sleep for a few hours before my next call is up
[05:58] <spm> night beuno!
[05:59] <beuno> have a good afternoon spm
[05:59] <ajmitch> night
[05:59]  * beuno waves to the channel and closes his laptop lid
[06:02] <Ursinha> beuno, good morning :P
[06:02] <Ursinha> see you tomorrow
[06:02]  * Ursinha waves goodbye 
[06:02] <spm> Night Ursinha!
[06:03] <Ursinha> spm, actually I missed the "to beuno" part
[06:03] <Ursinha> have to talk with jml before leaving :)
[06:04] <spm> Ursinha: I was gunna say - it's not my EOD yet, be earlyfor yuo to EOD yourself! ;-)
[06:04] <spm> wgrant: those buildd's seem to be still kicking along.
[06:04] <wgrant> spm: They've woken up now, yes.
[06:04] <wgrant> Hmmm.
[06:04] <wgrant> No logs, though.
[06:05] <wgrant> So the slave-scanner might be being a bit slothful.
[06:05] <wgrant> And it really doesn't take that long to build.
[06:05] <wgrant> So something is still wrong.
[06:07] <spm> interesting. it appeared to have gone gaga for quite a while. still chasing...
[06:08] <wgrant> It has been happening a bit lately.
[06:08] <spm> hmmm. cprov was chasing something this morning. possibly related.
[09:34] <thekorn> hi, there are some bugs/unclear descriptions on https://edge.launchpad.net/+apidoc, what's the right place to report this?
[09:35] <james_w> thekorn: on launchpadlib I think. I think it's automatically generated.
[09:37] <wgrant> I suspect the descriptions will come from Launchpad.
[09:38] <mwhudson> yeah, launchpad
[09:38] <thekorn> good, thanks
[12:44] <Peng_> jml: ping?
[12:57] <Flimm> Hello, I've got a question about netiquette on Launchpad, should I address other people by their first names in the comments of a bug report?
[12:57] <Hobbsee> Flimm: either that, or their launchpad username.
[12:57] <Hobbsee> whatever their display name is is usually the most sensible one to use
[12:58] <Flimm> Their display name being their full name, or their username?
[12:59] <Hobbsee> their display name being just before "wrote <length of time> ago.
[12:59] <Peng_> I always feel awkward calling people by their first name, but I feel even more awkward saying "Mr. Lastname" or something. I usually use username or first name.
[12:59] <Peng_> Conversation killed?
[13:01] <Flimm> It should be in the Ubuntu Code of Conduct! ;-)
[13:01] <Hobbsee> i figure that whatever they set as their display name is what they want to be called, unless i know them.
[13:01] <Flimm> Not at all.
[13:04] <Flimm> Hmm, I guess I would want to be called David D Lowe unless I recognise the user who is addressing me, in which case I wouldn't mind being called David
[13:06] <Flimm> Well, I guess my question has been answered, thank you everyone.
[13:11] <oSoMoN> hi folks
[13:11] <oSoMoN> I need to change the actual version number of a release I just registered for project elisa-plugin-weather
[13:11] <oSoMoN> anyone can help me?
[13:12] <oSoMoN> it seems this cannot be done from the web frontend
[13:16] <Flimm> You can't do this yourself, you'll have to ask a Launchpad admin to do it
[13:17] <Flimm> I don't if there are any Launchpad admins here... if you post a question at Launchpad itself, a Launchpad admin will eventually get round to doing it
[13:20] <intellectronica> oSoMoN: please file a question on launchpad. an admin will take care of it asap
[14:18] <oSoMoN> intellectronica: thanks, will do
[14:27] <emgent> evening
[14:53] <alvin> Is there anyone here who understands Italian? --> https://bugs.launchpad.net/vfront/+bug/280730 (I suppose it's Italian)
[14:55] <persia> alvin, It is Italian (although mine is sufficiently rusty that I won't hazard a gloss)
[15:03] <alvin> I was just wondering if this was really a bug report about IE7.
[15:55] <papasmile> Peaec and God's mercy :)
[16:50] <leonel> hello :
[16:51] <leonel> If I create a  launchpad team  the members for that team can upload  ppa packages for the team right ??
[16:51] <cprov> leonel: right.
[16:51] <Odd_Bloke> Is it worth having https://help.launchpad.net/HelpRotation in the topic?  I just had to go to my mail client to find it...
[16:52] <leonel> cprov:  great  I'm doing a package maintenance but I don't want to use my  ppa and that package can be done better in a team
[16:53] <leonel> cprov: so all the procedures are the same  just  create the team   , join the team  and upload the package to the team's ppa ?
[16:53] <cprov> leonel: yup, that simple.
[16:53] <leonel> cprov: great Thank you
[16:53] <cprov> leonel: you're welcome.
[16:55] <amondo> i been using launchpad for a while, recently whenever i do a "bzr up" on a checked out branch, i get a warning: " <RepositoryFormatKnit1> for <branch-url-on-launchpad-here> is deprecated - please use 'bzr upgrade' for better performance "
[16:55] <amondo> problem is that doing bzr upgrade never does anything, my bzr always says its using the latest repository format
[16:56] <amondo> anyone seen something like this?
[16:56] <laga_> amondo: i do
[16:56] <laga_> and it's very annoying
[16:56] <laga_> i've also seen messages like "server too old for streaming pull", but that's a different issue
[16:57] <amondo> laga_: any idea what's causing this? is there a bug filed for it, for example?
[16:57] <amondo> laga_: i haven't seen  "server too old for streaming pull", perhaps because i'm not running a local bzr server?
[16:58] <laga_> no, i saw that when pulling from LP
[16:58] <laga_> it's probably been resolved since thatr
[17:01] <amondo> laga_: i'll probably just file a bug report against bzr for it? or do you think its launchpad-specific?
[17:04] <laga_> yeah, i blame LP
[17:04] <laga_> but i always go
[17:04] <laga_> amondo: some LP guy is supposed to be on duty
[17:04] <laga_> he should be able to answer your question
[17:04] <amondo> thanks, i will find out who that is
[17:05] <laga_> you can check here: https://help.launchpad.net/HelpRotation
[17:05] <amondo> it says it should be in the channel topic
[17:06] <amondo> sinzui: are you on rotation now?
[17:06] <sinzui> amondo: I believe EdwinGrubbs is.
[17:06] <amondo> thanks
[17:06] <sinzui> amondo: But I'll help if I can
[17:07] <amondo> sinzui, did you see my messages just now about launchpad/bzr problem
[17:07] <sinzui> uhg
[17:07] <amondo> i don't know whether this is some kind of well known problem or not
[17:07] <sinzui> amondo: the deprecated messge?
[17:08] <amondo> yes, it keeps saying my repo format is deprecated, but i'm not hosting the repo -its on launchpad
[17:08] <sinzui> We launchpaders see it all the time. We do need to upgrade the server
[17:09] <amondo> sinzui: so its nothing for me to worry about?
[17:09] <amondo> i should ignore the "bzr upgrade" warning?
[17:09] <sinzui> amondo: We plan to upgrade the server soon, we have been transitioning infrastructure for the past few cycles
[17:10] <sinzui> amondo: There is nothing to worry about.
[17:10] <amondo> thanks for your help
[17:49] <leonel> I see that  launchpad  automagically  deletes de previous package when a new version is done ??   I had cherokee 0.9.3  and today was released  0.9.4  made the deb and uploaded to ppa  and  0.9.3 got deleted   Right ??
[17:50] <bigjools> leonel: that's right
[17:50] <leonel> bigjools: great  thank you
[17:52] <persia> bigjools, Are they deleted, or just superceded?
[17:53] <bigjools> persia: deleted from the archive
[17:53] <persia> bigjools, Thanks.
[17:54] <bigjools> np
[19:44] <mtaylor> how do I attach an upstream bug reference to a bug report? I can't quite seem to find it...
[20:00] <geser> mtaylor: you mean to add a bug watch?
[20:00] <mtaylor> geser: maybe that's it?
[20:00] <beuno> mtaylor, I *think* that if you click "Also affects distribution..."
[20:01] <beuno> at least that's where you can punch in a URL
[20:01] <beuno> BjornT_, intellectronica, can you confirm that?  (if you do, I'm filing a bug!)
[20:01] <sinzui> mtaylor: Use also affect to select an upstream project if you already have not.
[20:01] <mtaylor> sinzui: geser: ok. that does seem to be what I was looking for
[20:02] <sinzui> mtaylor: Click the status to reveal the form to add a bugw3atch
[20:02] <sinzui> mtaylor: which bug are you viewing?
[20:02] <mtaylor> sinzui: https://bugs.edge.launchpad.net/drizzle/+bug/264124
[20:03] <mtaylor> which already has a "also affects ..."
[20:03] <mtaylor> but now there's a real upstream bug
[20:03] <sinzui> mtaylor: Drizzle is hosted on Launchpad .
[20:04] <mtaylor> yes. but protobuf isn't
[20:04] <mtaylor> (which is where the bug is)
[20:04] <mtaylor> or the upstream bug I want to keep track of
[20:04] <sinzui> mtaylor: you want to add /protobuf using Also affect prooject
[20:05] <mtaylor> gotcha
[20:05] <sinzui> mtaylor: the protobuf (ubuntu) is a package in ubuntu, not the upstream project
[20:06] <mtaylor> sinzui: awesome. ok. that makes sense now
[20:07] <mtaylor> sinzui: and now I'm guessing that google code isn't supported as an upstream bug tracker :(
[20:07] <sinzui> mtaylor: I suspect not, but I'll check with the list of bugtrackers.
[20:09] <sinzui> mtaylor: I think users are using the projects google email address to report a the bug upstream, but there is not syncing of the statues
[20:09] <sinzui> https://bugs.edge.launchpad.net/bugs/bugtrackers
[20:09]  * mtaylor doesn't like google code hosted projects...
[20:09] <mtaylor> sinzui: thanks alot!
[20:58] <radix> is the branch mirror thingy lagging or broken right now?
[20:58] <radix> wait, never mind
[22:04]  * Eluxzen is away: Away
[22:04] <beuno> Eluxzen, please turn off the auto-away message
[22:10] <Eluxzen> done, sorry :-/
[22:11] <beuno> np