diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2015-07-27 15:29:10 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2015-07-27 15:29:10 -0400 |
| commit | c65e886105bec5bcdab80c8122c31dfaa7850d08 (patch) | |
| tree | d06b2fabf26807b1686fc5e2509c05eaeb8f83a0 | |
| parent | 3b940de11c2fb854a3b4855e79d9d01a8e6854e4 (diff) | |
more info
| -rw-r--r-- | doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn b/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn index 06ea255d0..732d1e304 100644 --- a/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn +++ b/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn @@ -10,3 +10,13 @@ gcryptsetup fails with "gcryptsetup refusing to run; this repository already has This does not happen when I try the same setup on a self-hosted repo. Unsure what is causing git-annex-shell to behave this way on gitlab. --[[Joey]] + +> Here's a minimal way to reproduce this problem: +> +> 1. Make a new, empty repository on gitlab.com. +> 2. Run command: ssh git@gitlab.com git-annex-shell 'gcryptsetup' '/~/username/reponame.git' ':id:dummy' +> +> Leads to the failure as described above. But, the repo is new and empty +> and has not had any opportunity to get a git-annex uuid set.. +> +> I wonder what version of git-annex gitlab.com is running? --[[Joey]] |