Recent comments posted to this site:

dead is the best we can do. The automatic merging used on the git-annex branch tends to re-add lines that are deleted in one repo when merging with another that still has them.
Comment by http://joeyh.name/ Thu May 31 17:01:37 2012

Is there a way to have git-annex completely ignore a repository? I see that the dead command adds the uuid of the repository to trust.log but does not change uuid.log. Is it enough to remove the corresponding line in uuid.log and trust.log?

Comment by http://dlaxalde.myopenid.com/ Thu May 31 14:36:33 2012
If the subdirectory has a .git, then it's a separate git repo, and inside the directory, all git (and git-annex) commands in it will operate on that nested repo and ignore the outside one.
Comment by http://joeyh.name/ Wed May 30 00:54:38 2012
It's strange. I've done some testing on another machine, and this one, and the issue seems to be with adding only certain sub-directories of the git-annex directory. Would it cause an issue with git-annex if a sub-directory was a git repo?
Thanks! Being new here, I didn't want to overstep my boundaries. I've gone ahead and made a small edit and will do so elsewhere as needed.
Thanks, I've fixed that. (You could have too.. this is a wiki ;)
Comment by http://joeyh.name/ Tue May 29 19:10:46 2012
Thanks, I've fixed that. (You could have too.. this is a wiki ;)
Comment by http://joeyh.name/ Tue May 29 19:10:42 2012

git annex sync only syncs git metadata, not file contents, and metadata is not stored on S3, so it does notthing (much).

git annex move . --to s3 or git annex copy . --to s3 is the right way to send the files to S3. I'm not sure why you say it's not working. I'd try it but Amazon is not letting me sign up for S3 again right now. Can you show what goes wrong with copy?

Comment by http://joeyh.name/ Tue May 29 19:09:50 2012
Just noting that the environment variables ANNEX_S3_ACCESS_KEY_ID and ANNEX_S3_SECRET_ACCESS_KEY seem to have been changed to AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
The instructions state ANNEX_S3_ACCESS_KEY_ID and ANNEX_SECRET_ACCESS_KEY but git-annex cannot connect with those constants. git-annex tells me to set both "AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY" instead, which works. This is with Xubuntu 12.04.
Comments on this page are closed.