This error message is misleading. This bug is about people NOT having to move the target directory away when a push to launchpad failed. Bzr should be able to recover from this situation.
Currently, the user has to sftp manually into launchpad, then delete the broken .bzr, then push again with --use-existing-dir.
At least, the error message should provide those instructions. At best bzr should be able to just ignore and overwrite an existing broken .bzr when --use-existing-dir is specified.
This error message is misleading. This bug is about people NOT having to move the target directory away when a push to launchpad failed. Bzr should be able to recover from this situation.
Currently, the user has to sftp manually into launchpad, then delete the broken .bzr, then push again with --use-existing-dir.
At least, the error message should provide those instructions. At best bzr should be able to just ignore and overwrite an existing broken .bzr when --use-existing-dir is specified.