Package Details: duplicity-dev 0.8.18-1

Git Clone URL: (read-only, click to copy)
Package Base: duplicity-dev
Description: A utility for encrypted, bandwidth-efficient backups using the rsync algorithm
Upstream URL:
Licenses: GPL
Conflicts: duplicity
Provides: duplicity
Submitter: bertptrs
Maintainer: peippo
Last Packager: peippo
Votes: 1
Popularity: 0.000446
First Submitted: 2019-06-08 20:28
Last Updated: 2021-01-10 11:27

Latest Comments

gamezelda commented on 2020-01-24 21:30

Working fine now!

peippo commented on 2020-01-24 14:10

thanks for noticing, did that last thing yesterday evening, played around with how to include this suffix into the PKGBUILD in the most logical way and then apparently made a mistake (had already downloaded the file, so the source url did not test anymore)

I’ll wait a few days to see what’s going on. I think, though, that the suffix is intended - I’d think it’s connected to this bullet point of the CHANGELOG:

> * Move to single-sourceing the package version
>   - Rework, dist/makedist, dist/makesnap,
>     etc., to get version from duplicity/
>   - Drop dist/relfiles. It was problematic.

gamezelda commented on 2020-01-23 21:24

The source link in the PKGBUILD is broken, the working link is:

The download link on the official site "" is also broken, so I'm not even sure if this "fin1558" suffix was really intented. Maybe better to wait for things to settle...

gamezelda commented on 2020-01-07 15:28

@peippo: Thanks!

peippo commented on 2020-01-07 14:25

@yellowsquid (cont.): I myself had a more general problem with gpg not retrieving PGP keys properly. Configuring a keyserver and standard-resolver for dirmngr resolved this for me. My ~/.gnupg/dirmngr.conf now contains the lines:

keyserver hkp://

peippo commented on 2020-01-07 14:21

@yellowsquid: gpg --recv-keys 9D95920CED4A8D5F8B086A9F8B6F8FF4E654E600

yellowsquid commented on 2020-01-07 10:49

duplicity-0.8.08.tar.gz ... FAILED (unknown public key 330B3C2A96A9EA9C)

==> ERROR: One or more PGP signatures could not be verified!

I've tried searching keyservers for all of: 330B3C2A96A9EA9C 9D95920CED4A8D5F8B086A9F8B6F8FF4E654E600 9946FB5BE18E34E016DAE992330B3C2A96A9EA9C AF953139C1DF9EF3476DE1D58F571BB27A86F4A2 (PPA key)

No results for any of them. What key do I need to add, and what keyserver?

peippo commented on 2020-01-07 09:43

@gamezelda: Thanks for the suggestions. Rather nice to not have to replace the shebang, and to be able to rely on PGP verifications.

gamezelda commented on 2020-01-01 14:28

Hi, I have some small suggestions to improve the PKGBUILD

  • The lines on 'package()' that replace python2 with python seem no longer necessary. I checked and they were useful on the original version you packaged, but not on 0.8.08.

  • The PGP key check seems to work now, for this keyID 9D95920CED4A8D5F8B086A9F8B6F8FF4E654E600 needs to be listed in validpgpkeys. This is how it's done for the stable package on the main repos.

-> NB: If you run a manual gpg --verify it will also list 9946FB5BE18E34E016DAE992330B3C2A96A9EA9C, this does not need to be listed since it is a subkey of the former key (see gpg --list-keys --with-subkey-fingerprint 9D95920CED4A8D5F8B086A9F8B6F8FF4E654E600).