aboutsummaryrefslogtreecommitdiff
path: root/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn')
-rw-r--r--doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn b/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn
new file mode 100644
index 000000000..06ea255d0
--- /dev/null
+++ b/doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn
@@ -0,0 +1,12 @@
+It's not possible to use gcrypt with gitlab repos, despite the webapp
+currently offering this as an option. The resulting remote works as far as
+pushes go, but fails with an error "Failed to connect to remote to set it
+up."
+
+It seems that the gitlab repo is somehow in a state where git-annex-shell
+configlist reports it's not yet a git-annex repo, but git-annex-shell
+gcryptsetup fails with "gcryptsetup refusing to run; this repository already has a git-annex uuid!"
+
+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]]