When issuing a git annex info
, I get:
$ git-annex info
repository mode: indirect
trusted repositories: fatal: Not a git repository: '/home/micas/Music/.git' fatal: Not a git repository: '/home/micas/Music/.git' 0
semitrusted repositories: 3
00000000-0000-0000-0000-000000000001 -- web
85f8a5ea-6278-11e2-9978-ebb59e8f37a2 -- here (Music annex backup)
9aff38f2-6447-11e2-8c89-ef50e6c0ea6c -- backupone (Music annex backupone)
untrusted repositories: 0
transfers in progress: none
available local disk space: 174.28 gigabytes (+1 megabyte reserved)
local annex keys: 5348
local annex size: 25.62 gigabytes
annexed files in working tree: 5374
size of annexed files in working tree: 25.68 gigabytes
bloom filter size: 16 mebibytes (1.1% full)
backend usage:
SHA256: 10692
SHA256E: 30
The troubling part (I think) is trusted repositories: fatal: Not a git repository: '/home/micas/Music/.git' fatal: Not a git repository: '/home/micas/Music/.git' 0
Is there a command I can use to show all the uuid of known remotes? I thought I had marked all remotes pointing to /home/micas/Music/.git as dead
Is there another reason for the output? How can I get trusted repos back to 0?
EDIT:
I removed the folder (was not a git repo at the time of the error) /home/micas/Music
and the error went away.
Yeah, git-annex will skip a repository if its directory doesn't exist, but if the directory exists, it expects it to be a git repository, and will run git commands that use it (to get its config specifically).
The ugly message is doing just what it should; letting you know you have a problem.