mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

comment; this is a dup of the windows long filename bug

Browse source
This commit is contained in:
Joey Hess 2015-01-20 15:14:44 -04:00
parent 2e9ff2ea6b
commit ffe0c8e482
2 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend.mdwn
View file

@ -59,3 +59,6 @@ add extras/Extra Content - Reason Drum Takes/Kit Samples/1. Bass Drum mic (BD)/D
# End of transcript or log. # End of transcript or log.
"""]] """]]
> [[done]]; this is a duplicate of the bug referred to in my comment below.
> --[[Joey]]

18
doc/bugs/No_such_file_with_certain_filenames_using_WORM_backend/comment_2_c5645988eaf4f7493d70b6a63f21cdaf._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2015-01-20T19:09:39Z"
content="""
Seems this does not have to do with special characters at all.
Instead, it's a problem with too-long filenames; windows has a crazy short
limit. All explained here:
(http://git-annex.branchable.com/bugs/__34__git-annex:_direct:_1_failed__34___on_Windows)
You could just switch from the WORM backend to one with shorter filenames.
SHA1 might be a god choice.
Or, install git-annex 5.20150113, which includes some changes to use shorter
relative paths to files, and may avoid the problem at least some of the
time. That version also avoids making such long WORM keys.
"""]]