[DRE-maint] Bug#983915: gitlab: fails to install: Could not find gem 'rugged (~> 0.28)'

[Pirate Praveen]

On 2021, മാർച്ച് 3 4:20:32 PM IST, Andreas Beckmann <anbe at debian.org> wrote:
>Package: gitlab
>Version: 13.4.7-2
>Severity: serious
>User: debian-qa at lists.debian.org
>Usertags: piuparts
>
>Hi,
>
>during a test with piuparts I noticed your package failed to install. As
>per definition of the release team this makes the package too buggy for
>a release, thus the severity.
>
>From the attached log (scroll to the bottom...):
>
>  Setting up gitlab (13.4.7-2) ...
>  fatal: not a git repository (or any of the parent directories): .git
>  fatal: not a git repository (or any of the parent directories): .git
>  [ESC][31mCould not find gem 'rugged (~> 0.28)' in any of the gem sources listed in your
>  Gemfile.[ESC][0m

This is a known issue. We are not yet able to make gitlab work with rugged 1.1 in the archive. A license compatibility issue delayed the upstream update (reverse-markdown in the dependency chain is licensed under wtfpl which was not OK for gitlab initially, and this issue is now resolved).

This is tracked in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979563

 Hopefully we will see a fix soon.

For now, work around is to use rugged 0.28 from snapshot.debian.org

See https://wiki.debian.org/gitlab#Experimental_-_During_freeze_and_transitions

>  dpkg: error processing package gitlab (--configure):
>   installed gitlab package post-installation script subprocess returned error exit status 1
>  Processing triggers for ca-certificates (20210119) ...
>  Updating certificates in /etc/ssl/certs...
>  0 added, 0 removed; done.
>  Running hooks in /etc/ca-certificates/update.d...
>  done.
>  Errors were encountered while processing:
>   gitlab
>
>
>cheers,
>
>Andreas

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.