--exclude-if-present gives OSError looking for tag in locked folders
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned | ||
duplicity (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Zesty |
Fix Released
|
Medium
|
Unassigned |
Bug Description
As per:
http://
"I want to send a backup with --exclude-
--include-filelist.
The folder /src/folder is not accessible (mode 750, not owner, not
member of group). This folder is excluded by way of '- **/folder' in
the include filelist. Does the selection process resolve
exclude-
anyway ?
duplicity 0.7.10 (python 2.7.12) fails with
OSError: [Errno 13] Permission denied: '/src/folder/TAG'
duplicity 0.7.06 prints
Error accessing possibly locked file /src/folder
but it isn't a showstopper."
I can confirm this is the case. The reason is that --exclude-
The difference between version 0.7.06 and 0.7.10 is likely caused by my rev 1224:
http://
which fixed Bug #1089131 by removing the readability check when the directory was first scanned and instead moved it to when the file comes to be included by the Select function. The issue here is that the function that deals with --exclude-
Related branches
- Kenneth Loafman: Disapprove
-
Diff: 579 lines (+280/-114) (has conflicts)11 files modifiedCHANGELOG (+34/-14)
Changelog.GNU (+49/-26)
README (+1/-1)
README-REPO (+24/-7)
duplicity/selection.py (+18/-4)
po/duplicity.pot (+4/-0)
testing/__init__.py (+5/-1)
testing/functional/test_selection.py (+130/-49)
testing/gnupg/gpg.conf (+0/-9)
testing/test_code.py (+4/-1)
tox.ini (+11/-2)
- duplicity-team: Pending requested
-
Diff: 229 lines (+148/-53)2 files modifiedduplicity/selection.py (+18/-4)
testing/functional/test_selection.py (+130/-49)
Changed in duplicity: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
assignee: | nobody → Aaron Whitehouse (aaron-whitehouse) |
Changed in duplicity: | |
status: | Confirmed → In Progress |
Changed in duplicity: | |
assignee: | Aaron Whitehouse (aaron-whitehouse) → nobody |
milestone: | none → 0.7.11 |
status: | In Progress → Fix Committed |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
Changed in duplicity (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Update from Richard McGraw on mailing list:
"Since my update to duplicity 0.7.11, I haven't reproduced the problem."
Great, thanks for the update Richard and good to hear it is working for you.