I've tried both the snap distribution which is at 0.8.19 and the apt
distribution which is at 0.8.12 and both print the same error.
Everything still works fine so its only a cosmetic issue though.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Interesting. Jesse, that might be due to
https://gitlab.com/duplicity/duplicity/-/merge_requests/31 which
rejiggered how `--exclude-if-present` checks files in order to avoid a
fatal error that occurred in some edge cases. That change was released
in 0.8.17.
Maybe we would need a smarter fix to
It seems this bug has resurfaced? I'm running duplicity 0.8.19 on Ubuntu
20.04.
If I have the file tree:
test
- root
- ...
- other stuff
And run
duplicity --exclude **/root --exclude-if-present .nobakup test
file:///.../backup
duplicity prints a non-fatal error:
Error accessing
It seems that this bug has resurfaced? I'm having the same issue when
using "--exclude-if-present" when using duplicity 0.8.12 on Ubuntu
20.04.2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
This bug was fixed in the package duplicity - 0.7.06-2ubuntu3
---
duplicity (0.7.06-2ubuntu3) zesty; urgency=medium
* d/p/backport-fix-tags-in-locked-folders.patch:
- Fix OSError looking for tag in locked folders with exclude-if-present
(LP: #1620085)
*
** Also affects: duplicity (Ubuntu Zesty)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1620085
Title:
--exclude-if-present gives
** Also affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: duplicity (Ubuntu)
Status: New => Triaged
** Changed in: duplicity (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
7 matches
Mail list logo
