diff options
author | 2015-09-18 13:29:35 -0400 | |
---|---|---|
committer | 2015-09-18 13:29:35 -0400 | |
commit | 71558b3b202ddc27257bea8e8c7cbb491a053b6e (patch) | |
tree | ab67c2d481a2d153b21ec1f94b6f6834363c184a | |
parent | c38ef538bfa0fe13acbc3403ab23c8857f2a52e5 (diff) |
analysis
-rw-r--r-- | doc/bugs/gcrypt_special_remote_fails_on_bare_remote_repos/comment_1_7e690402c8dd663d60f7fc659c323ed8._comment | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/bugs/gcrypt_special_remote_fails_on_bare_remote_repos/comment_1_7e690402c8dd663d60f7fc659c323ed8._comment b/doc/bugs/gcrypt_special_remote_fails_on_bare_remote_repos/comment_1_7e690402c8dd663d60f7fc659c323ed8._comment new file mode 100644 index 000000000..e208b9bd1 --- /dev/null +++ b/doc/bugs/gcrypt_special_remote_fails_on_bare_remote_repos/comment_1_7e690402c8dd663d60f7fc659c323ed8._comment @@ -0,0 +1,26 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-09-18T16:56:42Z" + content=""" +So, the missing bit of data needed to reproduce this is that +~/astro.git didn't exist at all before this initremote call. + +If you `git init --bare ~/astro.git` first, it works fine. + +The documentation says, of gitrepo: + + This repository should be either empty, or an existing gcrypt repositry. + +So, I don't know if this is really a bug, you're not doing what the +documentation says to do. + +I suppose git-annex initremote could create a bare repository when none exists +in this case, but it would then have to parse the gitrepo parameter, normalize +it, use the approptiate protocol (file, ssh, rsync) to check if it exists or +create it, etc, instead of simply passing it to gcrypt. + +(What is actually going on here is, gcrypt supports remotes that are not git repositories at all. +When the repo doesn't exist, it assumes such a remote is wanted and makes one. +But, git-annex does not support working with that kind of gcrypt remote.) +"""]] |