On Fri, Feb 19, 2021 at 12:33 pm, Pirate Praveen
<prav...@onenetbeyond.org> wrote:
On 2021, ഫെബ്രുവരി 19 2:22:27 AM IST, Maximilian
Stein <m...@steiny.biz> wrote:
Uploaded gitaly 13.7.5 to fasttrack-staging. If someone can
confirm this, I will move it to fasttrack.
Hi,
I can confirm that gitaly-git2go is now present, however gitlab now
refuses to start since it's missing gitaly-13.6.5. So I cannot
confirm
that gitaly-git2go is actually working.
But I guess the refusal to start is just due to the updated gitlab
package still being missing? If gitlab requires an exact version of
gitaly shouldn't that be an exact dependency (i.e., "gitaly
(=13.6.5-1)"
instead of "gitaly (>= 13.6~)")?
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.
