add: Detect when xattrs or perhaps ACLs prevent locking down a file's content
authorJoey Hess <joeyh@joeyh.name>
Fri, 27 Aug 2021 18:33:01 +0000 (14:33 -0400)
committerJoey Hess <joeyh@joeyh.name>
Fri, 27 Aug 2021 18:33:01 +0000 (14:33 -0400)
commita99a84f3420a1d93e4ecd4b8cf30638b48e2758e
tree04c0a1c982f48271ad5f3b137ad006601cb8d9c9
parente17342b2a023d7de6d1a7ae3e4bc746368ca1b63
add: Detect when xattrs or perhaps ACLs prevent locking down a file's content

And fail with an informative message.

I don't think ACLs can prevent removing the write bit, but I'm not sure,
so kept it mentioning them as a possibility.

Should git-annex lock also check if the write bits are able to be removed?
Maybe, but the case I know about with xattrs involves cp -a copying NFS
xattrs, and it's the copy of the file that is the problem. So when locking
a file, I guess it will not be the copy.

Sponsored-by: Dartmouth College's Datalad project
Annex/Ingest.hs
Annex/Perms.hs
CHANGELOG
Command/Fsck.hs
doc/bugs/__34__357_out_of_984_tests_failed__34___on_NFS_lustre_mount/comment_11_541e257ea04d6a7647a337998d79232c._comment
doc/bugs/__34__357_out_of_984_tests_failed__34___on_NFS_lustre_mount/comment_12_80b15bc4e0c8c9ed4680da9408c1d559._comment [new file with mode: 0644]