Description of problem:
Using duplicity to manage backups to S3, the following error is received:
BackendException: Boto requires a bucket name.
It appears this is an issue with boto and is fixed in a later release.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install duplicity (from epel-testing) and python-boto.
2. Attempt to do a backup to an existing backup on S3.
Backup proceeds normally.
The launchpad bug mentioned above indicates a newer version of boto fixes the problem. I don't know which code change in particular would do the trick as to make it trivial to backport the fox to the 1.0.x version.
If there are no other dependencies on python-boto, it might be worth rebasing to 2.x or at least to where EL6 is.
Note that downgrading to duplicity-0.6.08b-1.el5 is another workaround. Presumably, this version of duplicity doesn't make use of newer features in python-boto.
Either we shouldn't upgrade duplicity, should revert some of the newer changes in duplicity that break compatibility with python-boto 1.0.x, or should upgrade python-boto.
(It looks like you're also the EPEL maintainer of duplicity)
I'm going to prepare a python-boto update for EL-5, soon. If I let you know,
will you be able to test this python-boto update a lot?
Absolutely. Should I test via the latest duplicity you pushed to testing as well?
python-boto-1.9b-6.el5 has been submitted as an update for Fedora EPEL 5.
Please test duplicity-0.6.11-1.el5 and python-boto-1.9b-6.el5 together and
add positive karma to both, if it works for you. Thank you.
python-boto-1.9b-6.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update python-boto'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/python-boto-1.9b-6.el5
python-boto-1.9b-6.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.