diff options
| author |  sts <sts@web> | 2016-04-26 19:43:20 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2016-04-26 19:43:20 +0000 |
| commit | bfc944aaa900b9f71cda3e268333311346d7f2c1 (patch) | |
| tree | bcadbc71375d2ac1c5bbea78a98d5bd0c2cf233b | |
| parent | 42756b527e78f02b0662fab822f7edc094cd54fa (diff) | |
| -rw-r--r-- | doc/bugs/External_special_remote_broken__63__.mdwn | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/bugs/External_special_remote_broken__63__.mdwn b/doc/bugs/External_special_remote_broken__63__.mdwn index 29b512017..5cf36c17e 100644 --- a/doc/bugs/External_special_remote_broken__63__.mdwn +++ b/doc/bugs/External_special_remote_broken__63__.mdwn @@ -32,9 +32,9 @@ Resuming an upload seems not to work when used with chunking. Here is some sampl There are some steps that do not get in my mind: -1) What is the first "CHECKPRESENT GPGHMACSHA1" good for? The full file including all chunks? -2) Second: Why is git-annex looking for "CHECKPRESENT SHA256E", the plain file (not encrypted)? -3) And now the 'real' problem: git-annex does a "TRANSFER STORE" of some key, but does not first check with CHECKPRESENT if it's there. And indeed, this file is already in the repo, so a "CHECKPRESENT GPGHMACSHA1--48e285fd650dac05eefa328bfbe8efd8a0ca2100" would return true in my case. Therefore it reuploads all my data, which is not so great ;P. +1. What is the first "CHECKPRESENT GPGHMACSHA1" good for? The full file including all chunks? +2. Second: Why is git-annex looking for "CHECKPRESENT SHA256E", the plain file (not encrypted)? +3. And now the 'real' problem: git-annex does a "TRANSFER STORE" of some key, but does not first check with CHECKPRESENT if it's there. And indeed, this file is already in the repo, so a "CHECKPRESENT GPGHMACSHA1--48e285fd650dac05eefa328bfbe8efd8a0ca2100" would return true in my case. Therefore it reuploads all my data, which is not so great ;P. ### What version of git-annex are you using? On what operating system? |