mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2025-01-07 13:37:57 -04:00
parent 8bc88945e9
commit 7a735c7a4f
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
doc/bugs/git-remote-annex_doesn__39__t_work_on_Windows___40__perms__41__/comment_3_fcd6d9b8a9c569710ffdbd7f9be74352._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2025-01-07T17:29:57Z"
content="""
Only way I can see thawing removing write perms if is you have
core.sharedrepository configured to a particular umask value.
But it certainly is possible that some other part of git-annex removes
write perms.
And in particular the directory special remote does, when content is stored
in it. And you're using that.
So, new theory: The GITBUNDLE object is stored on the directory special
remote. When it later gets pulled from it, the file has readonly attribute
set.
Can you check if the directory special remote contains files with the
readonly attribute set, and see if clearing that attribute prevents the
problem from happening?
"""]]