Problem pushing my repository

[HyperQuantum]

On 6/14/07, HyperQuantum <hyperquantum at gmail.com> wrote:
> On 6/13/07, John Arbash Meinel <john at arbash-meinel.com> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > HyperQuantum wrote:
>
> > > I have a similar problem:
> > >
> > > $ bzr push ftp://username@users.telenet.be/fullcompiler
> > > FTP username at users.telenet.be password:
> > > FTP temporary error: 451 /fullcompiler/.bzr/repository/inventory.knit:
> > > Append/Restart not permitted, try again. Retrying.
> > > FTP temporary error: 451 /fullcompiler/.bzr/repository/inventory.knit:
> > > Append/Restart not permitted, try again. Retrying.
> > > FTP temporary error: 451 /fullcompiler/.bzr/repository/inventory.knit:
> > > Append/Restart not permitted, try again. Retrying.
> > > bzr: ERROR: Transport error: FTP temporary error during APPEND
> > > /fullcompiler/.bzr/repository/inventory.knit.Aborting. 451
> > > /fullcompiler/.bzr/repository/inventory.knit: Append/Restart not
> > > permitted, try again

> > Well, I would think the error was moderately clear. Bazaar uses the ftp "APPE"
> > command to append data to an existing file, but your FTP server does not
> > support/allow APPE.
> >
> > It might be something that can be easily enabled in your FTP server (it has
> > been a part of the FTP spec for a long time).
>
> Unfortunately this is the webspace from my ISP, so it's not *my* FTP server.
>
> The error first occurred after Bazaar had already uploaded about 14
> MB, so I doubt if the problem is an unsupported feature in the FTP
> server.

I have done a small test, and it seems that the FTP server also does
not allow a Resume operation:

REST 41

350 Restarting at 41. Send STORE or RETRIEVE to initiate transfer
STOR /ksjbdvcksdv.txt

451 /ksjbdvcksdv.txt: Append/Restart not permitted, try again

I had already contacted my ISP by mail about the append problem, but
the answer I received looked like some standard response and it said
they couldn't (or wouldn't) help me. I am moving to a different ISP
soon anyway, but if I'm unlucky I could have the same problem there.
So a workaround would be very welcome.

Greetings,
H.Q.