ENODEV should be added to list of recognized error string
Bug #1858204 reported by
Jose Riha
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Duplicity |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
in `path.py` line
```
if err_string in ["ENOENT", "ENOTDIR", "ELOOP", "ENOTCONN"]:
```
should be extended to
```
if err_string in ["ENOENT", "ENOTDIR", "ELOOP", "ENOTCONN", "ENODEV"]:
```
to cover cases as follows:
* multiple backends are configured via multi:// procotol
* systemd controls access to device (via .automount unit) but at the moment the device is unavailable
* user wants to list/query the backup
duplicity 0.7.18.2
python 2.7.16
debian 10
Revision history for this message
| Kenneth Loafman (kenneth-loafman) wrote | #1 |
| Changed in duplicity: | |
| importance: | Undecided → Medium |
| milestone: | none → 0.8.10 |
| status: | New → In Progress |
| Changed in duplicity: | |
| assignee: | nobody → Kenneth Loafman (kenneth-loafman) |
| Changed in duplicity: | |
| assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
| status: | In Progress → Fix Committed |
| Changed in duplicity: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Please upgrade to the current version of duplicity. This will assure that any bugs fixed since your release are available and may fix your issue.
There are three options:
* Release tarball Install - https:/
* Daily duplicity builds - https:/
* Stable snap builds - “sudo snap install duplicity —classic"
* Latest snap builds - “sudo snap install duplicity —classic —edge"
NOTE: UNinstall duplicity first if it was installed via the distribution repository. For Ubuntu, that would be "sudo apt-get purge duplicity".