blob: 732d1e30443bdaedf1f95a8ce46bb9a36b2df5b1 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
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]]
> 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]]
|
