Package Details: duply 2.3.1-1

Git Clone URL: (read-only, click to copy)
Package Base: duply
Description: A shell front end for duplicity. It manages backup job settings in profiles and allows to batch execute commands.
Upstream URL:
Keywords: duplicity wrapper
Licenses: GPL2
Submitter: Schnouki
Maintainer: SanskritFritz
Last Packager: SanskritFritz
Votes: 79
Popularity: 0.176511
First Submitted: 2009-12-21 11:46 (UTC)
Last Updated: 2021-02-19 14:35 (UTC)

Latest Comments

jose1711 commented on 2020-01-25 12:51 (UTC)

thank you for the quick fix!

SanskritFritz commented on 2020-01-23 14:09 (UTC)

Thanks for the heads-up. Added.

jose1711 commented on 2020-01-23 00:02 (UTC)

could you please install systemd service files into the /usr/lib/systemd/user? thank you, jose

SanskritFritz commented on 2017-09-30 15:38 (UTC)

You're right. I found a better way to patch it. Enjoy!

troyengel commented on 2017-09-30 13:55 (UTC)

Thanks for the heads up, working again! I noticed that the python2 patch is now getting pretty far away from it's original code location, maybe we need to rebuild it for the next release just in case. $0.02! ... ==> Starting build()... patching file duply Hunk #1 succeeded at 544 with fuzz 1 (offset 177 lines). ==> Entering fakeroot environment... ...

SanskritFritz commented on 2017-09-29 11:45 (UTC)

Sourceforge is up, so is duply homepage.

SanskritFritz commented on 2017-09-26 15:02 (UTC)

Duply site is down: The website is temporarily in static offline mode. Only a very limited set of project pages are available until the main website returns to service.

troyengel commented on 2017-09-26 14:56 (UTC)

I think upstream replaced the tarball for package 2.0.3-1 since you released it - I'm getting a MD5SUM mismatch on the downloaded tarball from sourceforge, here's what it's showing right now (2017-09-26): $ md5sum duply_2.0.3.tgz cb530d737c8f2d1023797cf0587b4e05 duply_2.0.3.tgz This doesn't match the commit hash. ( )

SanskritFritz commented on 2016-11-17 08:24 (UTC)

And quickly came 2.0.1. Again thanks for the heads-up!

SanskritFritz commented on 2016-11-14 10:47 (UTC)

Version 2.0 (thanks for the heads-up) and man page added.

SanskritFritz commented on 2015-12-02 22:56 (UTC)

That would create another dependency, but I just might do it nevertheless. Thanks for the heads-up.

justin8 commented on 2015-11-23 00:11 (UTC)

Can you please include the man pages for duply? Running 'duply txt2man' outputs it to stdout.

troyengel commented on 2015-08-26 01:01 (UTC)

FYI if you use Amazon S3 or Google Cloud Storage: the update to duply 1.10+ changes how TARGET_USER and TARGET_PASS work - your backups WILL BREAK upgrading from 1.9.2. You need to do this: 1) Copy TARGET_USER and TARGET_PASS from your .duply/<profile>/conf to a notepad, then comment them out. If you don't comment them out, the new duply 1.10+ will shove them into your bucket name resulting in errors and a python exception. 2) If you don't already, create a wrapper script to run your duply commands so that you can export the variables. It's generally not good security practice to globally export these types of things, limit it to just when you actually run duply. 3) In the wrapper, export the Environment variables for your service before you run duply that are the same values as TARGET_USER and TARGET_PASS, for example: S3: export AWS_ACCESS_KEY_ID=(old TARGET_USER) export AWS_SECRET_ACCESS_KEY=(old TARGET_PASS) Google: export GS_ACCESS_KEY_ID=(old TARGET_USER) export GS_SECRET_ACCESS_KEY=(old TARGET_PASS) At this point it should work as expected (like before). The Changelog and new example template embedded into the code is terrible at describing this breaking change and how to fix it. (you can also put them in ~/.boto if you only have one set of credentials, etc.)

hakunamenta commented on 2014-06-26 15:25 (UTC)

update to version 1.7.4 is possible

SanskritFritz commented on 2014-03-24 10:57 (UTC)

patch is part of base-devel

NSL commented on 2014-03-24 10:47 (UTC)

Please add 'patch' as build depency

SanskritFritz commented on 2013-03-17 12:29 (UTC)

chetwisniewski you're right, sadly a patch is needed. I'll write to the mailing list first asking for help.

chetwisniewski commented on 2013-03-17 01:25 (UTC)

Line 376 looks for python, should be python2

Schnouki commented on 2011-06-13 21:34 (UTC)

Updated and orphaned since I don't use this anymore. Feel free to adopt it if you want!

SanskritFritz commented on 2011-06-06 08:42 (UTC)

For those who use symmetric encription, it is advised to skip version 1.5.5, see here: or use the patched development version mentioned in the bugreport.

t-8ch commented on 2011-05-30 12:28 (UTC)

1.5.5 is out :-)