code browsing broken for bzr branch

Asked by Steve Beattie

The bzr branch at is not browsable, attempting to browse it at returns "Internal Server Error". The former page also displays the following error:

  No such file: u'/srv/': [Errno 2] No such file or directory: u'/srv/'

Finally, attempt to bzr branch from it fails:

  $ bzr branch lp:~kees/+junk/cpu-checker
  bzr: ERROR: No such file: '/srv/'

I am able to branch other bzr branches off of launchpad just fine.

Question information

English Edit question
Launchpad itself Edit question
Tim Penhey Edit question
Solved by:
Steve Beattie
Last query:
Last reply:
Revision history for this message
Michael Hudson-Doyle (mwhudson) said :

The branch has become broken somehow. Probably the easiest thing is to get the owner to delete and re-push it.

Revision history for this message
Keith Hughitt (keith-hughitt) said :


I've run into a similar problem with the trunk for a project I'm working on. Attempting to delete the branch in order to then restore it does not work, however, as Launchpad complains:

"This branch cannot be deleted as it has 5 branches sharing revisions. "

Any idea what the cause of this problem is, or how it can be resolved?

Revision history for this message
Keith Hughitt (keith-hughitt) said :

Update: I've decided to open a separate answer thread at since the proposed solution here is now suitable for us.

Revision history for this message
Steve Beattie (sbeattie) said :

In the specific case I reported above, kees ended up deleting that branch and pushed it to a new project + branch at Thanks!

Revision history for this message
Steve Beattie (sbeattie) said :

(Well, it would be nice to know what caused the breakage in the first place, to verify that it doesn't happen again, but I don't think it's reproducible.)

Revision history for this message
Tim Penhey (thumper) said :

Keith, the problem exists due to the way Launchpad shares revisions.

Once a branch has been chosen as a trunk branch, other branches that are pushed to that project will share the revisions with the trunk branch. This does have the side-effect of not allowing the trunk branch to be deleted or the other branches will no longer have the revisions they need.

The simplest solution for this if changing the trunk branch, is to mark the old one as abandoned. This will make it not appear in the default listings, but will keep it around.