[GitHub] [buildstream] gtristan edited a comment on issue #910: Execution rights on an object can corrupt local cache

[GitBox <gi...@apache.org>]

gtristan edited a comment on issue #910:
URL: https://github.com/apache/buildstream/issues/910#issuecomment-1044227541


   > The digest is indeed _only_ based on file content. In master when using buildbox-fuse (strongly recommended on Linux), this is no longer an issue. However, it is still an issue for BuildStream 1.x and also master if hardlinks are used for staging instead of buildbox-fuse.
   
   How is it possible for this to be an issue with hardlinks and not an issue with `buildbox-fuse` ?
   
   As far as I can see, there can be only one digest for a given blob, and if the permissions are not accounted for, then two artifacts can indeed disagree on the permissions for the same blob, ergo there *must* be a bug somewhere, right ?
   
   Perhaps use of buildbox-fuse only changes *which* of the two elements will win and have their say on what the final permission of the file is ?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org