duply fetch does not work: "Expected 2 args, got 3"

Bug #1073686 reported by Jens
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
duply (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

According to the documentation, the syntax is

    duply <profile> fetch <src_path> <target_path> [<age>]

But when I use this syntax, duply fails:

   duply systembackup fetch etc/postfix/main.cf postfix-main.cf.14d 14D

Start duply v1.5.5.4, time is 2012-10-31 20:22:39.
Using profile '/root/.duply/systembackup'.
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-pc-linux-gnu)'.
Using configured key 'F05338F2' as signing key.
Test - Encrypt to C2359085 & Sign with F05338F2 (OK)
Test - Decrypt (OK)
Test - Compare (OK)
Cleanup - Delete '/tmp/duply.28916.1351711359_*'(OK)

--- Start running command FETCH at 20:22:40.008 ---
Command line error: Expected 2 args, got 3
Enter 'duplicity --help' for help screen.
20:22:40.104 Task 'FETCH' failed with exit code '2'.
--- Finished state FAILED 'code 2' at 20:22:40.104 - Runtime 00:00:00.096 ---

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: duply 1.5.5.4-1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
Date: Wed Oct 31 20:22:56 2012
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: duply
UpgradeStatus: Upgraded to precise on 2012-05-04 (180 days ago)

Revision history for this message
Jens (jens-launchpad-net) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in duply (Ubuntu):
status: New → Confirmed
Revision history for this message
Terry (terry-kryogenic) wrote :

Actually, as it turns out this issue appears to be fixed in duply 1.5.10.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.