diff options
| -rw-r--r-- | doc/bugs/git-annex_smudge_fails_on_git_add/comment_3_f1c87d7132b0a335a4761098de8afa6d._comment | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_smudge_fails_on_git_add/comment_3_f1c87d7132b0a335a4761098de8afa6d._comment b/doc/bugs/git-annex_smudge_fails_on_git_add/comment_3_f1c87d7132b0a335a4761098de8afa6d._comment new file mode 100644 index 000000000..a639672b8 --- /dev/null +++ b/doc/bugs/git-annex_smudge_fails_on_git_add/comment_3_f1c87d7132b0a335a4761098de8afa6d._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2016-04-13T16:54:01Z" + content=""" +Hmm, so it is enabled. + +So, I guess that the attempt to use the magic database is somehow failing. +Apparently in a way that doesn't cause git-annex to display a useful error +message. + +Can you check what is the behavior if you run: + + git-annex smudge --clean file < file + +That is supposed to output something on stdout, and exit successfuly. +I guess it's probably exiting nonzero, and any output would be helpful to +know. + +It may also be helpful to strace that command. +"""]] |