On Thu, 14 Nov 2019 12:07:52 +0100 Romain Bignon <rom...@symlink.me> wrote:
Great it works, thank you. Please tell us when the issue is fixed in the
experimental repository and that we can upgrade all versions from this
repository, as it is currently somewhat a hot fix.
We are blocked in multiple projects to get a proper fix,
See https://github.com/grpc/grpc/issues/21226
1. protobuf needs to release version 3.11 (currently at 3.10.1),
then
2. grpc need to update its embedded copy of protobuf to this version,
then
3. gitlab and gitaly needs to update ruby-grpc-tools, ruby-grpc, protoc
and protobuf to this version,
then
4. debian's version of protobuf and grpc should be updated to this version
So as a work around I have uploaded older versions of protobuf and grpc
to my personal repo.
1. Add the following lines to your sources.list
deb https://people.debian.org/~praveen/protobuf/ experimental main contrib
2. Add my gpg keys to apt trusted keys
# wget https://people.debian.org/~praveen/gitlab/praveen.key.asc
# apt-key add praveen.key.asc
# apt update
3. Downgrade ruby-grpc, ruby-google-protobuf and update gitaly
# apt install ruby-google-protobuf=3.7.1-1 ruby-grpc=1.19.1-1
# apt install gitaly/experimental
Make sure gitaly version is at least 1.59.3+dfsg-2 (just uploaded, it
will take some hours to show up in the archives)
4. Manually update Gemfile.lock and restart services.
# cd /usr/share/gitlab
# sudo -u gitlab truncate -s0 Gemfile.lock
# sudo -u gitlab bundle install --local
# systemctl restart gitlab-sidekiq
# systemctl restart gitlab gitaly
