Push to new branch -> Launchpad: "Not a branch"

Asked by Pauli Virtanen

I cannot successfully push to new branches in Launchpad, (probably) after upgrading BZR from 1.3.1 to 1.6.1 (Ubuntu intrepid).

Previously, I was able to create new branches in Launchpad as follows:

1. Navigate to project page (eg. https://code.launchpad.net/scipy ) and click "Register branch".

2. Fill in branch information and click "Register branch"

3. Launchpad instructs to push to bzr like this: "bzr push lp:~pauli-virtanen/scipy/scipy-refguide", but for me this always produced the error "bzr: ERROR: Target directory lp:~pauli-virtanen/scipy/scipy-refguide already exists, but does not have a valid .bzr directory. Supply --use-existing-dir to push there anyway."

So, I do the initial push using "bzr push lp:~pauli-virtanen/scipy/scipy-refguide --use-existing". This succeeds without errors even now.

4. However, when I navigate to the Launchpad page of the branch, there is a message "Not a branch: "lp:~pauli-virtanen/scipy/scipy-refguide"."

For example like this: https://code.launchpad.net/~pauli-virtanen/scipy/scipy-refguide

5. Curiously enough, I can push and pull from the branch without problems: "bzr branch lp:~pauli-virtanen/scipy/scipy-refguide test" succeeds without errors.

Moreover, "bzr info -v" shows that the branch is of the format

       control: Meta directory format 1
  working tree: Working tree format 4
        branch: Branch format 6
    repository: Packs containing knits without subtree support

which is the same as previously with 1.3.1.

6. What to do now?

Revision history for this message
Paul Hummer (rockstar) said :
#1

Pauli-

  Unfortunately, you discovered a few bugs in Launchpad. First, I would highly suggest not registering a hosted branch. I know the UI is confusing, but it,s better to just push your hosted branches to launchpad. It will automatically register them.

The second issue is that the code import for the scipy project is set as the development focus, so launchpad is trying to "stack" your branch on top of it. Since that code import hasn't succeeded, it ends up breaking that functionality. There are two workarounds for this:

  (1) You can make the code import branch NOT the development focus (although you need rights in the project to do it) or,
  (2) Push the branch as a "junk" branch on launchpad. Junk branches are branches that don't have a project attached to them.

Can you help with this problem?

Provide an answer of your own, or ask Pauli Virtanen for more information if necessary.

To post a message you must log in.