Corrupt git-annex repository

Joey Hess joey at kitenet.net
Fri Oct 28 18:33:15 CEST 2011


Richard Hartmann wrote:
> fatal: ambiguous argument 'git-annex..refs/remotes/origin/git-annex':
> unknown revision or path not in the working tree.

It seems your repository has lost the git-annex branch.

You might try running git fsck to get a better view of the damage,
but it's unlikely to fix anything.

Your best bet is to re-clone the repository from origin, and preserve
the git-annex file contents by moving .git/annex/objects from the broken
repository to the new clone. You can also move .git/config over, to
preserve the annex UUID setting (and any other configs of course). Then
run git annex fsck to make sure its location tracking for that
repository is accurate.

-- 
see shy jo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 828 bytes
Desc: Digital signature
URL: <http://lists.madduck.net/pipermail/vcs-home/attachments/20111028/0c9854e6/attachment.pgp>


More information about the vcs-home mailing list