Comment 3 for bug 440838

I am seeing this bug also, but I have found an explanation. I believe that the bug is actually one of failing to report the correct error. I have updated this at #365160 also.

- I am uploading projects to our ftp site, to a path like ftp.oursite.com/client/project
- my client is trying to do this:
    bzr checkout ftp://<email address hidden>:<email address hidden>/client/project
- we get the same errors as seen above, with traceback posted to new bug #440838 because I hadn't yet found this bug#
- the cause in my case is that my client's ftp account defaults to a different parent path, where he first lands in the "client" directory, which looks like / to him, whereas I land in that directory's parent. So the same folder has a different path for him than it does for me. The cure is for him to connect to the path that HE sees, viz.
    bzr checkout ftp://<email address hidden>:<email address hidden>/project

So, I do not think there's a bug, except that bzr is reporting the errors that it is when it SHOULD be reporting that the client doesn't have access to this ftp path.