Comments

7 Comments
karma

thanks, works well

BZ#1415177 duplicity-0.7.11-1.el7 is incompatible with gnupg2-2.0.22-4.el7
BZ#1403936 Chromium 55 is available
BZ#1403611 chromium shows error on ssl-sites secured by symantec certificates
User Icon rbu commented & provided feedback on duply-1.11.3-1.el7 5 years ago
karma

@limb, thanks for preparing the update so fast. It does not trigger a deprecation warning with the updated duplicity anymore. Unfortunately, I experienced issue https://sourceforge.net/p/ftplicity/bugs/85/ where 0.10 changed the way credentials need to be provided to the backend.

With the current stable duply, one can do:

TARGET='s3+http://bucket-name/path/'
TARGET_USER='ABCD'
TARGET_PASS='EfGh'

With 0.11, this triggers an error: InvalidUriError: Invalid bucket name in URI "s3://ABCD@bucket-name/path/". One has to do this in the conf file:

TARGET='s3+http://bucket-name/path/'
export AWS_ACCESS_KEY_ID='ABCD'
export AWS_SECRET_ACCESS_KEY='EfGh'

Note that the exported variable names are target-backend-dependent (for Google Cloud, for example, one has to use GS_ACCESS_KEY_ID etc).

BZ#1360193 Duply triggers duplicity deprecation warning when excluding files (since duplicity upgrade)

duply, the duplicity wrapper, now needs an update in EL7 as well. This caused https://bugzilla.redhat.com/show_bug.cgi?id=1360193

BZ#1348391 certbot complains it is old
BZ#1348391 certbot complains it is old

letsencrypt-0.2.0-3.el7 implicitly requires the the psutil update that just got into EPEL7 stable today: FEDORA-EPEL-2015-eead4a588c. letsencrypt-0.2.0-4.el7 has that fixed.