summaryrefslogtreecommitdiff
path: root/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment
blob: 1aef52076b3ab157ef788f4d8cb04b25948a6089 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
[[!comment format=mdwn
 username="http://joeyh.name/"
 ip="4.153.8.80"
 subject="comment 1"
 date="2013-09-30T16:47:42Z"
 content="""
I was able to cause a permission denied on `git annex direct` if I made the file in .git/annex/objects be owned by an different user than me. I do not know how that could happen in normal operation of git-annex.


I have made `git annex direct` catch this exception and continue. So you will get a repository that is switched to direct mode, but with one file that is still a symlink to the content, and if you fix the permissions problem, `git annex fsck` will fix it.

I am curious about any details of how your repository got into the original state..
"""]]