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

response

Browse source
This commit is contained in:
Joey Hess 2017-11-07 14:15:54 -04:00
parent b64d19b2c2
commit d97ab71d38
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 20 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/forum/Remote_listed_in_whereis_but_not_in_info/comment_1_85cc355213f894e8c1aeece432de67c3._comment Normal file
View file

@ -0,0 +1,20 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-11-07T18:05:49Z"
content="""
For this to happen, the repository must somehow not be listed in uuid.log,
but the location log for the file includes its uuid. Normally, any time a
git-annex repo is initialized, it gets recorded in uuid.log.
One way that could have happened is if `git annex reinit` was run
with some uuid that was not known in uuid.log. Or, if `git config
annex.uuid` were manually set.
I don't think it's a problem, other than you not knowing where this
repository is -- unless some file is only present in that repository.
You can run `git annex dead` with the uuid as a parameter to mark it dead,
or you could `git annex describe` with the uuid as a parameter to give
it a description.
"""]]