From 008204b2f34bd00de690ba81fbd98ec70afb6e97 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 4 Aug 2022 12:39:07 -0400 Subject: [PATCH] explain why this happens and close --- ...cognized_as_a_git-annex_enabled_repos.mdwn | 2 + ..._8a27545e11b3d9e4e45aea4c9a5c9af4._comment | 42 +++++++++++++++++++ 2 files changed, 44 insertions(+) create mode 100644 doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos/comment_1_8a27545e11b3d9e4e45aea4c9a5c9af4._comment diff --git a/doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos.mdwn b/doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos.mdwn index 2326cf9398..c882dbe2d1 100644 --- a/doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos.mdwn +++ b/doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos.mdwn @@ -12,3 +12,5 @@ If there are any mistakes in my understanding please let me know. sincerely yours, Rino Mizuguchi + +> [[notabug|done]] --[[Joey]] diff --git a/doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos/comment_1_8a27545e11b3d9e4e45aea4c9a5c9af4._comment b/doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos/comment_1_8a27545e11b3d9e4e45aea4c9a5c9af4._comment new file mode 100644 index 0000000000..6112e946e2 --- /dev/null +++ b/doc/bugs/GIN_is_not_recognized_as_a_git-annex_enabled_repos/comment_1_8a27545e11b3d9e4e45aea4c9a5c9af4._comment @@ -0,0 +1,42 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-08-04T16:22:09Z" + content=""" +If you're using GIN, perhaps you're also using Datalad. Have you read +[their documentation](http://handbook.datalad.org/en/0.13_a/basics/101-139-gin.html) +on using it with git-annex? + +Part of that documentation that seems likely to be especially +relevant is [here](http://handbook.datalad.org/en/0.13_a/basics/101-139-gin.html#access): + +> Important: Take the URL in the browser, not the copy-paste URL +> Please note that you need to use the browser URL of the repository, +> not the copy-paste URL on the upper right hand side of the repository if you want +> to get anonymous HTTPS access! The two URLs differ only by a .git extension: +> +> Brower bar: `https://gin.g-node.org//` +> +> Copy-paste “HTTPS clone”: `https://gin.g-node.org//.git` +> +> A dataset cloned from `https://gin.g-node.org//.git`, however, can not retrieve annexed files! + +The reason is that git-annex needs to construct urls to download +files from the repo, starting with git's `config` file. +Looking at the sample repo , +an url based on that works , +but its web page suggests cloning the url +, and + does not work. + +How does git manage to clone the latter url then? Well, +the http server is speaking the git smart http protocol. +So git makes requests like `https://gin.g-node.org/adswa/DataLad-101.git/info/refs?service=git-upload-pack` +which do work. But that protocol is not useful for git-annex, so it +needs the url where the actual files in the repository can be downloaded, +not the url where the smart http protocol is spoken. + +There is not generally a way to discover one url from the other url +(removing ".git" might work in this case, but not in other cases). +So unfortunately you will need to remember to use the right url. +"""]]