On 2011-04-06 at 19:12:25, Joey Hess wrote:
> The only way to explain this is git-annex or git-annex-shell being run on
> the remote with an action like "setkey" that updates the location log, but
> without the cd to the repo.
> 
> That does not 100% make sense to me yet with the versions you mention
> (git-annex-shell was introduced in version 0.15, and AFAICS 0.21 should
> interoperate with 0.25), but it seems clear that a version mismatch is
> the cause.

Alright, I was able to install 0.25 on my lucid box as well (after
installing more recent versions of libpcre3 and libgmp10). However, I'm
still getting the same error message:

--------------------------------------------------
copy Rinocerose/Music_Kills_Me/cover.bmp (checking egilsstadir...) (to 
egilsstadir...) 
SHA1:a235a33337d97858e90bea2d76007198343027cf
       30054 100%    0.00kB/s    0:00:00 (xfer#1, to-check=0/1)
fatal: 
'/pub/music/cds/.git-annex/SHA1:a235a33337d97858e90bea2d76007198343027cf.log' 
is outside repository
Command xargs 
["-0","git","--git-dir=/pub/music/cds/.git","--work-tree=/pub/music/cds","add","--"]
 failed; exit code 123
  git-annex: user error (Command xargs 
["-0","git","--git-dir=/pub/music/cds/.git","--work-tree=/pub/music/cds","add","--"]
 failed; exit code 123)
git-annex-shell: 1 failed

sent 30163 bytes  received 31 bytes  20129.33 bytes/sec
total size is 30054  speedup is 1.00
rsync error: syntax or usage error (code 1) at main.c(1060) [sender=3.0.7]

  rsync failed -- run git annex again to resume file transfer
failed
--------------------------------------------------

What I did notice however, is that if I then run the same "git annex copy"
command, it does work the second time:

  git annex copy --to egilsstadir Rinocerose/Music_Kills_Me/

More imporantly though, is this bug report of any use to you or should I be
using the 0.2011 branch of git-annex?

Cheers,
Francois



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to