Package: duplicity Version: 0.6.23-1 Severity: normal Hi.
Let's pretend I'm doing a collection-status on an existing backup dir with : $ duplicity collection-status --ssh-backend=pexpect --use-scp --ssh-askpass scp://[email protected]/mnt/backups/whatever Then, it will create a mnt/backups/whatever inside rooot's home on aserver.local which didn't exist already, instead of reporting an error (the URl should be scp://[email protected]//mnt/backups/whatever for /mnt/backups/whatever which does contain an existing backup). collection-status shouldn't do any directory creation and only report failure if the first dir of the path is missing. Instead, as exhibited with -v9, it iterates on creating alll dirs of the path, and then tries to list its contents, which most liely will be empty. Subsequent attempts by the user to debug will most likely too result in trying other duplicity options instead of fixing the wrong path, as there's nothing like 'dir mnt not found' like error. Thanks in advance. Best regards, -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages duplicity depends on: ii libc6 2.18-7 ii librsync1 0.9.7-10 ii python 2.7.6-2 ii python-lockfile 1:0.8-2 Versions of packages duplicity recommends: ii python-oauthlib 0.6.1-1 ii python-paramiko 1.14.0-1 ii python-urllib3 1.8.2-1 ii rsync 3.1.0-3 Versions of packages duplicity suggests: ii lftp 4.5.0-1 ii ncftp 2:3.2.5-1.1 pn python-boto <none> pn python-cloudfiles <none> ii python-gdata 2.0.18+dfsg1-2 pn python-swiftclient <none> pn tahoe-lafs <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
