From 547a5a8ca8e55b41f7440f28085361e85009e937 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 23 Mar 2021 20:02:19 +0000 Subject: [PATCH 1/7] Added a comment: annex.supportunlocked=false --- ...omment_10_41cf16d6d14d1551c43736f854da3d05._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_10_41cf16d6d14d1551c43736f854da3d05._comment diff --git a/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_10_41cf16d6d14d1551c43736f854da3d05._comment b/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_10_41cf16d6d14d1551c43736f854da3d05._comment new file mode 100644 index 0000000000..1e72209654 --- /dev/null +++ b/doc/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/comment_10_41cf16d6d14d1551c43736f854da3d05._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="annex.supportunlocked=false" + date="2021-03-23T20:02:16Z" + content=""" +\"annex.supportunlocked=false does prevent installing smudge/clean filters\" -- then, do I understand correctly that, if it were a `git-annex-config` setting and `annex.supportunlocked=false` implied `annex.gitaddtoannex=false`, this would prevent inadvertently adding unlocked files? Then, assuming \"typical\" repo usage, it would also prevent inadvertently merging unlocked files, since you'd +have to add them first. + +"""]] From a4cc0c95b423284701d945ae029c0273d175d56a Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 23 Mar 2021 20:11:39 +0000 Subject: [PATCH 2/7] added suggestion for additional git-annex-config settings --- doc/todo/additional_git-annex-config_settings__63__.mdwn | 4 ++++ 1 file changed, 4 insertions(+) create mode 100644 doc/todo/additional_git-annex-config_settings__63__.mdwn diff --git a/doc/todo/additional_git-annex-config_settings__63__.mdwn b/doc/todo/additional_git-annex-config_settings__63__.mdwn new file mode 100644 index 0000000000..670d0133d1 --- /dev/null +++ b/doc/todo/additional_git-annex-config_settings__63__.mdwn @@ -0,0 +1,4 @@ +Should `annex.gitaddtoannex` and `annex.addsmallfiles` be [[`git-annex-config`|git-annex-config]] settings, given that `annex.largefiles`, `annex.dotfiles` and `annex.addunlocked` already are? +Also, [maybe](https://git-annex.branchable.com/todo/Avoid_lengthy___34__Scanning_for_unlocked_files_...__34__/#comment-85cb4d3eac345df7b08a31ea4bd810f6) make `annex.supportunlocked` a `git-annex-config` setting as well. + + From fc598d56e9dc848209e2dc998582492c155bbeac Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 23 Mar 2021 20:13:18 +0000 Subject: [PATCH 3/7] posted forum question re: git-annex-sync and git-annex-config --- doc/forum/git-annex-sync_and_git-annex-config.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/forum/git-annex-sync_and_git-annex-config.mdwn diff --git a/doc/forum/git-annex-sync_and_git-annex-config.mdwn b/doc/forum/git-annex-sync_and_git-annex-config.mdwn new file mode 100644 index 0000000000..28419e8081 --- /dev/null +++ b/doc/forum/git-annex-sync_and_git-annex-config.mdwn @@ -0,0 +1 @@ +How does [[git-annex-sync]] interact with [[git-annex-config]] settings? Does the latest-in-time setting silently take over? From ffccfff6184d2702dec0f7410ed0f800b3410d50 Mon Sep 17 00:00:00 2001 From: tomdhunt Date: Tue, 23 Mar 2021 22:59:07 +0000 Subject: [PATCH 4/7] Added a comment --- .../comment_12_eb732e9c1c44942bc313aa1ab3ff56fc._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/tips/setup_a_public_repository_on_a_web_site/comment_12_eb732e9c1c44942bc313aa1ab3ff56fc._comment diff --git a/doc/tips/setup_a_public_repository_on_a_web_site/comment_12_eb732e9c1c44942bc313aa1ab3ff56fc._comment b/doc/tips/setup_a_public_repository_on_a_web_site/comment_12_eb732e9c1c44942bc313aa1ab3ff56fc._comment new file mode 100644 index 0000000000..1ff98f9616 --- /dev/null +++ b/doc/tips/setup_a_public_repository_on_a_web_site/comment_12_eb732e9c1c44942bc313aa1ab3ff56fc._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="tomdhunt" + avatar="http://cdn.libravatar.org/avatar/02694633d0fb05bb89f025cf779218a3" + subject="comment 12" + date="2021-03-23T22:59:04Z" + content=""" +Okay, setting allowed-ip-addresses worked fine. Thanks much. +"""]] From cc9d6889e25a1c7aad78e42b19080a8c1c1dee94 Mon Sep 17 00:00:00 2001 From: "git-annex@6f13b739194f758abc0b86556b7ce966c1bf3c00" Date: Wed, 24 Mar 2021 09:44:49 +0000 Subject: [PATCH 5/7] --- doc/bugs/borg_not_recognizing_WORM.mdwn | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/borg_not_recognizing_WORM.mdwn diff --git a/doc/bugs/borg_not_recognizing_WORM.mdwn b/doc/bugs/borg_not_recognizing_WORM.mdwn new file mode 100644 index 0000000000..28c57b4c47 --- /dev/null +++ b/doc/bugs/borg_not_recognizing_WORM.mdwn @@ -0,0 +1,15 @@ +### Please describe the problem. +borg special remote is apparently ignoring WORM and URL key content (probably all content without hashes?) + +### What steps will reproduce the problem? +archive a repo containing WORM or URL keys with borg and sync it with git annex like in the example https://git-annex.branchable.com/special_remotes/borg/ + +doing `git annex list --not -i borg` later shows all WORM and URL keys not recognized being in borg + +### What version of git-annex are you using? On what operating system? +git-annex version: 8.20210310 +on NixOS 20.09 + +### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) +Thank you for including borg, and for fixing gcrypt remotes! This is great! + From d4a3465f8b1d78a2e6dfae0d41c5bb537e1747c3 Mon Sep 17 00:00:00 2001 From: "git-annex@6f13b739194f758abc0b86556b7ce966c1bf3c00" Date: Wed, 24 Mar 2021 10:07:30 +0000 Subject: [PATCH 6/7] Added a comment: / vs. % in key --- ..._06f4bb172180825501ffaec60c89c66b._comment | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/bugs/borg_not_recognizing_WORM/comment_1_06f4bb172180825501ffaec60c89c66b._comment diff --git a/doc/bugs/borg_not_recognizing_WORM/comment_1_06f4bb172180825501ffaec60c89c66b._comment b/doc/bugs/borg_not_recognizing_WORM/comment_1_06f4bb172180825501ffaec60c89c66b._comment new file mode 100644 index 0000000000..495cd3883a --- /dev/null +++ b/doc/bugs/borg_not_recognizing_WORM/comment_1_06f4bb172180825501ffaec60c89c66b._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="git-annex@6f13b739194f758abc0b86556b7ce966c1bf3c00" + nickname="git-annex" + avatar="http://cdn.libravatar.org/avatar/198790d74209efe4896fd4cfc37ec2a6" + subject="/ vs. % in key" + date="2021-03-24T10:07:26Z" + content=""" +the substitution of path elements (\"/\" in key to \"%\" in file) seems to be related: + + + $ git annex whereis --key WORM-s781040400-m1574160315--cd%therootsofsepultura.cdr + whereis WORM-s781040400-m1574160315--cd%therootsofsepultura.cdr (0 copies) + The following untrusted locations may also have copies: + 91fd7b0a-493b-408c-aa07-c8520210f6a6 -- [borg] + failed + git-annex: whereis: 1 failed + + $ git annex whereis --key WORM-s781040400-m1574160315--cd/therootsofsepultura.cdr + whereis WORM-s781040400-m1574160315--cd/therootsofsepultura.cdr (1 copy) + 3340887b-e3b3-4a88-9de4-a8b60116cc66 -- [here] + ok + +The first one should be within the second one. +"""]] From 14b846e9faf9b4299d1312b8462af7b7425af0d2 Mon Sep 17 00:00:00 2001 From: "git-annex@6f13b739194f758abc0b86556b7ce966c1bf3c00" Date: Wed, 24 Mar 2021 10:29:16 +0000 Subject: [PATCH 7/7] Added a comment: borg hardlinks --- ...mment_2_47085370d1d8223be4bacb271db63b09._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/borg_not_recognizing_WORM/comment_2_47085370d1d8223be4bacb271db63b09._comment diff --git a/doc/bugs/borg_not_recognizing_WORM/comment_2_47085370d1d8223be4bacb271db63b09._comment b/doc/bugs/borg_not_recognizing_WORM/comment_2_47085370d1d8223be4bacb271db63b09._comment new file mode 100644 index 0000000000..ab03692863 --- /dev/null +++ b/doc/bugs/borg_not_recognizing_WORM/comment_2_47085370d1d8223be4bacb271db63b09._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="git-annex@6f13b739194f758abc0b86556b7ce966c1bf3c00" + nickname="git-annex" + avatar="http://cdn.libravatar.org/avatar/198790d74209efe4896fd4cfc37ec2a6" + subject="borg hardlinks" + date="2021-03-24T10:29:12Z" + content=""" +Also not recognized by git-annex are hardlinks in borg, which show up in `borg list` like + + hr--r--r-- woffs 1000 0 Sun, 2014-08-03 23:04:27 annex-objects/jP/40/SHA256E-s698785--bbe23f87e576cd7ab3a87c0ef8d82c99044515c63a83977d1ac870d82b88f8b4.jpg/SHA256E-s698785--bbe23f87e576cd7ab3a87c0ef8d82c99044515c63a83977d1ac870d82b88f8b4.jpg link to otherdir/sdcard/dcim/Camera/2014-07-28_13-07-42_306.jpg + +"""]]