Recent comments posted to this site:

Just to support Nigel's comment; it's good to be precise and clear about what happens to the files from the start. I've sent a similar suggestion to the mailing list.

Comment by Matthew Mon Feb 10 08:53:44 2014
Yes, git-annex ensures your configured numcopies is met before dropping a file.
Comment by joeyh.name Thu Feb 6 13:00:59 2014
@joeyh.name But if I set numcopies=2 it won't let me drop the file right? I don't think we are mean to directly modify the archive; but if we do would git-annex detect the corruption and discourage us from dropping the other file?
Comment by John Wed Feb 5 06:45:45 2014

The correct old hash value for the empty file SHA256E-s0--e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 is pX/ZJ .

The text describes the old hash value computation incorrectly, because it doesn't mention that 1 bit is skipped between each group of 5 bits. See the sample implementation in display_32bits_as_dir in https://github.com/joeyh/git-annex/blob/master/Locations.hs

Comment by Péter Thu Jan 30 20:45:47 2014
The URLs in question in this case were read-only github https URLs. In any case, my problems are solved by what you've already suggested. I think a less error-sounding response to read-only https repos sounds nice!
Comment by Dav Sun Jan 26 18:51:28 2014
comment 5 8789fc27466714faa5a3a7a6b8ec6e5d
[[!comment Error: unsupported page format txt]]
Tue Jan 21 19:17:12 2014
comment 1 cc9caa5dd22dd67e5c1d22d697096dd2
[[!comment Error: unsupported page format txt]]
Tue Jan 21 19:17:11 2014

TODO: stream the file up/down the pipe, rather than using a temp file

You might want to use chunked transfer, i.e. a series of "EXPECT 65536" followed by that many bytes of binary data and an EOF marker (EXPECT-END or EXPECT 0), instead of escaping three characters (newline, NUL, and the escape prefix) and the additional unnecessary tedious per-character processing that would require.

Comment by Matthias Mon Jan 20 12:22:09 2014

Is there a low cost web hosting solution that would support a public git-annex repo relatively simply with simple access to download the public files.

I figure I could set up an Amazon EC2 micro instance and mount an s3 share, hosting the git-annex remote, but this is a lot of overhead for something that dropbox does with 1 click "share dropbox link"?

Any suggestions would be great!

Comment by Lyle Fri Jan 17 18:59:27 2014

Adding:

'git-annex-shell' =>1,

To the .gitolite.rc file resulted in the "FATAL: suspicous characters loitering about 'git-annex-shell 'configlist' '/~/testing''...

Gitolite source code (https://github.com/sitaramc/gitolite/commit/b1d3c0571409b7c6279fc6a77253c3bc262ab425#diff-79a3701e9e2cee0ea1316451c21a3fec) requires this entry:

'git-annex-shell ua'

Comment by Laura Fri Jan 17 16:14:16 2014
Comments on this page are closed.