On 2011-04-07 at 12:10:03, Joey Hess wrote: > Yeah, I had another think over this, and I think it's just a git > incompatability on your remote system actually. git-annex-shell recvkey > is being run, and I see now that it does update the remote repo's > location log, and will try to git add it:
On sid: git version 1.7.4.1 On lucid: git version 1.7.0.4 > Seems like the git on the remote does not work like git does here, > WRT the --git-dir and --work-tree options. > > joey@gnu:/tmp>mkdir repo > joey@gnu:/tmp>cd repo > joey@gnu:/tmp/repo>git init > Initialized empty Git repository in /tmp/repo/.git/ > joey@gnu:/tmp/repo>touch foo > joey@gnu:/tmp/repo>cd / > joey@gnu:/>git --git-dir=/tmp/repo/.git --work-tree=/tmp/repo/ add -- foo > joey@gnu:/> I did the above and it does seem to work fine: francois@egilsstadir:/tmp/repo$ git status # On branch master # # Initial commit # # Changes to be committed: # (use "git rm --cached <file>..." to unstage) # # new file: foo # Anyways, I've got all of my files copied over now (running the same copy command twice seems to have worked). One thing I wasn't expecting though was that after the whole process, I had to commit (with git commit -a) a bunch of changes in the git-annex log files: .git-annex/SHA1:00192b19a836d5a472c6d942837911d016a427da.log .git-annex/SHA1:00fef2995258a28669a70dafec30a828e0a466a7.log ... I'm guessing that it has to do with the second part of the "git annex copy" operation failing... Cheers, Francois -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
