Dont' report failing backend imports at "WARNING" log level
Bug #1255453 reported by
Gaudenz Steinlin
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Duplicity |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Duplicity tries to import all available backends and reports error messages at warning level if an import fails. This is annoying as some backends (like dropbox) need external proprietary modules to be installed. I think it should be possible to run duplicity from cron with log level warning, as most warning are something you would like to see, but to not get the import warnings on every backup. I propose to reduce the log level for these warnings to INFO. See the attached patch.
Gaudenz
Revision history for this message
| Gaudenz Steinlin (gaudenz-debian) wrote | #1 |
Revision history for this message
| Miro Hrončok (churchyard) wrote | #2 |
| Changed in duplicity: | |
| importance: | Undecided → Medium |
| milestone: | none → 0.7.01 |
| status: | New → Fix Committed |
| Changed in duplicity: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Just to know: Python Dropbox SDK is not proprietary module, it's MIT licensed.
Nevertheless, anything else is true. However, I'd say that if user want's to use Dropbox (i.e. uses dpbx:// in URL), theis should go to ERROR level. But if the user does not, this should not go anywhere (not even to INFO, possibly to DEBUG), as the information is not needed at all.