Please describe the problem.
On windows, git-annex webapp reports a crash.
On the command-line, I get :
$ git annex fsck fatal: unable to read tree 6d692a016b7d772800ddc3993ffd68fc6aaa21f3 error: invalid object 100644 39e3d739a15dc3ed11a0c324781bf3658ccb933a for '001/e8c/SHA256E-s38500--9017f32c23b4de6363d3e5105bc1c47dd3cd983e471e71e0a9d420daaf0e3e7b.html.log' fatal: git-write-tree: error building trees (merging origin/git-annex into git-annex...) (recording state in git...) git-annex: failed to read sha from git write-tree
Then, I try :
$ git annex repair Running git fsck ... Unpacking all pack files.
git-annex: DeleteFile ".git\objects\pack\pack-c53ea32e9514b6dda95af1d8d879d91d32240d76.idx": permission denied (Accès refusé.) failed git-annex: repair: 1 failed
What steps will reproduce the problem?
Dunno how that got messed up, and what to do now...
What version of git-annex are you using? On what operating system?
latest nightly build (2015/10/19) on win 7
Please provide any additional information below.
# If you can, paste a complete transcript of the problem occurring here.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
# End of transcript or log.
Why can't you read files in your git repository? This must be due to some permissions issue, etc. I know nothing about permissons in Windows, so can't offer any useful advice, beyond the fact that, for git (or git-annex) to work, you need to be able to read all the files in the git repository.
You may also have some form of corruption of the files in the repository. Perhaps your disk is going bad or something?
I don't see any indications of a git-annex bug here.
Windows certianly does cause problems with its short path limits. The SHA512 hash backend is known to not work at all on windows, for example.
However, recent versions of git-annex use relative paths to files, so it shouldn't much matter if they're run in a directory deep in a tree; it'll refer to '.git/foo' rather than 'c:/verylong/path/to/.git/foo'
Also, a long path is certianly not the cause of
Since the path there is relative, is plenty short to not bother Windows's tiny mind, and there's clearly some sort of permission problem preventing this user from modifying this file.