Launchpad itself

private branch disappeared

Asked by David Graf

Hello
Last night, one of our private branches disappeared (https://code.launchpad.net/~28msec/sausalito/eclipse_tools_36). The really bad thing is: it didn't disappear completely. So, we cannot recreate it. We always get an error like:
bzr: ERROR: Permission denied: "~28msec/sausalito/eclipse_tools_36/": A branch with the name "eclipse_tools_36" already exists for 28msec in sausalito.

Can you please help us quickly? This is a blocking problem for us.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
William Grant (wgrant) said : 		#1

The branch is still there, but you can't see it any more. It looks like 12 of your branches from early 2010 are misconfigured, so ~28msec can't see them. In this particular case, only ~gabipetrovay is subscribed, so only they can see it.

The misconfiguration only became really problematic a few hours ago, when we removed a deprecated behaviour which allowed the branch owner to see the branch even without a subscription. We can subscribe ~28msec to the 12 misconfigured branches to let you access them again, if you like.

This migration is part of our ongoing work to make branch access more transparent and sensible. In a few weeks you'll be able to configure your team to see all of your project's branches, even those to which they're not subscribed. But for now you'll need to subscribe ~28msec, or ask us to.

Revision history for this message
David Graf (davidagraf) said : 		#2

Hello William

Good to know! Thanks!
Can you please subscribe ~28msec to the 12 misconfigured branches? That would be nice!

Thanks
David

Revision history for this message
William Grant (wgrant) said : 		#3

We found a few other projects with branches broken in the same way, and have applied a global fix. You should be able to see all your branches again. Sorry about this -- the migration script erred a little too far on the side of caution in this case.

Can you help with this problem?

Provide an answer of your own, or ask David Graf for more information if necessary.

To post a message you must log in.