[ Eric Evans ]
> Now, is it worth delaying the release of Jessie for that? I lean toward 'no'
as there are two possible workarounds (disabling multipart and installing it via
pip). But it still severely affects the usability of the package.
I wasn't able to replicate this with duplicity (though my backups are
using
a north american region). Can you update this report with the exact
steps to
reproduce, and for posterity sake, what you do to work around it?
This is my backup script:
#!/bin/bash
export AWS_ACCESS_KEY_ID='XXX'
export AWS_SECRET_ACCESS_KEY='XXX'
export AWS_S3_ENDPOINT="s3-eu-central-1.amazonaws.com"
export AWS_S3_BUCKET="XXX"
export S3_DATAPFX="data"
export S3_METAPFX="meta"
export SUBDIR="XXXX"
export ENCRYP_KEY=XXXX
export S3_USE_SIGV4="True"
duplicity \
--full-if-older-than 1M \
--volsize 1024 \
--asynchronous-upload \
--s3-use-multiprocessing --s3-multipart-chunk-size 15 \
--file-prefix-signature ${S3_METAPFX}_${SUBDIR}_ --file-prefix-manifest
${S3_METAPFX}_${SUBDIR}_ --file-prefix-archive ${S3_DATAPFX}_${SUBDIR}_
\
--encrypt-key ${ENCRYP_KEY} \
--include /etc/dovecot/ --include /etc/bind/ --include
/var/lib/spamassassin/ --include /var/mail/virtual/ --include
/etc/postfix/ --exclude "**" / \
s3://${AWS_S3_ENDPOINT}/${AWS_S3_BUCKET}
-----
This spits out errors such as:
Upload 's3://s3-eu-central-1.amazonaws.com/XXX/data_XXXX' failed
(attempt #1, reason: TypeError: argument of type 'int' is not iterable)
Remove the line with "s3-use-multiprocessing" and it will work.
F.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
