Breezy

  1. Bug #412244
  2. Comment #0

Comment 0 for bug 412244

Revision history for this message
Alexander Regueiro (alexreg) wrote : Cannot push to Windows FTP server (Microsoft FTP Service IIS6)

I have been trying to use a remote Windows 2003 server running IIS6/Microsoft FTP Service to host my Bazaar repos, but have encountered a lot of issues getting bzr to play nicely with it. Note that in all cases full permissions are granted to the operating FTP user.

Firstly, simply pushing a local bzr repo to the FTP server (straight "bzr push ftp://.../repo") generates numerous CHMOD errors followed by a message complaining that the branch has been locked a number of seconds ago (which I have verified is earlier during the same push).

FTP Could not set permissions to 448 on /darwindotnet/.bzr. 500 'SITE CHMOD 0700
 /darwindotnet/.bzr': command not understood
FTP Could not set permissions to 448 on /darwindotnet/.bzr/branch-lock. 500 'SIT
E CHMOD 0700 /darwindotnet/.bzr/branch-lock': command not understood
FTP Could not set permissions to 384 on /darwindotnet/.bzr/README. 500 'SITE CHM
OD 0600 /darwindotnet/.bzr/README': command not understood
FTP Could not set permissions to 384 on /darwindotnet/.bzr/branch-format. 500 'S
ITE CHMOD 0600 /darwindotnet/.bzr/branch-format': command not understood
FTP Could not set permissions to 448 on /darwindotnet/.bzr/repository. 500 'SITE
 CHMOD 0700 /darwindotnet/.bzr/repository': command not understood
FTP Could not set permissions to 448 on /darwindotnet/.bzr/repository/lock. 500
'SITE CHMOD 0700 /darwindotnet/.bzr/repository/lock': command not understood
Unable to obtain lock ftp://alexreg-repos@213.175.198.12/darwindotnet/.bzr/repos
itory/lock
held by <email address hidden> on host Alex-PC [process #4040]
locked 4 seconds ago
Will continue to try until 00:34:34, unless you press Ctrl-C
If you're sure that it's not being modified, use bzr break-lock ftp://username@hostname/darwindotnet/.bzr/repository/lock
bzr: interrupted

Immediately executing the specified "bzr break-lock" command usually succeeds; however, a subsequent push results in the same types of errors (CHMOD errors followed by "branch locked"). I have checked that the lack of support for CHMOD in Microsoft FTP Service is *not* the cause of the problem, as commenting out the line in the source that performs the action results in no difference.