open and close gitlab issues
This commit is contained in:
parent
ee25170de5
commit
3e98e26303
3 changed files with 21 additions and 0 deletions
|
@ -0,0 +1,6 @@
|
|||
Enabling a gitlab repo that was set up elsewhere in the webapp doesn't
|
||||
work.
|
||||
|
||||
This is a SMOP; it needs to detect that the repo is on gitlab and use a
|
||||
custom enabling process and no the generic one, which doesn't work.
|
||||
--[[Joey]]
|
12
doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn
Normal file
12
doc/bugs/gitlab_repos_cannot_use_gcrypt.mdwn
Normal file
|
@ -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]]
|
|
@ -5,3 +5,6 @@ Hi,
|
|||
Gitlab.com and Gitlab enterprise edition, but unfortunately not Gitlab community edition, now [provides git annex support](https://about.gitlab.com/2015/02/17/gitlab-annex-solves-the-problem-of-versioning-large-binaries-with-git/). It works fairly based for the repos I have enabled it on. At the moment it's free, but one may have to pay for repos larger than 5Gb [in the future](https://about.gitlab.com/2015/02/22/gitlab-7-8-released/#comment-1870271594).
|
||||
|
||||
Perhaps gitlab.com should be added to preconfigured cloud providers?
|
||||
|
||||
> [[done]] although there are a few known bugs in the webapp's
|
||||
> implementation. --[[Joey]]
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue