If no-one else can do it first, I'll see if I can fix this sometime,
but I don't know my way around.

I have access to web space which supports sftp but not scp.  If I
`darcs get' from it using the foo@bar:baz respository syntax, darcs
creates an empty repository with no error message about scp failing.

I can make it work by setting DARCS_SCP to `sftp' and I'll send a
patch to the doc to mention that, though I don't know how common a
situation that is.

How do you disable scp while keeping sftp?  I'd like to try to reproduce this bug.

Juliusz Chroboczek <bugs@darcs.net> writes:

> How do you disable scp while keeping sftp?  I'd like to try to
> reproduce this bug.

You'd have to run a server which stops scp but allows sftp.

I actually investigated further and found that what happens is that
you get a message:

  This account is restricted by rssh.
  Allowed commands: sftp rsync

  If you believe this is in error, please contact your system administrator.

and the client returns condition code 0, so it's the equivalent of
using DARCS_SCP=true.  Sorry for not realizing that earlier.  I
haven't figured out yet whether something more sensible can/should
happen when darcs doesn't get any data back from the scp attempt.