I have repo with autoenabled special remote and clone it. Gets enabled, I can obtain data - all good. Now I clone it from that clone to a third location. Special remote isn't autoenabled, while git annex init will do it. Nevertheless I have a git-annex branch and a filled .git/annex before that annex-init call.
What's happening is, that we discover from within clone, that there is that original origin which we add to the clone of the clone as well as origin-2 and try to enable it to figure its UUID. This git-annex enableremote call is done right before we check whether we need to git-annex-init the fresh clone and now it looks already initialized to us, since we find a local git-annex branch and everything. Therefore we don't call git-annex-init.
Trying to fix this by simply change the order of things. A possible need for annex-init should be considered before anything else, I think.
I have repo with autoenabled special remote and clone it. Gets enabled, I can obtain data - all good. Now I clone it from that clone to a third location. Special remote isn't autoenabled, while
git annex initwill do it. Nevertheless I have a git-annex branch and a filled.git/annexbefore thatannex-initcall.What's happening is, that we discover from within
clone, that there is that originaloriginwhich we add to the clone of the clone as well asorigin-2and try to enable it to figure its UUID. Thisgit-annex enableremotecall is done right before we check whether we need togit-annex-initthe fresh clone and now it looks already initialized to us, since we find a local git-annex branch and everything. Therefore we don't callgit-annex-init.Trying to fix this by simply change the order of things. A possible need for
annex-initshould be considered before anything else, I think.