IndexError: list index out of range
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Duplicity version: 0.6.18
Python version: 2.7.3
OS Distro: Ubuntu 12.04
Filesystem: Linux
I am getting the error output below when using the following TARGET setting and invoking duply status:
TARGET=
(Note: the ftp:// scheme works.)
# duply localhost status
Start duply v1.5.5.4, time is 2012-07-31 16:53:30.
Using profile '/etc/duply/
Using installed duplicity version 0.6.18, python 2.7.3, gpg 1.4.11 (Home: ~/.gnupg), awk 'mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan', bash '4.2.24(1)-release (x86_64-
Autoset found secret key of first GPG_KEY entry '7242A51B' for signing.
Test - Encrypt to 7242A51B & Sign with 7242A51B (OK)
Test - Decrypt (OK)
Test - Compare (OK)
Cleanup - Delete '/tmp/duply.
--- Start running command STATUS at 16:53:31.072 ---
Using archive dir: /root/.
Using backup name: duply_localhost
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Import of duplicity.
Using temporary directory /tmp/duplicity-
Traceback (most recent call last):
File "/usr/bin/
with_tempdir(main)
File "/usr/bin/
fn()
File "/usr/bin/
action = commandline.
File "/usr/lib/
globals.backend = backend.
File "/usr/lib/
return _backends[
File "/usr/lib/
dirs[0]= '/' + dirs[0]
IndexError: list index out of range
16:53:33.717 Task 'STATUS' failed with exit code '30'.
--- Finished state FAILED 'code 30' at 16:53:33.717 - Runtime 00:00:02.645 ---
Changed in duplicity: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Kenneth Loafman (kenneth-loafman) |
milestone: | none → 0.8.20 |
Changed in duplicity: | |
status: | In Progress → Fix Committed |
assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
It seems that this is caused by using an "empty" path on the server. I haven't tried duply, but `duplicity some-dir scp://some.host/' fails with the same error while `duplicity some-dir scp://some. host/path' doesn't.