On Tue, 8 Sep 2020 17:20:38 +0200
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= <g...@debian.org>
wrote:
> Hi Thomas,
>
> On Tue, Sep 8, 2020 at 1:27 PM Thomas Goirand <z...@debian.org>
wrote:
> > I'm not seeing any progress on this bug. Is anyone working on this?
> The bug report is too wide, "GitLab can't start" doesn't help to
> narrow it down. I even suspect the real bug is in GitLab itself, it
> may not (correctly) handle the new gRPC version.
>
> > Without any action, this going to trigger the removal of most of
> > OpenStack from testing... :/
> For some weeks I don't have time to learn GitLab and its internals to
> find out where and why it fails with gRPC 1.30.2 version.
> In the long run it might be the best to drop Ruby support from
> src:grpc and let Pirate maintain that from a separate source tree.
I don't think the problem is with gitlab, as gRPC 1.30.2 rubygem
installed from rubygems.org (gem install -v 1.30.2 grpc) does not have
this problem and only the debian package have this problem. So we
cannot reproduce this issue in upstream ci.
ruby-grpc was a separate package initially and I think having it
maintained as part of src:grpc itself would be best, but I don't mind
maintaining it separately if that is preferred.
