Description of problem:
duplicity prints a non-fatal error message.
Version-Release number of selected component (if applicable):
At least once, but it probably happens every time.
Steps to Reproduce:
1. duplicity restore --file-to-restore xxx file:///yyy/ /tmp/zzz/
Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
No message. No news is good news.
I don't think it matters, but the backup was create under Fedora 19.
FWIW, I'm seeing this on the latest F19 package as well. Installing the python-dropbox package makes it go away, so it looks like a missing rpm dep to me.
That's good to know, although I disagree on making that package a
dependency. If the program is modular, it should remain modular, so that
the user doesn't have to install all the modules (for Dropbox, Amazon S3
[I only recently took over this package]
The python modules are pretty small and duplicity isn't based on sub packages that can be added or removed at will and the error when one of the modules aren't installed isn't very gracious so I am going to look at adding all the necessary modules as dependencies which is what other distributions have already done.
Many of them such as python-boto for Amazon s3 services are unconditionally installed regardless of whether that particular user is using that backend, so this isn't really a major change and shouldn't add any real significant size difference to the install. I don't intend to push such a change to the existing release however. Let me know if anyone has other suggestions on handling this.
(In reply to Rahul Sundaram from comment #3)
> Let me know if anyone has other suggestions on handling this.
Why not ask upstream to remove that message or at least make it
friendlier? If I don't need Dropbox, I shouldn't care if that module is
Feel free to file that upstream directly. Thanks!
*** Bug 1052319 has been marked as a duplicate of this bug. ***
As this already depends on python-boto, I'd suggest to add python-dropbox to requires even for current Fedora release to silent this error message.
Later, if someone actually cares, you can solve such dependencies in more proper way.
duplicity-0.6.22-4.fc20 has been submitted as an update for Fedora 20.
duplicity-0.6.22-4.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing duplicity-0.6.22-4.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
duplicity-0.6.22-5.fc20 has been submitted as an update for Fedora 20.
duplicity-0.6.22-5.fc19 has been submitted as an update for Fedora 19.
duplicity-0.6.22-5.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
duplicity-0.6.22-5.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.