Package: duplicity Version: 0.6.24-1 Severity: normal To connect to an S3 bucket in Frankfurt, if one reads the documentation, they get the impression they should be using --s3-use-new-style. Not only this doesn't work, but it prevents the (undocumented) workaround to work which is to export S3_USE_SIGV4="True".
Either the documentation should be fixed, including the workaround, or (better?) duplicity should be able to select the correct authentication method for the s3-eu-central-1 endpoint. -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages duplicity depends on: ii libc6 2.19-17 ii librsync1 0.9.7-10 ii python 2.7.9-1 ii python-lockfile 1:0.8-2 Versions of packages duplicity recommends: ii python-oauthlib 0.6.3-1 ii python-paramiko 1.15.1-1 ii python-urllib3 1.9.1-3 ii rsync 3.1.1-3 Versions of packages duplicity suggests: pn lftp <none> ii ncftp 2:3.2.5-1.1 ii python-boto 2.34.0-2 pn python-cloudfiles <none> pn python-gdata <none> pn python-swiftclient <none> pn tahoe-lafs <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
