[00:23] <micahg> lifeless: https://answers.edge.launchpad.net/launchpad/+question/126078
[00:25] <lifeless> wgrant: https://answers.edge.launchpad.net/launchpad/+question/126078 could you note in there what needs doing to make it trivial for EBUSY losas's :)
[00:29] <wgrant> lifeless: Done.
[00:29] <lifeless> spm: in your queue, low pri-or-hand-to-your-successor-this-evening
[00:29] <lifeless> spm: https://answers.edge.launchpad.net/launchpad/+question/126078
[01:22] <micahg> can we no longer subscribe people to questions?
[01:22] <lifeless> micahg: I don't recall any changes to stop it
[01:22] <lifeless> why?
[01:23] <micahg> becuase I can't do it on the above question
[01:25]  * micahg looks for a bug
[01:26] <bdrung_> i have a question about launchpadlib: if i have a merge proposal object, how do i get the related distribution?
[01:26] <micahg> lifeless: bug 201498
[01:26] <ubot5`> Launchpad bug 201498 in Launchpad Answers "subscribe someone else to a question in Answers (affected: 1, heat: 12)" [Low,Triaged] https://launchpad.net/bugs/201498
[01:27]  * micahg guesses it was never there to being with
[01:34] <lifeless> bdrung_: from the target branch
[01:37] <bdrung_> lifeless: mergeproposal.target_branch.?
[01:39] <lifeless> yeah
[01:39] <bdrung_> lifeless: i don't see a distribution link in https://edge.launchpad.net/+apidoc/1.0.html#branch
[01:39] <bdrung_> am i blind or is there a trick?
[01:40] <lifeless> well it won't be to distro
[01:40] <lifeless> it will be to distro series
[01:40] <lifeless> and it may not be exposed yet
[01:41] <lifeless> nope, there it goes
[01:41] <lifeless> sourcepackage_link
[01:42] <bdrung_> lifeless: mergeproposal.target_branch.sourcepackage.distribution . let's test it
[01:47] <poolie> i just got a gpg rejection mail from launchpad
[01:48] <poolie> even though i wasn't asking it to do anything but add a comment
[01:48] <poolie> is this a known bug?
[01:48] <lifeless> hmm
[01:48] <lifeless> it may be; colin watson filed a bug last week on malone
[02:13] <poolie> ah mine was bug 643170
[02:13] <ubot5`> Launchpad bug 643170 in Launchpad Foundations "mail quoting a gpg-signed mail produces "submit request failure" (affected: 1, heat: 6)" [Undecided,New] https://launchpad.net/bugs/643170
[02:14] <poolie> makes sense when you think about it
[02:46] <ajmitch> is loggerhead a bit broken today?
[02:49] <lifeless> first report we've had
[02:49] <lifeless> why/
[02:50] <ajmitch> OOPS-1724CB184
[02:50] <ubot5`> https://lp-oops.canonical.com/oops.py/?oopsid=1724CB184
[02:50] <ajmitch> I was probably being bad, since I was opening a series of revisions in a new tab
[02:50] <ajmitch> got an oops on each of them
[02:53] <lifeless> try again
[02:54] <ajmitch> still broke, OOPS-1724CB204
[02:54] <ubot5`> https://lp-oops.canonical.com/oops.py/?oopsid=1724CB204
[02:56] <lifeless> spm: can you see of loggerhead has gone south and if so gcore and restrat ?
[02:59] <spm> hrm. it seems perfectly fine. doing zip all.
[03:02] <lifeless> hmm
[03:02] <lifeless> ajmitch: what url ?
[03:02] <ajmitch> http://bazaar.launchpad.net/~indicator-applet-developers/libindicate/trunk/revision/382
[03:02] <lifeless> hmm, that should be trivial
[03:03] <lifeless> the OOPS reports aren't showing up in the oops ui
[03:03] <lifeless> could you do me a favour and file a bug about that on launchpad-foundations
[03:03] <wgrant> *cough* op issue
[03:04] <lifeless> wgrant: *cough* no
[03:04] <ajmitch> file a bug about the OOPS happening, or it not showing up for you?
[03:04] <wgrant> :(
[03:05] <lifeless> wgrant: and even if it was, we're one project, not two projects.
[03:05] <lifeless> ajmitch: about it not showing up.
[03:06] <ajmitch> ok, bug #643182
[03:06] <ubot5`> Launchpad bug 643182 in Launchpad Foundations "OOPS report not showing up in the OOPS UI (affected: 1, heat: 6)" [Undecided,New] https://launchpad.net/bugs/643182
[03:07] <ajmitch> given the number of revisions I tried to view at once, I probably caused some locking to go funny
[03:08] <lifeless> its readonly ;)
[03:08] <lifeless> there's clearly also an issue with the branch, but until we can diagnose..
[03:08] <ajmitch> I won't pretend to know why it fell over in a screaming heap then :)
[06:06] <micahg> lifeless: do you have a document explaining why bi-directional linking with upstream is good?
[06:06] <lifeless> no idea
[06:06] <lifeless> probably
[06:07] <micahg> lifeless: Mozilla's asking why they need it
[06:07] <micahg> mozilla 597786
[06:07] <ubot5`> Mozilla bug 597786 in Bugzilla: Other b.m.o Issues "Ubuntu Launchpad bugspamming b.m.o. Linking to (Ancient|Dupped|Wrong Product) bugs." [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=597786
[06:07] <lifeless> gmb: ^
[06:07]  * micahg thinks he's subscribed already
[06:07] <lifeless> micahg: you have seen the parallel bug in launchpad, right ?
[06:07] <micahg> lifeless: yes
[06:07] <lifeless> good good
[06:07] <micahg> lifeless: but the LP bug seemed a little tamer
[06:08] <lifeless> so it allows closer integration
[06:08] <lifeless> it breaks down the silo and allows something more like federation
[06:08] <lifeless> its new, and there will be tuning steps needed.
[06:08] <lifeless> I'm sure there is a spec /wiki page(s) etc
[06:09] <lifeless> but you'll be just as able as I to find them.
[06:09] <lifeless> there are some contentious angles
[06:09] <lifeless> one is extra noise (though frankly, if this had happened when the bugs were open, as it would normally, not 2 years later), I don't htink anyone would have thought to complain.
[06:10] <lifeless> another is the proxy effect of non bugzilla users being able to comment via LP
[06:10] <micahg> lifeless: what if we just added more recent stuff?
[06:10] <lifeless> but see also http://www.salmon-protocol.org/
[06:10] <micahg> like w/in the last year?
[06:10] <lifeless> which would be lovely to migrate to, but LP needs more of an atom/rss model for that to be within reach.
[06:10] <lifeless> micahg: well it should be caught up now.
[06:11] <lifeless> but talk to gmb; the dude knows.
[06:11] <micahg> lifeless: k, will have to do later if I"m still on or in the morning here
[08:57] <Eliovir> hello
[08:58] <Eliovir> is there a problem with the translation export to bzr branch ?
[08:58] <Eliovir> https://answers.launchpad.net/rosetta/+question/125775
[09:03] <dpm> henninge, ^
[09:45] <henninge> Eliovir, dpm: jtv will be looking into this.
[09:45]  * jtv waves
[09:46] <Eliovir> henninge: thanks
[09:51] <Eliovir> jtv, thanks for finding the bug.
[09:52] <jtv> Eliovir: I haven't found anything yet… we have the error message, but I'm still looking for what might trigger it.
[09:52] <Eliovir> ;) it is "in progress"
[09:52] <jtv> It's not directly triggered by translations code, only indirectly.  So the question is now, where exactly.
[09:53] <Eliovir> so, good luck/good work!
[09:53] <jtv> thanks :)
[09:54] <jtv> Eliovir: do you happen to know whether the template(s) contain a translation credits message?
[09:54] <jtv> (If so, chances are actually that the same error is waiting for us in the translation UI somewhere)
[09:55] <Eliovir> I'm looking
[09:55] <jtv> I'm guessing probably not, but might as well check.
[09:55] <jtv> Thanks.
[09:55] <Eliovir> the only email address is
[09:55] <Eliovir> "Language-Team: eo <translation-team-eo@lists.sourceforge.net>\n"
[09:56] <Eliovir> for example
[09:56] <Eliovir> and
[09:56] <Eliovir> # FULL NAME <EMAIL@ADDRESS>, 2010.
[09:56] <Eliovir> hm, sorry, you told "template"
[09:57] <Eliovir> "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n"
[09:57] <jtv> The translation credits message is a special msgid, typically "translator_credits" or somesuch
[09:57] <jtv> That's where the names and email addresses of the translators are automatically inserted.
[09:58] <jtv> (It's not actually translatable in the Launchpad UI, because the "translation" is automatically generated, but it shows up as one of the messages in the template)
[09:58] <Eliovir> the templates do not contain such message
[09:58] <jtv> OK
[09:58] <Eliovir> thanks for the notice
[10:01] <jtv> ah-hah
[10:02] <jtv> Eliovir: I have a suspect, though it's not actually in the Translations code.  I'll go over to #launchpad-dev to see if I can raise anyone to discuss it with.
[10:03] <jtv> (If you're interested in Launchpad's internal workings, my suspect is a function called get_contact_email_addresses)
[10:05] <jtv> Hrm… no, I clear that one of all charges.  Back to searching.
[10:11] <jtv> Okay, new suspect… I _think_ this can happen if we have no preferred email address for the branch owner.
[10:11] <ricotz> bigjools, hello, i found a build which is stuck - https://edge.launchpad.net/~guido-iodice/+archive/guiodic-testing/+build/1958516
[10:12] <bigjools> ricotz: ok thanks, I need to wait for an admin to reset the builder
[10:12] <Eliovir> jtv: I have a prefered email-address
[10:12] <jtv> Eliovir: but you're not the branch owner, are you?  :)  It's owned by a team.
[10:13] <Eliovir> ;) you're right
[10:13] <jtv> This is a change in the Code app that we developed for this feature.
[10:13] <jtv> (We developed the change for this feature, not the entire Code app :)
[10:14] <Eliovir> jtv: the team does not have an email address 'No contact email'
[10:14] <jtv> 'zacly
[10:14] <Eliovir> jtv: if you need, I can set an email address
[10:15] <jtv> Eliovir: if my guess is right, that'll work around the problem for now.
[10:15] <Eliovir> jtv: do you want I set an email address or you want to change the code ?
[10:17] <jtv> Eliovir: I'll change the code, and hopefully that'll fix the problem before tomorrow's run.
[10:17] <Eliovir> many thx
[10:18] <jtv> But in case I don't make it (I need to design a solution together with people in other timezones), it'd still be useful to set a contact address.  If that fixes your problem before I get my fix in, it'll confirm whether this is really the problem you're hitting.
[10:27] <Eliovir> jtv: ok, so I set it. I nothing occurs tomorrow, I'll come back to tell it.
[11:51] <luboss> hello
[11:54] <luboss> do you think that you could point me to place where I could find how ubuntu repository work? what's the mechanism behind creating distro files. I have found bunch of tools which can do the work, but very curious which of them uses Ubuntu.
[11:54] <luboss> not distro files, sorry. I mean suites - releases
[12:12] <Odd_Bloke> I'd appreciate someone having a look at https://answers.launchpad.net/launchpad-code/+question/123948
[13:14] <maxb> Is there a CHR person?
[13:15] <maxb> If so, please reassign development focus branch on https://edge.launchpad.net/librsvg/main from lp:~vcs-imports/librsvg/old-svn to lp:~vcs-imports/librsvg/master
[13:19] <bdrung_> when will the bzr-builder format 0.3 be supported? i tried to use it, but i got an oops (OOPS-1724ED552)
[13:19] <ubot5`> https://lp-oops.canonical.com/oops.py/?oopsid=1724ED552
[13:25] <allenap> Hi maxb :)
[13:25] <maxb> Hi
[13:26] <allenap> maxb: Done.
[13:26] <maxb> Also, could you public-pastebin bdrung_'s oops?
[13:27] <maxb> thanks
[13:29] <allenap> maxb: Is the traceback enough? I'm not sure if there's sensitive information in the rest of the log.
[13:29] <maxb> traceback should be enough to hazard a guess as to the cause
[13:30] <allenap> maxb: http://pastebin.ubuntu.com/496992/
[13:34] <maxb> bdrung_: So, it looks like a new enough bzr-builder was integrated already, but there's still a check in the Launchpad code which believes 0.2 is the maximum supported.
[13:34] <bdrung_> ok
[13:34] <maxb> It would probably be wise to file a bug against launchpad-code to record that, in which case there's a decent chance it can be taken care of for next month's rollout
[13:36] <wgrant> maxb, bdrung_: There's already a branch in progress to support 0.3.
[13:36] <wgrant> It's even approved.
[13:36] <maxb> ah. I checked for bugs
[13:37] <bdrung_> do you have the bug number?
[13:38] <wgrant> I don't think there is one.
[13:38] <wgrant> https://code.edge.launchpad.net/~abentley/launchpad/allow-0.3/+merge/34478
[13:43] <bdrung_> that links to bug #479705, which has an open launchpad-code task
[13:43] <ubot5`> Launchpad bug 479705 in Launchpad Bazaar Integration "merge subdirs (affected: 4, heat: 22)" [High,Triaged] https://launchpad.net/bugs/479705
[13:44] <wgrant> Ah, I didn't see the -code task.
[14:07] <mgedmin> "OOPS reports - lovely" on https://dev.launchpad.net/ArchitectureGuide tickles my curiosity
[14:07] <mgedmin> do you have any non-private examples?
[15:05] <jml> mgedmin, not that I know of.
[15:05] <jml> mgedmin, there might be some pasted on the public mailing list
[15:21] <james_w> hey, oopses generate by loggerhead!
[15:26] <jcastro> Hi, I need help transferring the smuxi superproject to the right person: https://edge.launchpad.net/smuxi
[15:48] <Odd_Bloke> maxb: I've worked out the problem at https://answers.launchpad.net/launchpad-code/+question/123948.  Should I now file a bug?
[15:48] <Odd_Bloke> maxb: Thanks for all your help, by the way. :)
[15:55] <maxb> *blink* That's. Really. Not. Supposed. To. Happen.
[16:18] <mdeslaur> Can someone help me? I've been trying to unembargo a security update for the past two hours, and LP has been OOPSING every single time. ie: OOPS-1724O1306
[16:18] <ubot5`> https://lp-oops.canonical.com/oops.py/?oopsid=1724O1306
[16:19] <mdeslaur> or this: OOPS-1724L1218
[16:19] <ubot5`> https://lp-oops.canonical.com/oops.py/?oopsid=1724L1218
[17:31] <allenap> mdeslaur: That OOPS is not recorded it seems. Can you check that it's correct?
[17:58] <cjohnston> What's up with bazaar.lp.net?
[17:59] <mdeslaur> allenap: actually, it's bug #641338
[17:59] <ubot5`> Launchpad bug 641338 in Soyuz "timeouts too low for security unembargo (affected: 1, heat: 10)" [High,Triaged] https://launchpad.net/bugs/641338
[18:00] <cjohnston> I'm constantly getting "Sorry, there was a problem connecting to the Launchpad server." when trying to look at code on lp
[18:16] <gege2061> Hello
[18:17] <gege2061> (sorry for my poor english)
[18:17] <gege2061> I have a problem with launchpad: http://bazaar.launchpad.net/~valide/valide/trunk/files
[18:17] <gege2061> And I can't init a new local repository:
[18:18] <gege2061> $ bzr init lp:valide
[18:18] <gege2061> bzr: ERROR: Server sent an unexpected error: ('error', "Cannot lock LockDir(lp-100603472:///%2Bbranch/valide/.bzr/branchlock): File exists: u'/srv/bazaar.launchpad.net/mirrors/00/05/bb/f3/.bzr/branch/lock': [Errno 17] File exists: '/srv/bazaar.launchpad.net/mirrors/00/05/bb/f3/.bzr/branch/lock'")
[18:19] <gege2061> anyone can help me?
[18:40] <maxb> gege2061: Generally, you do not "bzr init" branches on Launchpad. You initialize a new branch locally, and push it to launchpad once you've got something in the branch
[18:43] <gege2061> maxb: indeed, 'bzr branch' is better but doesn't work
[18:43] <maxb> What are you actually trying to do?
[18:43] <gege2061> $ bzr branch lp:valide
[18:44] <gege2061> bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~valide-dev/valide/trunk/": location is a repository.
[18:44] <maxb> right, so what we have here is a stacking issue. Let me investigate...
[18:44] <gege2061> It's probably du to the new team (valide-dev)
[18:44] <gege2061> maxb: thank's
[18:44] <maxb> yes, combine with a launchpad bug
[18:46] <maxb> gege2061: Why is there both ~valide-dev/valide/trunk and ~valide/valide/trunk ? What is the intended end result?
[18:47] <gege2061> I don't know, I created a new team for a mailing-list
[18:48] <gege2061> ~/valide/valide/trunk is the only valid branch
[18:49] <maxb> hmm. I wonder what someone did to create that
[18:49] <maxb> s/that/the other branch, with this messed up stacking relationship
[18:55] <gege2061> strangely my local branche point to ~valide-dev/valide/trunk but I don't ask anything
[18:57] <ahasenack> can I undo a nomination for a release?
[18:57] <maxb> ahasenack: I don't think so
[18:57] <ahasenack> it wasn't acted upon yet, it just says "nominated for maverick by foo"
[18:58] <maxb> gege2061: Ok, so what has happened, is that somehow someone has deleted the branch tip metadata for lp:~valide-dev/valide/trunk, and turned it into a shared repository
[19:01] <jcsackett> freaking internet connection is having issues today.
[19:02] <gege2061> maxb: I have an opportunity to correct it?
[19:02] <maxb> Yes, I'm just trying to figure out how to best describe the process
[19:07] <maxb> gege2061: Please could you run "bzr init lp:~valide-dev/valide/trunk" - I am expecting it to error, but have done something useful by the time it errors
[19:13] <gege2061> maxb: bzr: ERROR: Already a branch: "lp:~valide/valide/trunk".
[19:13] <maxb> you did run exactly what I said? ~valide-*dev* not ~valide?
[19:14] <gege2061> bzr: ERROR: Already a branch: "lp:~valide-dev/valide/trunk".
[19:14] <maxb> gege2061: great, it's improved the situation a bit
[19:15] <maxb> gege2061: ok, so next step is to get things to the point where you can delete one of the trunks
[19:16] <maxb> First, lp:valide/website is marked as sharing storage with it, though it doesn't need to - so run: bzr reconfigure --unstacked lp:valide/website
[19:18] <gege2061> maxb: bzr+ssh://bazaar.launchpad.net/%2Bbranch/valide/website/ is now not stacked
[19:21] <maxb> gege2061: right, now the same for the other branch: bzr reconfigure --unstacked lp:valide
[19:24] <gege2061> maxb: done
[19:25] <maxb> gege2061: Ideally you would now delete ~valide-dev/valide/trunk. However, there's one recipe build attached to it
[19:26] <maxb> You would have to get the owner of the recipe build to delete it first
[19:29] <Azendale> I'm having problems looking at bzr branches. Is that down for scheduled maintenance or something?
[19:30] <gege2061> maxb: On the website, that doesn't work : "This branch cannot be deleted as it has 6  branches sharing revisions."
[19:31] <maxb> gege2061: hmm, looking
[19:31] <maxb> Azendale: not that I know of, but it breaks often. Can you paste an exact URL that breaks?
[19:32] <gege2061> maxb: the command is mut (no message)
[19:34] <maxb> gege2061: Could you try "bzr reconfigure --stacked-on=bzr+ssh://bazaar.launchpad.net/~valide/valide/trunk lp:~valide/valide/0.7" ?
[19:35] <maxb> And if that succeeds, repeat for 0.4 0.5 0.6 0.5.1 0.6.1
[19:35] <gege2061> ok
[19:38] <gege2061> maxb: I have a problem with 0.4 and 0.5:
[19:38] <gege2061> bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~valide/valide/main/".
[19:39] <maxb> ah, I see, stuff has been renamed in the past
[19:40] <maxb> gege2061: Could you download this script, the bzr core command doesn't have the necessary options for fixing this alone: http://j.maxb.eu/~maxb/bzr-set-stacked-url.py
[19:41] <maxb> You can then run "./bzr-set-stacked-url.py lp:~valide/valide/0.4 ~valide-dev/valide/trunk", followed by "bzr reconfigure --stacked-on=bzr+ssh://bazaar.launchpad.net/~valide/valide/trunk lp:~valide/valide/0.4"
[19:41] <gege2061> ok
[19:44] <Azendale> maxb: I went away from the computer for a couple of minutes and when I retryed it it worked. It was http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/4378 if you still wanted to know
[19:45] <maxb> Azendale: ok. Unfortunately Loggerhead is a little flaky in huge deployments. People are working on it, slowly.
[19:46] <gege2061> maxb: bzrlib.errors.PermissionDenied: Permission denied: "Cannot create '~valide-dev'. Only Bazaar branches are allowed."
[19:47] <gege2061> it's not rather ~/valide/valide/trunk ?
[19:47] <maxb> gege2061: oh whoops, I missed the lp: prefix
[19:48] <gege2061> maxb: bzrlib.errors.NotBranchError: Not a branch: "bzr+ssh://bazaar.launchpad.net/~valide-dev/valide/trunk/": location is a repository.
[19:48] <maxb> !
[19:49] <maxb> So somehow lp:~valide-dev/valide/trunk has returned to its earlier broken state
[19:49] <maxb> Try "bzr init lp:~valide-dev/valide/trunk" again
[19:52] <gege2061> maxb: bzr: ERROR: bzr+ssh://bazaar.launchpad.net/~valide-dev/valide/trunk/.bzr/ is not a local path.
[19:53] <maxb> gege2061: ok, it says that, but it did what we need it to. Try the "./bzr-set-stacked-url.py lp:~valide/valide/0.4 lp:~valide-dev/valide/trunk", followed by "bzr reconfigure --stacked-on=bzr+ssh://bazaar.launchpad.net/~valide/valide/trunk lp:~valide/valide/0.4" again
[19:56] <gege2061> maxb: it's ok now
[19:56] <maxb> gege2061: ok, so repeat for 0.5, and then hopefully there will be no branches sharing revisions
[19:59] <gege2061> maxb: done
[19:59] <maxb> just to check, try deleting ~valide-dev/valide/trunk again
[20:02] <gege2061> maxb: "recipe uses this branch"
[20:03] <maxb> ok, so you'll have to get in contact with the owner of the recipe. Once they've deleted it, you should be able to finish this tidy-up
[20:03] <gege2061> Ok it's an old branch I see this the owner for deletion
[20:04] <gege2061> s/this/with/
[20:07] <gege2061> maxb: now that work fine, thank you so much for your help!
[20:07] <maxb> no problem :-)
[20:08] <gege2061> Is my fault? To avoid repeat
[20:12] <maxb> I don't think so. Part of it is a Launchpad bug that it doesn't fix the Bazaar-side metadata when it lets you rename a branch with other branches stacked upon it (this is being worked on). But there was also something very weird with the branch becoming not-a-branch
[21:55] <bsaibes_> Is the staging server up?