Re: [Duplicity-talk] SCP Issue With duplicity 0.7.01 and rsync.net

[Kenneth Loafman]

Actually, I do.  I'll take a look this afternoon.

What is the advantage of scp over sftp anyway?

...Ken

On Mon, Mar 9, 2015 at 8:38 AM, <address@hidden> wrote:

does anyone of you have a rsync.net account to test out their specific shell? i could do it if you can provide me with a working (temporary) account.


..ede/duply.net


On 09.03.2015 13:55, Kenneth Loafman wrote:
> Hi,
>
> Yes, I can verify that a change was made that fixed an inconsistency in the way scp was handled.  Prior to 0.7.01, scp was treated basically the same as sftp unless you specified the --use-scp flag.  When we did the backend unification, scp became straight scp, sftp became straight sftp, and the --use-scp flag went away.  What this means is that we are now trying to use an interactive shell for scp and it's not working for rsync.net <http://rsync.net>, they are using a different shell, and we'll need to tailor for that.  Changing over to sftp is not really changing what you were doing, you are just telling us to do what we were already doing.
>
> ...Ken
>
>
> On Sun, Mar 8, 2015 at 9:29 PM, Simon Watson <address@hidden <mailto:address@hidden>> wrote:
>
>     Hi,
>
>     Just letting you know I came across an issue with using duplicity 0.7.01 and my rsync.net <http://rsync.net/> account.
>
>     When I used duplicity 0.7.01 with the scp protocol to connect to my rsync.net <http://rsync.net/> account it would fail with:
>     BackendException: scp mkdir failed(2): test: target/remote/directory: unexpected operator
>
>     Thanks to Kenneth Loafman's assistance I was able to resolve this issue.
>     If I changed to using the sftp protocol instead it would work fine. Also if I downgraded to duplicity 0.7.0 or lower it would also work fine. So it seems like a remote command that duplicity 0.7.01 uses with the scp method won't work on rsync.net <http://rsync.net/> accounts.
>
>     Is anyone else able to replicate or confirm this issue?
>
>     Here is the full traceback for the exception I was getting:
>     Backend error detail: Traceback (most recent call last):
>       File "/usr/bin/duplicity", line 1497, in <module>
>         with_tempdir(main)
>       File "/usr/bin/duplicity", line 1491, in with_tempdir
>         fn()
>       File "/usr/bin/duplicity", line 1324, in main
>         action = ""> >       File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 1048, in ProcessCommandLine
>         globals.backend = backend.get_backend(args[0])
>       File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 221, in get_backend
>         obj = get_backend_object(url_string)
>       File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 207, in get_backend_object
>         return factory(pu)
>       File "/usr/lib/python2.7/dist-packages/duplicity/backends/ssh_paramiko_backend.py", line 230, in __init__
>         self.runremote("test -d '%s' || mkdir -p '%s'" % (self.remote_dir, self.remote_dir), False, "scp mkdir ")
>       File "/usr/lib/python2.7/dist-packages/duplicity/backends/ssh_paramiko_backend.py", line 359, in runremote
>         raise BackendException("%sfailed(%d): %s" % (errorprefix, res, chan.recv_stderr(4096)))
>     BackendException: scp mkdir failed(2): test: duplicity/pavlics: unexpected operator
>
>     Cheers,
>     Simon
>     --
>     Moon Buggy Media
>     moonbuggymedia.com <http://moonbuggymedia.com>
>     m. 0410 190 553
>     p. 03 9913 1715
>
>     _______________________________________________
>     Duplicity-talk mailing list
>     address@hidden <mailto:address@hidden>
>     https://lists.nongnu.org/mailman/listinfo/duplicity-talk

>
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk
>

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk