Somehow I've lost my S3 remote... git-annex knows it's there, but its not associating it with the git remote in .git/config

$ git-annex whereis pebuilder.iso 
whereis pebuilder.iso (3 copies) 
    3b6fc6f6-3025-11e1-b496-33bffbc0f3ed -- housebackup (external seagate drive on /mnt/back/RemoteStore)
6b1326d8-2abb-11e1-8f43-979159a7f900 -- synology
9b297772-2ab2-11e1-a86f-2fd669cb2417 -- Amazon S3
ok

Amazon S3 is the description from the remote. My .git/config file contains this block:

[remote "cloud"]
  annex-s3 = true
  annex-uuid = 9b297772-2ab2-11e1-a86f-2fd669cb2417
  annex-cost = 70

The UUID matches... But I cannot access it... see below:

[39532:39531 - 0:626] 08:20:38 [vivitron@tronlap:o +3] ~/annex/ISO 
$ git-annex get pebuilder.iso --from=cloud
git-annex: there is no git remote named "cloud"

[39532:39531 - 0:627] 08:20:56 [vivitron@tronlap:o +3] ~/annex/ISO 
$ git-annex get pebuilder.iso --from="Amazon S3"
git-annex: there is no git remote named "Amazon S3"

[39532:39531 - 0:628] 08:21:01 [vivitron@tronlap:o +3] ~/annex/ISO 
$ git-annex get pebuilder.iso --from=9b297772-2ab2-11e1-a86f-2fd669cb2417
git-annex: there is no git remote named "9b297772-2ab2-11e1-a86f-2fd669cb2417"

[39532:39531 - 0:629] 08:21:08 [vivitron@tronlap:o +3] ~/annex/ISO 
$ 

git remote lists "cloud" as a remote:

$ git remote
all
cloud
cs
es3
origin

git-annex status lists S3 support:

$ git-annex status
supported backends: SHA256 SHA1 SHA512 SHA224 SHA384 SHA256E SHA1E SHA512E SHA224E SHA384E WORM URL
supported remote types: git S3 bup directory rsync web hook

I appreciate any help.... I've tested versions 3.20111211, 3.20111231, and 3.20120105

$ git --version
git version 1.7.8.1

done; I've fixed the build system so this confusing thing cannot happen anymore. --Joey

Despite status listing S3 support, your git-annex is actually built with S3stub, probably because it failed to find the necessary S3 module at build time. Rebuild git-annex and watch closely, you'll see "** building without S3 support". Look above that for the error and fix it.

It was certianly a bug that it showed S3 as supported when built without it. I've fixed that.

Comment by http://joey.kitenet.net/ Fri Jan 6 03:04:35 2012
BTW, you'll want to "make clean", since the S3stub hack symlinks a file into place and it will continue building with S3stub even if you fix the problem until you clean.
Comment by http://joey.kitenet.net/ Fri Jan 6 03:08:28 2012
make clean and rebuild worked... Thank you
Comments on this page are closed.