I just ran into the same error when uploading a branch to Launchpad.
When I registered a branch first, then pushed to it with --use-existing-dir, everything seemed fine:
$ bzr push lp:~bzr-upload-devs/bzr-upload/journalled --use-existing-dir
Using default stacking branch /~bzr-upload-devs/bzr-upload/trunk at bzr+ssh://bazaar.launchpad.net/%7Ebzr-upload-devs/bzr-upload/
Created new branch.
$ bzr push
Using saved push location: bzr+ssh://bazaar.launchpad.net/~bzr-upload-devs/bzr-upload/journalled/
No new revisions to push.
I just ran into the same error when uploading a branch to Launchpad.
When I registered a branch first, then pushed to it with --use-existing-dir, everything seemed fine:
$ bzr push lp:~bzr-upload-devs/bzr-upload/journalled --use-existing-dir devs/bzr- upload/ trunk at bzr+ssh: //bazaar. launchpad. net/%7Ebzr- upload- devs/bzr- upload/ //bazaar. launchpad. net/~bzr- upload- devs/bzr- upload/ journalled/
Using default stacking branch /~bzr-upload-
Created new branch.
$ bzr push
Using saved push location: bzr+ssh:
No new revisions to push.
But on Launchpad, the BzrCheckError is displayed, and branching from Launchpad fails. /code.launchpad .net/~bzr- upload- devs/bzr- upload/ journalled
See https:/
The same happens when pushing to a new branch (not previously registered, without --use-existing- dir).
As long as my server isn't down, the branch will be available at http:// encukou. cz/petr/ bzr/buggy- branch if you want it to test something with it.