Dear all, I successfuly cloned my annex repo (hosted on gitlab.com) on my windows box (win 7, 64bits), and my data is on an exFat partition.
git annex version is
git-annex version: 6.20160126-g2336107 build flags: Assistant Webapp Pairing Testsuite S3(multipartupload) WebDAV ConcurrentOutput TorrentParser Feeds Quvi key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external
However, when I try to initialize annex on the newly cloned repo fails with the following error:
$ git annex init "repo_win" init repo_win Detected a filesystem without fifo support.
Disabling ssh connection caching.
Detected a crippled filesystem.
Enabling direct mode.
git-annex: .git\annex\objects\c89\57a\SHA256E-s1339658--e7cfebb4ac9c81a6a060506c537b55aed9f13bd02d861d2b341fb8a79ad6e046.png: openTempFile: does not exist (No such file or directory) failed git-annex: init: 1 failed
any hints about this? Thanks in advance. Best regards, Juan
That sounds like this bug: http://git-annex.branchable.com/bugs/__34__git-annex__58___direct__58___1_failed__34___on_Windows/
Windows has some path length issues that come up especially when using git-annex in a deeply nested directory tree. Try cloning the repository to somewhere like c:\ and see if that works around the problem.
Although, the path it's complaining about is relative and only 113 characters long, which should not be long enough to trigger that problem. So, this could be some other problem. I tried cloning a git-annex repo and git annex init did not fail like this, so any information you can provide to help me reproduce the problem would be good.
Hey Joey, Thanks for the answer, I'm trying to reproduce it on a test repo, but I'm having problems with my ssh-key. As soon as I fix it I'll be back with the results. Thanks for your time and effort. Best, Juan
After fixing my ssh key problem I was able to test it appropiately. The path to the .git directory of my repo is 41 characters long (/d/juan/develop/git/xxxxxx_xxxxx_xxxxxxxx), if we add the offending file name: .git\annex\objects\fca\de3\SHA256E-s1312136--a79e30c5121f7843f023abbd36b211a245385b952926760d55a07baf8da1b24d.png\ which is 114 characters long, it adds up to 155 characters. Moving the repo to /d/xxxxxx_xxxxx_xxxxxxxx solved the problem. However, I need it to be on that path, because some other projects use this on a relative path. Is there any way to circumvent this issue?