From 777137dc4f7adf1cf5ebc32d7d4bb300ebdb0670 Mon Sep 17 00:00:00 2001 From: Cyberthal Date: Mon, 1 May 2017 22:19:05 +0000 Subject: [PATCH 1/4] Added a comment: PEBKAC --- .../comment_3_79ddc1a3c554efb375b9575687e1ee04._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly/comment_3_79ddc1a3c554efb375b9575687e1ee04._comment diff --git a/doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly/comment_3_79ddc1a3c554efb375b9575687e1ee04._comment b/doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly/comment_3_79ddc1a3c554efb375b9575687e1ee04._comment new file mode 100644 index 0000000000..b44311d105 --- /dev/null +++ b/doc/bugs/cause__58___fake_annex_repo___124___result__58___inflated_numcopies___124___workaround__58___initialize_properly/comment_3_79ddc1a3c554efb375b9575687e1ee04._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Cyberthal" + avatar="http://cdn.libravatar.org/avatar/1c619d65ee07d2343295c8f70f23c9df" + subject="PEBKAC" + date="2017-05-01T22:19:05Z" + content=""" +I was unable to duplicate the problem. Your explanation sounds likely. I shall strive to do better! +"""]] From 38c051751909fe9336468ab7668b3649dc02ca9d Mon Sep 17 00:00:00 2001 From: supernaught Date: Tue, 2 May 2017 21:40:36 +0000 Subject: [PATCH 2/4] --- ...uplicates_honour_multiple_backends__63__.mdwn | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/Can_git-annex-import_--clean-duplicates_honour_multiple_backends__63__.mdwn diff --git a/doc/forum/Can_git-annex-import_--clean-duplicates_honour_multiple_backends__63__.mdwn b/doc/forum/Can_git-annex-import_--clean-duplicates_honour_multiple_backends__63__.mdwn new file mode 100644 index 0000000000..d73c7be990 --- /dev/null +++ b/doc/forum/Can_git-annex-import_--clean-duplicates_honour_multiple_backends__63__.mdwn @@ -0,0 +1,16 @@ +Multiple backends can be stated in the .git/config annex.backends option -- but what is the purpose of the secondary backends? The first is used to add new files, but the second (third, fourth, ...) do not seem to serve any purpose. + +I frequently use git-annex to de-duplicate. The default SHA256E backend has caused issues since filename case is significant, so I have partially switched to SHA256. Now, as far as I can tell, I have to de-duplicate once per possible backend like + + git annex import --clean-duplicates --backend=SHA256E fileA.pdf fileB.PDF ... + git annex import --clean-duplicates --backend=SHA256 fileA.pdf fileB.PDF ... + git annex import --clean-duplicates --backend=SKEIN256 fileA.pdf fileB.PDF ... + ... + +even when my .git/config has annex.backends = "SHA256E SHA256 SKEIN256 ...". In this use case I wouldn't mind hashing the file multiple times. + +Is there a better way to de-duplicate using multiple backends? + +--- + +PS. Thanks for git-annex Joey. I have around 100 annexes and rely on them on a daily basis. From bc835b390a5af8aa19e6c25aa4e541ed3ef71394 Mon Sep 17 00:00:00 2001 From: supernaught Date: Wed, 3 May 2017 05:25:55 +0000 Subject: [PATCH 3/4] --- ...icates_honour_multiple_backends__63__.mdwn | 29 ++++++++++++------- 1 file changed, 19 insertions(+), 10 deletions(-) diff --git a/doc/forum/Can_git-annex-import_--clean-duplicates_honour_multiple_backends__63__.mdwn b/doc/forum/Can_git-annex-import_--clean-duplicates_honour_multiple_backends__63__.mdwn index d73c7be990..a75dd0f1b8 100644 --- a/doc/forum/Can_git-annex-import_--clean-duplicates_honour_multiple_backends__63__.mdwn +++ b/doc/forum/Can_git-annex-import_--clean-duplicates_honour_multiple_backends__63__.mdwn @@ -1,16 +1,25 @@ -Multiple backends can be stated in the .git/config annex.backends option -- but what is the purpose of the secondary backends? The first is used to add new files, but the second (third, fourth, ...) do not seem to serve any purpose. +Is there a better way to de-duplicate in a way that considers multiple backends? -I frequently use git-annex to de-duplicate. The default SHA256E backend has caused issues since filename case is significant, so I have partially switched to SHA256. Now, as far as I can tell, I have to de-duplicate once per possible backend like - - git annex import --clean-duplicates --backend=SHA256E fileA.pdf fileB.PDF ... - git annex import --clean-duplicates --backend=SHA256 fileA.pdf fileB.PDF ... - git annex import --clean-duplicates --backend=SKEIN256 fileA.pdf fileB.PDF ... - ... +Multiple backends can be added to the .git/config annex.backends entry, but what is the purpose of the secondary backends? The first is used when adding new files, but the second (third, fourth, ...) do not seem to serve any purpose. (Or am I missing something?) -even when my .git/config has annex.backends = "SHA256E SHA256 SKEIN256 ...". In this use case I wouldn't mind hashing the file multiple times. +Here's my use case, problem, and a possible solution. I frequently use git-annex to de-duplicate. The default SHA256E backend has caused issues since filename case is significant, so I have partially switched to SHA256. I also occasionally use other backends. Now when I'm given an arbitrary file, as far as I can tell, I have to try de-duplicate once for every possible backend which amounts to something like -Is there a better way to de-duplicate using multiple backends? + for i SHA256E SHA256 SKEIN256 ... ; do + [ -f /tmp/afile.pdf ] && git annex import --clean-duplicates --backend=$i /tmp/afile.pdf + done ---- +even though my .git/config has annex.backends = "SHA256E SHA256 SKEIN256 ...". I was surprised that `--clean-duplicates` does not honour all listed annex.backends. In this case hashing multiple times as needed seems quite reasonable IMO, so adding multiple backend support for `--clean-duplicates` would solve the problem. If you're not keen to modify this existing behaviour, it might be instead sensible to have to opt-in by explicitly specifying all backends to consider, like + + git annex import --clean-duplicates --backends="SHA256E SHA256 SKEIN256" /tmp/afile.pdf + +or + + git annex import --clean-duplicates --backends="$( git config --get annex.backends )" /tmp/afile.pdf + +Moving this loop into git-annex would also allow hashing to be parallelized; it currently cannot because the file could disappear. + +- - - PS. Thanks for git-annex Joey. I have around 100 annexes and rely on them on a daily basis. + +-supernaught From 89d82ba260d41ecb52bdfe82061705c327a58c59 Mon Sep 17 00:00:00 2001 From: Cyberthal Date: Wed, 3 May 2017 16:50:54 +0000 Subject: [PATCH 4/4] Added a comment: Deleting a repository UUID from vicfg --- ...mment_4_688a8473d074830303133ba939438084._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/How_to_delete_a_remote__63__/comment_4_688a8473d074830303133ba939438084._comment diff --git a/doc/forum/How_to_delete_a_remote__63__/comment_4_688a8473d074830303133ba939438084._comment b/doc/forum/How_to_delete_a_remote__63__/comment_4_688a8473d074830303133ba939438084._comment new file mode 100644 index 0000000000..ef7b820bca --- /dev/null +++ b/doc/forum/How_to_delete_a_remote__63__/comment_4_688a8473d074830303133ba939438084._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="Cyberthal" + avatar="http://cdn.libravatar.org/avatar/1c619d65ee07d2343295c8f70f23c9df" + subject="Deleting a repository UUID from vicfg" + date="2017-05-03T16:50:53Z" + content=""" +I followed these instructions, but a single entry for the targeted UUID persists in vicfg. + +For those of us with OCD, this is mildly irksome. Later I might have dead UUID's I actually want to remember, and that bit of spam will always be sitting there at the top of the file. + +However, deleting it is still worthwhile, because otherwise it is repeated in every list of remotes. +"""]]