Launchpad itself

Bazaar Upgrade Not Working

Asked by Ross Light on 2008-10-24

I've just heard about the Launchpad stacked branch feature, which urges all branches to be upgraded to the new 1.6 format. I want this for my project, zfilenet, so I tried to upgrade the trunk to 1.6 using the command:

bzr upgrade --1.6 lp:zfilenet

Although Bazaar can access the branch correctly, Launchpad gives me a warning message saying:

"RuntimeError: maximum recursion depth exceeded"

And the online source code viewer does not work anymore, giving me a vanilla 500 "Internal Server Error". Any advice would be appreciated.

Question information

Language:: English Edit question

Status:: Solved

For:: Launchpad itself Edit question

Assignee:: No assignee Edit question

Solved by:: Tim Penhey

Solved:: 2008-11-14

Last query:: 2008-11-14

Last reply:: 2008-11-13

Link existing bug

Ross Light (quartz25) said on 2008-10-24:

I forgot to add that the RuntimeError message appears on the branch's Launchpad page at https://code.launchpad.net/~zfilenet/zfilenet/trunk

Tim Penhey (thumper) said on 2008-11-05:

What was the result of the bzr upgrade command?

Did it upgrade without any errors shown?

Tim Penhey (thumper) said on 2008-11-05:

Hit wrong button.

Ross Light (quartz25) said on 2008-11-06:

I don't have the exact log of the command saved, but it did not result in any errors. I also went into SFTP on the trunk to move the backup.bzr directory back to .bzr (after removing the new .bzr, of course), but the Launchpad page is still stuck on the RuntimeError.

Tim Penhey (thumper) said on 2008-11-06:

Hmm.. interesting. I was wondering why the branch was showing as format 6.

Also, the branch that is to be stacked upon I don't believe that it needs to be in format 1.6. Can I get you to push another commit to the trunk branch? I think this will trigger a re-mirror for the branch that is publicly accessible.

Ross Light (quartz25) said on 2008-11-08:

Alright, the problem is now partially solved: the trunk is restored to normality (not upgraded, though) after pushing a commit, but as a test, I also tried to upgrade my 0.1 branch. The 0.1 branch was doing the same thing, so I pushed a couple test commits to it, but now it's complaining that it couldn't install a revision from three months ago. I reconciled the new repository, but nothing.

Should I just go back to the old repository format and hope things get better in the not-too-distant future? :)