Pushing to an FTP server not supporting APPE

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Matthieu Moy wrote:
> Hi,
> 
> I'm trying to use my ISP's webspace to host a bzr archive. It used to
> work with bzr < 0.8, but is now broken :
> 

...

> 
> I suppose this means my ftp server doesn't support "append". There are
> two problems here:
> 
> 1) bzr should have been clear about the diagnosis. I shouldn't have
>    needed to read ~/.bzr.log to understand it.
> 
> 2) It would be nice to have a fallback to PUT when append is not
>    available (but for reasonable performances, it means doing all the
>    operations on a file at the same time).
> 
> Thanks,
> 

We probably should recognize the command unrecognized action, I'm not
sure about falling back to put.

FTP is notorious for giving bad error responses. You get an error code
that is minimally useful (mostly just telling you success/failure), and
then the error message is implementation specific.

I do believe that if you switch your public branch to being a Weave
format, things will work again. Though you lose all the advantages of
knits. But if your server doesn't support APPE, then you've already lost
them.

You can certainly file a bug on 'not recognizing unknown command'.

I know that APPE was part of the FTP spec, but I also know that Medusa
didn't implement it (I had to implement it myself for the bzr selftest
suite).

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEktcbJdeBCYSNAAMRAj1FAJkBCDcLzfGjRbdJKsy0DMmaC2eVrwCg001U
LPtvL6qFEAqREGA5rmr1HcQ=
=rUcg
-----END PGP SIGNATURE-----