encountering locked excluded files wrongly considered as an error

--exclude shell_pattern

is documented as "Exclude the file or files matched by shell_pattern. If a directory is matched, then files under that directory will also be matched. See the FILE SELECTION section for more information."

but

duplicity / --include '/home/user1' --exclude '**' file:///media/mateusz/Backup/user1_backup

behaves in unexpected way with two errors reported:

Error accessing possibly locked file /lost+found
Error accessing possibly locked file /root

Given that these folders are matched by shell_pattern it should not matter whatever duplicity may potentially access them - testing whatever file is inaccessible and complaining should be done only for files supposed to be included in backup.

This weird --include --exclude pattern was suggested in http://askubuntu.com/questions/757358/restore-duplicity-archive-with-entire-path-remembered/757608#757608 as solution for a different problem

duplicity --version
duplicity 0.6.23

python --version
Python 2.7.6

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.4 LTS
Release: 14.04
Codename: trusty

ext4 to ext4, the same partition