[DRE-maint] Bug#982903: gitlab: Internal error caused by missing gitaly-git2go binary

[Maximilian Stein]

>> You will need to regenerate Gemfile.lock. See the wiki page for steps.
>>
>> It saves the exact versions used during installation in Gemfile.lock
>>
>> It is supposed to be handled automatically for most gems, but it does 
>> not work for native gems. There is an open bug about it.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944698
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914989
>
> Which I have fixed now in 13.6.7-2 and 13.6.7-1_fto10+2 (I was trying 
> to fix by dpkg trigger which was not sufficient, now everytime 
> gitlab-sidekiq service start, this will be fixed). So restarting 
> gitlab service should be sufficient to fix this.
>
>
This has worked like a charm! As far as I can tell, Gitlab works with 
this setup now (gitlab=13.6.7-1~fto10+2, gitaly=13.7.5+dfsg-1~fto10+3).

This doesn't seem to cause any trouble but I noticed that gitlab's check 
is complaining:

   GitLab Shell: ... GitLab Shell version >= 13.13.1 ? ... FAIL. Please 
update gitlab-shell to 13.13.1 from 13.13.0

Indeed, there does not seem to be any newer version of gitlab-shell 
available than 13.13.0+debian-1~bpo10+1.

Best
Maximilian


-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 236 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20210219/abab3de9/attachment.sig>