duply fetch not compatible with shipped duplicity

Bug #2065559 reported by Bruce Merry
This bug affects 1 person
Affects Status Importance Assigned to Milestone
duply (Ubuntu)

Bug Description

The versions of duply (2.4.1) and duplicity (2.1.4) shipped in 24.04 are not fully compatible. Backing up works, but when running 'duply <profile> fetch <path> <target>' I get the following error:

--- Start running command FETCH at 2024-05-13 08:51:44.314 ---
CommandLineError: Option '--file-to-restore was changed in 2.0.0.
    --file-to-restore to --path-to-restore
    --do-not-restore-ownership to --no-restore-ownership

Enter 'duplicity --help' for help screen.

This seems to be fixed in the current upstream version of duply (2.5.2).

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: duply 2.4.1-1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Mon May 13 08:52:54 2024
InstallationDate: Installed on 2024-04-26 (17 days ago)
InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424.2)
PackageArchitecture: all
SourcePackage: duply
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Bruce Merry (bmerry) wrote :
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.