From 5f5d90e6f71ed8801cb29b558272b78adef19071 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Thu, 11 Oct 2018 22:22:50 +0000 Subject: [PATCH 01/15] Added a comment: arm64 possible CIs etc --- ..._381c675c33aa4bdedb823700f40dd3a6._comment | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 doc/todo/arm64_autobuilder/comment_1_381c675c33aa4bdedb823700f40dd3a6._comment diff --git a/doc/todo/arm64_autobuilder/comment_1_381c675c33aa4bdedb823700f40dd3a6._comment b/doc/todo/arm64_autobuilder/comment_1_381c675c33aa4bdedb823700f40dd3a6._comment new file mode 100644 index 0000000000..cc599e31e5 --- /dev/null +++ b/doc/todo/arm64_autobuilder/comment_1_381c675c33aa4bdedb823700f40dd3a6._comment @@ -0,0 +1,20 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="arm64 possible CIs etc" + date="2018-10-11T22:22:50Z" + content=""" +According to the great details @mmarmm on github provided in request to support [arm64 for neurodebian](https://github.com/neurodebian/dockerfiles/issues/10#issuecomment-406644418): + +Shippable supports free Arm64 CI/CD and I believe Codefresh does too (both 64-bit and 32-bit for both providers): + +https://blog.shippable.com/shippable-arm-packet-deliver-native-ci-cd-for-arm-architecture +http://docs.shippable.com/platform/tutorial/workflow/run-ci-builds-on-arm/ + +CodeFresh Arm Beta signup: https://goo.gl/forms/aDhlk56jZcblYokj1 + +If you need raw infrastructure the WorksOnArm project will supply full servers if you want to deal with metal: https://github.com/worksonarm/cluster/ + + +I personally haven't looked into any of them yet +"""]] From 3e3b5e62267367e21578f47d3d4a34851765dde5 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Thu, 11 Oct 2018 23:40:56 +0000 Subject: [PATCH 02/15] initial report on the problem of parallel get from exporter remote --- ...al_get_-J_on_exported_S3_bucket_fails.mdwn | 49 +++++++++++++++++++ 1 file changed, 49 insertions(+) create mode 100644 doc/bugs/initial_get_-J_on_exported_S3_bucket_fails.mdwn diff --git a/doc/bugs/initial_get_-J_on_exported_S3_bucket_fails.mdwn b/doc/bugs/initial_get_-J_on_exported_S3_bucket_fails.mdwn new file mode 100644 index 0000000000..2df65e2e76 --- /dev/null +++ b/doc/bugs/initial_get_-J_on_exported_S3_bucket_fails.mdwn @@ -0,0 +1,49 @@ +I was excited to give a shot to https://github.com/OpenNeuroDatasets/ds001544/ which has proper publicurl set etc... unfortunately there is something forbidding immediate parallel get (in below example `-J8` but it is the same with `-J2`). It works on the 2nd try, or if not using -J. Error message states "unknown export location": + +[[!format sh """ +$> git annex version | head -n 1; git clone https://github.com/OpenNeuroDatasets/ds001544/ ; cd ds001544; git annex enableremote s3-PUBLIC; git annex get -J8 . 2>&1 | head -n 20; echo "2nd run"; git annex get -J8 . +git-annex version: 6.20181011+git7-g373c2abc2-1~ndall+1 +Cloning into 'ds001544'... +remote: Enumerating objects: 866, done. +remote: Counting objects: 100% (866/866), done. +remote: Compressing objects: 100% (483/483), done. +remote: Total 866 (delta 144), reused 863 (delta 141), pack-reused 0 +Receiving objects: 100% (866/866), 75.07 KiB | 4.69 MiB/s, done. +Resolving deltas: 100% (144/144), done. + +(merging origin/git-annex into git-annex...) +(recording state in git...) + + Remote origin not usable by git-annex; setting annex-ignore +enableremote s3-PUBLIC ok +(recording state in git...) +get code/convert_sub01_ses01.R (from s3-PUBLIC...) + unknown export location + + Unable to access these remotes: s3-PUBLIC + + Try making some of these repositories available: + 1c66b8f9-34c7-42d1-8e9f-d7bc1982311a -- root@460f24a504cc:/datalad/ds001544 + 837e28c7-9e4a-4792-b1b1-aa69d3430a42 -- [s3-PUBLIC] + a7294efc-f620-445d-8e9d-803b3ec748ef -- s3-PRIVATE + + (Note that these git remotes have annex-ignore set: origin) +failed +get sub-01/ses-01/fmap/sub-01_ses-01_acq-cf0PA_run-03_epi.nii.gz (from s3-PUBLIC...) + unknown export location + + Unable to access these remotes: s3-PUBLIC + + Try making some of these repositories available: + 1c66b8f9-34c7-42d1-8e9f-d7bc1982311a -- root@460f24a504cc:/datalad/ds001544 + 837e28c7-9e4a-4792-b1b1-aa69d3430a42 -- [s3-PUBLIC] +2nd run +get code/convert_sub01_ses02.R (from s3-PUBLIC...) (checksum...) ok +get code/convert_sub01_ses01.R (from s3-PUBLIC...) (checksum...) ok +get sub-01/ses-01/fmap/sub-01_ses-01_acq-cf1PA_run-02_epi.nii.gz (from s3-PUBLIC...) (checksum...) ok +get sub-01/ses-01/func/sub-01_ses-01_task-Stroop_acq-cf0AP_run-03_physio.tsv.gz (from s3-PUBLIC...) (checksum...) ok +... +"""]] + + +[[!meta author=yoh]] From 8505dc50aa534446e2b54b96b4578eee6d32b84e Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 12 Oct 2018 00:06:16 +0000 Subject: [PATCH 03/15] Added a comment --- .../comment_4_957247cc827cc4d2597c01f1f5627d0b._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/news/version_6.20181011/comment_4_957247cc827cc4d2597c01f1f5627d0b._comment diff --git a/doc/news/version_6.20181011/comment_4_957247cc827cc4d2597c01f1f5627d0b._comment b/doc/news/version_6.20181011/comment_4_957247cc827cc4d2597c01f1f5627d0b._comment new file mode 100644 index 0000000000..d55b8d864f --- /dev/null +++ b/doc/news/version_6.20181011/comment_4_957247cc827cc4d2597c01f1f5627d0b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 4" + date="2018-10-12T00:06:16Z" + content=""" +a test failure: https://circleci.com/gh/conda-forge/git-annex-feedstock/116?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link +"""]] From 7acfe6186a99fb8f0ecb37fb367cffdfe5084c4e Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 12 Oct 2018 00:30:06 +0000 Subject: [PATCH 04/15] Added a comment --- .../comment_4_26b9715e49ad0d90dd38d2d718926bfa._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/shorter_keys_through_better_encoding/comment_4_26b9715e49ad0d90dd38d2d718926bfa._comment diff --git a/doc/todo/shorter_keys_through_better_encoding/comment_4_26b9715e49ad0d90dd38d2d718926bfa._comment b/doc/todo/shorter_keys_through_better_encoding/comment_4_26b9715e49ad0d90dd38d2d718926bfa._comment new file mode 100644 index 0000000000..4b960d3e45 --- /dev/null +++ b/doc/todo/shorter_keys_through_better_encoding/comment_4_26b9715e49ad0d90dd38d2d718926bfa._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 4" + date="2018-10-12T00:30:05Z" + content=""" +\"I'm not convinced that git-annex should try to make the symlinks shorter just because some programs have UIs that don't work well with longer symlinks\" -- UI is just one plus of shorter keys. Another is that some systems can't handle long paths; e.g. [[backends]] says don't use *512 or *384 hashes on Windows. Another is that long keys and symlinks increase the amount of data git deals with, which can matter for large repos. Using base64 encoding for hashes would halve the key lengths; not repeating the hash twice in symlinks would give another factor of 2. +"""]] From bfab48efa42babd22a4e5a1e9462265edc8d9088 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 12 Oct 2018 01:04:43 +0000 Subject: [PATCH 05/15] removed --- .../comment_4_26b9715e49ad0d90dd38d2d718926bfa._comment | 8 -------- 1 file changed, 8 deletions(-) delete mode 100644 doc/todo/shorter_keys_through_better_encoding/comment_4_26b9715e49ad0d90dd38d2d718926bfa._comment diff --git a/doc/todo/shorter_keys_through_better_encoding/comment_4_26b9715e49ad0d90dd38d2d718926bfa._comment b/doc/todo/shorter_keys_through_better_encoding/comment_4_26b9715e49ad0d90dd38d2d718926bfa._comment deleted file mode 100644 index 4b960d3e45..0000000000 --- a/doc/todo/shorter_keys_through_better_encoding/comment_4_26b9715e49ad0d90dd38d2d718926bfa._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="Ilya_Shlyakhter" - avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" - subject="comment 4" - date="2018-10-12T00:30:05Z" - content=""" -\"I'm not convinced that git-annex should try to make the symlinks shorter just because some programs have UIs that don't work well with longer symlinks\" -- UI is just one plus of shorter keys. Another is that some systems can't handle long paths; e.g. [[backends]] says don't use *512 or *384 hashes on Windows. Another is that long keys and symlinks increase the amount of data git deals with, which can matter for large repos. Using base64 encoding for hashes would halve the key lengths; not repeating the hash twice in symlinks would give another factor of 2. -"""]] From 070ad189215fd3240251ad3244465a4582ad3dd4 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 12 Oct 2018 01:05:30 +0000 Subject: [PATCH 06/15] Added a comment --- .../comment_4_720012572e1d748bc628fdb17a55a3bd._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/shorter_keys_through_better_encoding/comment_4_720012572e1d748bc628fdb17a55a3bd._comment diff --git a/doc/todo/shorter_keys_through_better_encoding/comment_4_720012572e1d748bc628fdb17a55a3bd._comment b/doc/todo/shorter_keys_through_better_encoding/comment_4_720012572e1d748bc628fdb17a55a3bd._comment new file mode 100644 index 0000000000..ea89550a08 --- /dev/null +++ b/doc/todo/shorter_keys_through_better_encoding/comment_4_720012572e1d748bc628fdb17a55a3bd._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 4" + date="2018-10-12T01:05:30Z" + content=""" +\"I'm not convinced that git-annex should try to make the symlinks shorter just because some programs have UIs that don't work well with longer symlinks\" -- UI is just one plus of shorter keys. Another is that some systems can't handle long paths; e.g. backends says don't use 512 or 384 hashes on Windows. Another is that long keys and symlinks increase the amount of data git deals with, which can matter for large repos. Using base64 encoding for hashes would shorten key lengths by a third; not repeating the hash twice in symlinks would give another factor of 2. +"""]] From c9870c08126f72193b9e37c32c3e9a9b397bb684 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 12 Oct 2018 13:42:07 +0000 Subject: [PATCH 07/15] Added a comment --- ...omment_5_41857b7f25f8a922640378a41574b84d._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/todo/shorter_keys_through_better_encoding/comment_5_41857b7f25f8a922640378a41574b84d._comment diff --git a/doc/todo/shorter_keys_through_better_encoding/comment_5_41857b7f25f8a922640378a41574b84d._comment b/doc/todo/shorter_keys_through_better_encoding/comment_5_41857b7f25f8a922640378a41574b84d._comment new file mode 100644 index 0000000000..97c0b7a8c7 --- /dev/null +++ b/doc/todo/shorter_keys_through_better_encoding/comment_5_41857b7f25f8a922640378a41574b84d._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 5" + date="2018-10-12T13:42:07Z" + content=""" +I was arguing for removal of the KEY-directory/ for a while ;) See e.g. as old as https://github.com/datalad/datalad/issues/32 . There is an issue/discussion on this website too somewhere, couldn't find quickly. +IMHO it is just a \"tech\" problem, i.e. no design principle forbids fixing it. It might though lead to performance issues since the containing directory then needs to be chmod'ed back and forth to introduce changes to the KEY-file under it, but it is probably very similar to what it is now anyways. + +FWIW in DataLad we moved to use MD5E backend as the default to at least somewhat relief the burden of long symlinks. I think we are \"secure\" enough for what we use DataLad here ;) +"""]] From 256ac89bb6589d9ab7e4d739f98b6fe76a9d03a1 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 12 Oct 2018 13:58:05 +0000 Subject: [PATCH 08/15] Added a comment --- .../comment_6_de3f0be0f6b560ca7bb66f7b5c8f0592._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/shorter_keys_through_better_encoding/comment_6_de3f0be0f6b560ca7bb66f7b5c8f0592._comment diff --git a/doc/todo/shorter_keys_through_better_encoding/comment_6_de3f0be0f6b560ca7bb66f7b5c8f0592._comment b/doc/todo/shorter_keys_through_better_encoding/comment_6_de3f0be0f6b560ca7bb66f7b5c8f0592._comment new file mode 100644 index 0000000000..1f7dc490d1 --- /dev/null +++ b/doc/todo/shorter_keys_through_better_encoding/comment_6_de3f0be0f6b560ca7bb66f7b5c8f0592._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 6" + date="2018-10-12T13:58:05Z" + content=""" +Removing KEY/directory could give more savings, but sometimes there is more than one file there (eg key metadata), so the dir makes sense. But the content filename in the dir needn’t repeat the key. But, changing that could be hard. Adding backend variamts with base64-encoded checksums seems possible though? +"""]] From fd8a599a832c40006460c32c9fc1452917003f46 Mon Sep 17 00:00:00 2001 From: "pz63@5ea0a27986d782e467e1ebef6eb31ba440cc58d5" Date: Fri, 12 Oct 2018 15:49:01 +0000 Subject: [PATCH 09/15] Added a comment --- .../comment_2_58c42e1f0dcb827f788ead011dd61981._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/bugs/Missing_backend_extension_in_files_with_long_extensions/comment_2_58c42e1f0dcb827f788ead011dd61981._comment diff --git a/doc/bugs/Missing_backend_extension_in_files_with_long_extensions/comment_2_58c42e1f0dcb827f788ead011dd61981._comment b/doc/bugs/Missing_backend_extension_in_files_with_long_extensions/comment_2_58c42e1f0dcb827f788ead011dd61981._comment new file mode 100644 index 0000000000..6f5a41e1b0 --- /dev/null +++ b/doc/bugs/Missing_backend_extension_in_files_with_long_extensions/comment_2_58c42e1f0dcb827f788ead011dd61981._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="pz63@5ea0a27986d782e467e1ebef6eb31ba440cc58d5" + nickname="pz63" + avatar="http://cdn.libravatar.org/avatar/6268f09b18a71aafa3ad68ecd8a20d50" + subject="comment 2" + date="2018-10-12T15:49:00Z" + content=""" +Makes sense. Thank you very much! +"""]] From 99731fd3d14f3e2f6eaf9150eabe765150f8964d Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 12 Oct 2018 20:17:20 +0000 Subject: [PATCH 10/15] Added a comment --- .../comment_9_7fb2f20ff86ad546a8c491714d3bf39c._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/internals/comment_9_7fb2f20ff86ad546a8c491714d3bf39c._comment diff --git a/doc/internals/comment_9_7fb2f20ff86ad546a8c491714d3bf39c._comment b/doc/internals/comment_9_7fb2f20ff86ad546a8c491714d3bf39c._comment new file mode 100644 index 0000000000..53900116fb --- /dev/null +++ b/doc/internals/comment_9_7fb2f20ff86ad546a8c491714d3bf39c._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 9" + date="2018-10-12T20:17:19Z" + content=""" +What are *.rmet files? +"""]] From 209184a798dddd042d1a23dd22a3870b8848a98d Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 12 Oct 2018 20:28:25 +0000 Subject: [PATCH 11/15] added details about the URL backend --- doc/backends.mdwn | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/doc/backends.mdwn b/doc/backends.mdwn index e7acd8ed98..d69701b95e 100644 --- a/doc/backends.mdwn +++ b/doc/backends.mdwn @@ -46,7 +46,12 @@ content of an annexed file remains unchanged. files or slow systems. * `URL` -- This is a key that is generated from the url to a file. It's generated when using eg, `git annex addurl --fast`, when the file - content is not available for hashing. + content is not available for hashing. The key may not contain the full + URL; for long URLs, part of the URL may be represented by a checksum. + The URL key may contain `&` characters; be sure to quote the key if + passing it to a shell script. The URL-backend key is distinct from URLs/URIs + that may be attached to a key (from any backend) indicating the key's location + on the web or in one of [[special_remotes]]. If you want to be able to prove that you're working with the same file contents that were checked into a repository earlier, you should avoid @@ -75,3 +80,5 @@ in `.gitattributes`: * annex.backend=WORM *.mp3 annex.backend=SHA256E *.ogg annex.backend=SHA256E + +See also: [[git-annex-examinekey]] From 9e845405f299bb150deed731907089d75ee01ab6 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 12 Oct 2018 20:33:16 +0000 Subject: [PATCH 12/15] added a note about git-annex-examinekey and the URL backend --- doc/git-annex-examinekey.mdwn | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/git-annex-examinekey.mdwn b/doc/git-annex-examinekey.mdwn index 83baa56676..739d2fd90f 100644 --- a/doc/git-annex-examinekey.mdwn +++ b/doc/git-annex-examinekey.mdwn @@ -28,6 +28,10 @@ that can be determined purely by looking at the key. Also, '\\n' is a newline, '\\000' is a NULL, etc. + Note that it is not possible to extract the URL from a key created by the + URL backend: parts of longer URLs may be represented in the key by a + checksum. + * `--json` Enable JSON output. This is intended to be parsed by programs that use From 5085019f5ea450738976e7d6a921d01c67f01fda Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 12 Oct 2018 20:35:05 +0000 Subject: [PATCH 13/15] removed --- .../comment_9_7fb2f20ff86ad546a8c491714d3bf39c._comment | 8 -------- 1 file changed, 8 deletions(-) delete mode 100644 doc/internals/comment_9_7fb2f20ff86ad546a8c491714d3bf39c._comment diff --git a/doc/internals/comment_9_7fb2f20ff86ad546a8c491714d3bf39c._comment b/doc/internals/comment_9_7fb2f20ff86ad546a8c491714d3bf39c._comment deleted file mode 100644 index 53900116fb..0000000000 --- a/doc/internals/comment_9_7fb2f20ff86ad546a8c491714d3bf39c._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="Ilya_Shlyakhter" - avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" - subject="comment 9" - date="2018-10-12T20:17:19Z" - content=""" -What are *.rmet files? -"""]] From 99a9e2169ce6cebe717dd91cebbca5477241a3f3 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Fri, 12 Oct 2018 20:54:42 +0000 Subject: [PATCH 14/15] --- doc/forum/keys__44___URLs_and_URIs.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/forum/keys__44___URLs_and_URIs.mdwn diff --git a/doc/forum/keys__44___URLs_and_URIs.mdwn b/doc/forum/keys__44___URLs_and_URIs.mdwn new file mode 100644 index 0000000000..c83deae6ed --- /dev/null +++ b/doc/forum/keys__44___URLs_and_URIs.mdwn @@ -0,0 +1 @@ +What, exactly, is the relationship between keys, URLs and URIs? As I understand it, for each key, git-annex keeps a list of zero or more URLs/URIs from which the key's contents may be downloaded. Is each entry in this list specific to one special remote, i.e. is this really a list of pairs (URL/URI, special-remote-uuid)? Is the record of which key is present in which remote completely independent of the record of which key may be downloaded from which remote through which URL/URI? Is the only difference between URLs and URIs that, when a URL is added for a key, git-annex records the key as present in the web special remote, while when a URI is added, it doesn't? (Sorry for too many questions.) From 927a612d232f4de103626e37761e8c03a2c5b8b2 Mon Sep 17 00:00:00 2001 From: Mowgli Date: Sat, 13 Oct 2018 12:37:57 +0000 Subject: [PATCH 15/15] Added a comment --- ...omment_72_fb9581f4949efe1e8c90851fce9d61bf._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/install/fromsource/comment_72_fb9581f4949efe1e8c90851fce9d61bf._comment diff --git a/doc/install/fromsource/comment_72_fb9581f4949efe1e8c90851fce9d61bf._comment b/doc/install/fromsource/comment_72_fb9581f4949efe1e8c90851fce9d61bf._comment new file mode 100644 index 0000000000..9647ff4679 --- /dev/null +++ b/doc/install/fromsource/comment_72_fb9581f4949efe1e8c90851fce9d61bf._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="Mowgli" + avatar="http://cdn.libravatar.org/avatar/17ab194dddf7b7da59ec039cbb3ac252" + subject="comment 72" + date="2018-10-13T12:37:56Z" + content=""" +@joey, What I have is just the builds I get from gentoo respective the haskell overlay. The most current version in that overlay is 6.20180626 but it also does not compile. + +I need a version more recent than 6.20170818 as that version does still use rsync for remote copy. +"""]]