I upgraded another one of my git-annex clones. The upgrade worked fine (i.e. according to the manual) on two other clones before, but this time something is different.
After 'git pull' and 'git annex upgrade', which took a long time and seemed to have succeeded, there are no staged changes in git. Instead there are lots of untracked directories in .git-annex. Aside from that, nothing seems to be wrong.
At the time I had git-annex version 0.20110329 and I've been using the SHA1 backend since version 1.
Yes, I agree with Jimmy, it's the same bug. So I'll be closing this one. Please keep us informed how the workaround committed to git-annex yesterday for the case insensativity issue works out. dup --Joey
I'm not sure how this happened, as far as I can see, and based on my testing,
git annex upgrade
does stage the location log files. OTOH, I vaguely rememeber needing to stage some of them when I was doing my own upgrades, but that was a while ago, and I don't remember the details.Your upgrade seems to have gone ok from the file lists you sent, so you can just:
git add .git-annex; git commit
'git add .git-annex' didn't do anything. That's when I noticed that this repository is on a case-insensitive HFS+ file system.
So, if I get this right it's not a new bug, but similar to this situation: git-annex directory hashing problems on osx
Assuming that it was the file system's fault, I went ahead and upgraded yet another clone. That one (on an ext3 file system) had neither staged changes nor left-over untracked files. Everything seems to just have fallen right into place. Is that possible or still weird?