Hi,
Whenever I do a git annex vicfg (as pasted below) the long gone repo 40da403e-6f74-4705-aae0-433aa656b55e keeps automatically being added back into the configuration. Worse in the webapp this manifests itself as a repository list item that's empty of text (and when buttons are clicked there's a complaint about missing UUIDs).
In addition to removing the lines via git-annex vicfg, I've switched my repository into indirect mode, manually checked out the the git-annex branch and deleted the offending key from the preferred content and group files (it oddly didn't appear in the uuid file). However they keep coming back 
Everything seems to be okay bar this rogue entry which in the web-app irrationally bothers me.
I'm running the very latest git-annex release.
Any thoughts?
Cheers,
Matt.
# git-annex configuration
#
# Changes saved to this file will be recorded in the git-annex branch.
#
# Lines in this file have the format:
# setting uuid = value
# Repository trust configuration
# (Valid trust levels: trusted semitrusted untrusted dead)
# (for mattford63 (matt@descartes.rss.mhs.man.ac.uk:~/current))
trust 88733342-45ef-420f-8f1b-9a5ed8d8e070 = semitrusted
# Repository groups
# (Standard groups: client transfer backup incrementalbackup smallarchive archive source manual public unwanted)
# (Separate group names with spaces)
# (for )
group 40da403e-6f74-4705-aae0-433aa656b55e = client
# (for mattford63 (matt@descartes.rss.mhs.man.ac.uk:~/current))
group 88733342-45ef-420f-8f1b-9a5ed8d8e070 = client
# Repository preferred contents
# (for )
content 40da403e-6f74-4705-aae0-433aa656b55e = standard
# (for mattford63 (matt@descartes.rss.mhs.man.ac.uk:~/current))
content 88733342-45ef-420f-8f1b-9a5ed8d8e070 = standard
git annex dead 40da403e-6f74-4705-aae0-433aa656b55eHi,
I should have mentioned I can't do this either:
I can't quite remember how I removed the remote - it was a whilst back, I think maybe I just edited it out of the git config file....
It seems that the uuid is present in the group.log and preferred-content.log files in the git-annex branch, but not in the uuid.log file. I missed that in your description before. That's weird, don't know how that could happen.
However, when I manually configure things this way, I do not see the repository in the webapp. Which makes sense; uuid.log is the canonical list of repositories.
I guess if I were you I'd manually edit the uuid into uuid.log and then mark it dead.
I tried as you suggested. It worked as far in so far that I was able to mark the repository dead. However, I still see an empty line in the web app so perhaps this odd repo isn't the cause (but I'm deeply suspicious of it). Looking at the HTML source the line in the web-app does not have any UUID at all (see the screen shot here).
What causes the code to add back a previously deleted repository (I vaguely remember something about this being due to the merge algorithm...and why one can only mark repos as deleted)? Why would it only add back to the group and trust logs and not the UUID? The code that generates the web-app HTML must use something else or things in addition to the UUID log?
The logs don't really say much - how can I help debug this further?