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

Added a comment: 'git-annex semitrust' seems to solve the issue

Browse source
This commit is contained in:
emanuele.olivetti@47d88ed185b03191e25329caa6fabc2efb3118b2 2016-02-18 21:51:00 +00:00 • committed by admin
parent 8f03c5df12
commit 0edacffc65
1 changed files with 10 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

10
doc/bugs/after_git_annex_add_and_commit__44___git_annex_fsck_fails:_no_known_copies/comment_5_a256583bd9b3815a23cd1ca40d6c19ca._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="emanuele.olivetti@47d88ed185b03191e25329caa6fabc2efb3118b2"
nickname="emanuele.olivetti"
subject="'git-annex semitrust' seems to solve the issue"
date="2016-02-18T21:51:00Z"
content="""
Given that the repository is marked as dead, I tried to bring it back with 'git-annex semitrust laptop' - 'laptop' being the name of the git annex repository on my laptop. Apparently, this action solved the problem. Fsck now works as expected, and I could sync and get the new files on the clone on the external hard disk as usual.
Now, if this the correct solution to my problem, I am wondering how it is possible that the repository was marked as dead. I carefully checked the history of previous command, but no sign of 'git annex dead' o similar. Are there scenarios where a repository is automatically marked as dead?
"""]]