summaryrefslogtreecommitdiff
path: root/doc/bugs/direct_mode_fails__44___left_in_an_inconsistent_state/comment_1_be1302a006a66e501fe543f3af191fea._comment
blob: c0455b99247b6644d01339c4da2385de89d1dd96 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
[[!comment format=mdwn
 username="http://joeyh.name/"
 ip="209.250.56.2"
 subject="comment 1"
 date="2014-07-10T18:11:22Z"
 content="""
The most likely problem would be if your repository contained annexed objects owned by different user than the one running `git annex direct`.

However, I cannot reproduce this problem:

<pre>
direct foo 
  /home/joey/tmp/r/.git/annex/objects/pV/7j/SHA256E-s30--2754b7f82f6994005b97256273756f14d4abc17165c8819c06c07340d03351fa: setFileMode: permission denied (Operation not permitted)

  leaving this file as-is; correct this problem and run git annex fsck on it
direct  ok
</pre>

Since version 4.20130921, any exception when moving a file to direct mode should be caught like that.

I will need more information to reproduce your bug. Or are you sure you wrote down the right version of git-annex?
"""]]