can't push to new remote branch

[displayname]

This is with the latest bzr.dev as of 3/24/2006

First it complains that the 'test' directory doesn't exist on the remote server. However, the remote directory does get created (by bzr, not by me).

Then it complains that the 'test' directory does exist.

C:\documents>mkdir test

C:\documents>cd test

C:\documents\test>bzr init

C:\documents\test>echo "test" > readme.txt

C:\documents\test>bzr add readme.txt
added readme.txt

C:\documents\test>bzr commit
added readme.txt
Committed revision 1.

C:\documents\test>bzr push sftp://user@host/test
Connected (version 2.0, client OpenSSH_3.9p1)
SSH user@host password:
Authentication type not permitted.
Authentication successful!
Secsh channel 1 opened.
bzr: ERROR: No such file: '/test': [Errno 2] No such file

C:\documents\test>bzr push sftp://user@host/test
Connected (version 2.0, client OpenSSH_3.9p1)
SSH user@host password:
Authentication type not permitted.
Authentication successful!
Secsh channel 1 opened.
bzr: ERROR: File exists: 'test': Failure: unable to mkdir

Pushing again gets the 'unable to mkdir' error again.
The remote system is Ubuntu hoary.

[John A Meinel (jameinel)]

In the past, it was difficult to push into directories which were based directly off of the root filesystem.
You probably wanted to do something more like:
bzr push sftp://host/~/test
Which would put the changes into your home directory.
However, this bug should also be fixed once the 'encoding' changes land. It fixes how we handle URLs. The old code path improperly would strip off the last '/' giving sftp://host rather than sftp://host/