diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2013-09-30 16:47:43 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-09-30 16:47:43 +0000 |
| commit | 313e8516b0ee8482c9c4ed1a99e0d3e4b8f1df9a (patch) | |
| tree | 6f4dfe8942d046ce31ff11eb13981d0c11372708 | |
| parent | 6eea809f92f1af6a01ec057aad2a7bd3fb25657e (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment new file mode 100644 index 000000000..1aef52076 --- /dev/null +++ b/doc/bugs/rename:_permission_denied__44___after_direct_mode_switch/comment_1_14cec6448831c67794b62926a03b2fc5._comment @@ -0,0 +1,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.. +"""]] |