Control: fixed -1 gitaly/0.129.0+debian-2 On Thu, 13 Dec 2018 23:10:58 +0100 =?UTF-8?B?RGF2aWQgTMOzcGV6IFphamFyYSAoRXJfTWFxdWkp?= <[email protected]> wrote: > Hi, > > I've tried to copy my /var/lib/gitlab from production server to the test > one. When I've do it, test server stop working. > > Doing some diffs between folders, I've found this: > > root@debian:/home# diff gitlab/gitaly-Gemfile.lock gitaly-Gemfile.lock > 16c16 > < gitaly-proto (0.117.0) > --- >> gitaly-proto (0.118.1) > > On production server, gitaly gemfile are trying to find gitaly-proto > 0.117.0. But on the server the version installed are 0.118.1-dfsg-2. > > I've changed these line on production server and now it's working. > > I don't know why the gemfile didn't update when the gem itself has been > updated, maybe, you can figure something about this. If there's a local > problem, it's done. If the problem are with the update, you have the error > now and you can deploy a patch.
This is now fixed in gitaly (#909191). This will be uploaded to unstable once https://gitlab.com/gitlab-org/gitlab-shell/issues/171 is fixed. In the meantime, the workaround is to run 'dpkg-reconfigure gitaly' manually.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
