Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 482984 - app-backup/duplicity-0.6.22 - Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
Summary: app-backup/duplicity-0.6.22 - Import of duplicity.backends.dpbxbackend Failed...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Tim Harder
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-30 07:09 UTC by Steffen Weber
Modified: 2013-10-19 12:41 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Weber 2013-08-30 07:09:40 UTC 
Since upgrading from duplicity 0.6.21 to duplicity 0.6.22 I get the following warning on various commands. For example with the following command (that intentionally does nothing for demo purposes):

$ duplicity collection-status /dev/null
Import of duplicity.backends.dpbxbackend Failed: No module named dropbox
...

The operation succeeds but the warning is annoying, especially when running duplicity as a cronjob.

I'm not using duplicity's Dropbox backend. Can I somehow disable Dropbox support in duplicity?

Reproducible: Always
Comment 1 Sven Schwyn (svoop) 2013-09-01 18:33:41 UTC 
As a workaround: "--verbosity error" suppresses the warning.
Comment 2 Steffen Weber 2013-09-02 16:42:40 UTC 
Another workaround:

rm /usr/lib64/python2.7/site-packages/duplicity/backends/dpbxbackend.py*
Comment 3 Tim Harder gentoo-dev 2013-10-04 20:58:27 UTC 
This kind of request should be opened on the upstream launchpad tracker.

Basically upstream should switch to checking for modules only when certain backends are used or do silent failures/fallbacks when they're missing.
Comment 4 Tim Harder gentoo-dev 2013-10-19 12:41:36 UTC 
I've added a post install message about optional deps for various backends. If you want the warning messages to go away you should take that request upstream.