[02:57] <exarkun> bzr commit --fixes lp:... is weird.  do people really use it?
[03:05] <lifeless> exarkun: yes, a lot
[03:05] <lifeless> exarkun: how is it weird?
[03:09] <exarkun> having the trunk branch linked to every closed ticket doesn't seem too useful.  maybe that's just because my project only has one active branch.
[03:10] <exarkun> but the ticket doesn't get closed automatically either, not even set to "Fix Committed"
[03:10] <lifeless> ah
[03:10] <lifeless> so having trunk linked to every bug isn't that useful
[03:10] <lifeless> lp only links the *first* branch to have a given commit to the bugs that commit claims to fix
[03:11] <exarkun> ah
[03:11] <exarkun> so I should use --fixes sooner in the workflow
[03:11] <exarkun> on a branch commit
[03:12] <lifeless> thats the usual use of it, yes.
[03:13] <exarkun> that will help a bit I guess.  how about getting "Fix Committed" set automatically?  am I missing something there?
[03:13] <lifeless> an automated toggle to fix committed when that branch is merged to a series branch is a request feature
[03:13] <exarkun> ah, ok.
[03:14] <lifeless> we haven't really decided if fix committed should mean 'fixed in *a* branch'
[03:14] <lifeless> or 'fixed in this series'
[03:15] <lifeless> there is a proposal on the table to get rid of non-series bugs, which would make this definition easier to come to: if all bugs are for series then fix committed is more clearly useful as 'in the given series branch'
[03:16] <exarkun> I look forward to whatever the solution is :)
[03:20] <exarkun> thanks
[08:13] <micahg> lifeless: I seem to be hitting a timeout on editstatus on an Ubuntu chromium-browser bug
[08:14] <micahg> or benji, can you take a look for me
[08:18]  * micahg wonders if this is fallout from last week still
[09:36] <lifeless> micahg: OOPS code or it didn't happen :P
[10:31] <apw> is it known that it seems to be impossible to nominate more than one series at the same time without getting a timeout
[13:55]  * czajkowski hugs mrevell 
[13:56] <czajkowski> c
[13:56] <mrevell> ah, thanks czajkowski
[16:17] <Ampelbein> hi, I got an oops when trying to change a bug report via email: OOPS-1990INBOUNDEMAILEMAIL1
[16:30] <fta> OOPS-1990BA93
[18:27] <Ampelbein> ok, I think I have a pattern for the oops when submitting per mail. I just got OOPS-1990INBOUNDEMAILEMAIL2. Apparently trying to change a private bug per mail will result in this oops.
[18:28] <Ampelbein> (the error mail isn't helpful btw).
[18:33] <Ampelbein> ok, more precisely, the command "private no" is the reason for the oops.
[18:37] <Ampelbein> I filed bug 796733 about this
[18:45] <Cube``> hey guys
[19:08] <micahg> abentley: can you track down an OOPS for me?
[19:09] <abentley> micahg: sure, what's the oops?
[19:09] <micahg> abentley: OOPS-1990DW32
[19:10] <abentley> micahg: This is a timeout error while recalculating bug heat.
[19:11] <micahg> abentley: ah, is there a bug tracking it? is this fallout from the upgrade last week?
[19:11] <abentley> micahg: https://bugs.launchpad.net/launchpad/+bug/638924
[19:12] <micahg> abentley: umm, that was fixed 4.5 months ago
[19:12] <Cube``> hey guys, when trying to do bzr pull i get this: Permission denied (publickey).
[19:12] <Cube``>  bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.
[19:13] <abentley> micahg: That's what the oops tools associate with this oops.  There may be a different bug, but I have no easy way to find it.
[19:13] <micahg> abentley: see the last comment in that bug :)
[19:13] <abentley> micahg: Yes, I did see that.  See my last statement :-)
[19:14] <micahg> abentley: k, I'll take a look then, thanks
[19:14] <abentley> Cube``: You need to upload your public SSH key to launchpad.  [That's what the (publickey) means]
[19:14] <Cube``> yee
[19:14] <Cube``> got it
[19:14] <Cube``> thanks
[19:14] <Cube``> ssh-add was it
[19:15] <abentley> Cube``: Ah, good.
[20:05] <micahg> abentley: I noticed recently I can't set upstream links in Ubuntu anymore, I guess I haven't tried for a while, but what level privilege is required?
[20:07] <abentley> micahg: There are no restrictions.  Any logged-in user can create these links.  It's possible that the UI has changed, and link isn't where you're expecting, though.
[20:10] <micahg> abentley: what about modifying
[20:10] <abentley> micahg: there are restrictions on modifying.  Let me see...
[20:12] <abentley> micahg: only the packager can change existing links.
[20:12] <micahg> abentley: please define packager?
[20:13] <abentley> micahg: sorry, that's out of my depth.
[20:13] <micahg> hmm, I can change for some, but not others, hmm, will dig a little
[20:14] <micahg> abentley: ah, it seems that the fix for the bug tasks to work for whoever could upload didn't get applied to this, I wonder if there's a bug tracking...
[20:15] <micahg> oh, wait, not true again...
[20:15]  * micahg will wait for someone else, thanks abentley 
[22:41] <micahg> abentley: can we get https://answers.launchpad.net/launchpad/+question/160629 assigned to someone to fix or look into?