33 lines
1.5 KiB
Markdown
33 lines
1.5 KiB
Markdown
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]]
|
|
|
|
>> gitlab tells me their version is 5.20140412ubuntu1.
|
|
>> I tried installing git-annex-shell from 5.20140412, but
|
|
>> was not able to reproduce the problem using it. This makes me think the
|
|
>> problem is somehow in gitlab's git-annex-shell integration code.
|
|
>>
|
|
>> Update: Root-caused and filed a bug:
|
|
>> <https://gitlab.com/gitlab-org/gitlab-shell/issues/24
|
|
>>
|
|
>> This will need to be fixed on the gitlab side, so closing it here.
|
|
>> [[done]] --[[Joey]]
|