Joey Hess <[email protected]> writes:
> Russ Allbery wrote:

>> I have an annex that's fully synced with its remote.  git annex get
>> returns nothing, successfully, on both ends.  But if I run git annex
>> sync --content (which I would also expect to return nothing
>> successfully), I get a stream of errors like the following:

>> copy Arnold Weinstein/Understanding Literature and Life/01 - Why Literature 
>> -- Civilization and Its Discontents.mp3 (to origin...) git-annex-shell: key 
>> is already present in annex

> Hmm, this could in theory happen when using `git annex copy --to`, in a
> couple of situations where the git-annex branch's location tracking info
> is wrong. There are a variety of situations where the git-annex branch
> can be out of date WRT what's present in the remote repository.

> But, copy --to does an active check to see if the remote has content
> before trying to send it. This narrows any cases where this could happen
> down to essentially races (eg, some other repo copies the same file to
> the remote just before).

> sync --content does not currently do that check, so it's much more
> likely to see that happen (as is git annex copy --fast --to).

The same error does not occur with git annex copy --fast --to, for
whatever it's worth:

wanderer:~/courses$ git annex copy --fast --to work-desktop Arnold\ 
Weinstein/Understanding\ Literature\ and\ Life/01\ -\ Why\ Literature\ --\ 
Civilization\ and\ Its\ Discontents.mp3 
copy Arnold Weinstein/Understanding Literature and Life/01 - Why Literature -- 
Civilization and Its Discontents.mp3 ok

git annex sync thinks all the metadata is in sync:

wanderer:~/courses$ git annex sync
commit  ok
pull work-desktop 
ok
pull origin 
ok
push work-desktop 
Total 0 (delta 0), reused 0 (delta 0)
To ssh://windlord.stanford.edu/srv/courses
 * [new branch]      git-annex -> synced/git-annex
 * [new branch]      master -> synced/master
ok
push origin 
Everything up-to-date
ok

(I thought those new branch pushes might indicate that it fixed something,
but I'm still getting the same errors with git annex sync --content after
running that command.)

-- 
Russ Allbery ([email protected])               <http://www.eyrie.org/~eagle/>


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to