Date: Thu, 9 Aug 2018 11:01:30 +0200 From: Matthias Fechner <idefix@fechner.net> To: Christoph Moench-Tegeder <cmt@burggraben.net> Cc: "Vanilla I. Shu" <vanilla@freebsd.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org, Steve Wills <swills@freebsd.org> Subject: Re: svn commit: r476331 - head/devel/grpc Message-ID: <192c47a7-ae69-4fd2-a3bf-4b8e31824ed8@fechner.net> In-Reply-To: <20180807172744.ac2x3lkoqgvi3o4d@squirrel.exwg.net> References: <201808040214.w742Essb042694@repo.freebsd.org> <20180804100638.GA44989@elch.exwg.net> <af0030a9-0579-d7fa-f562-5cd644c7af3e@fechner.net> <20180807172744.ac2x3lkoqgvi3o4d@squirrel.exwg.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Dear all, Am 07.08.18 um 19:27 schrieb Christoph Moench-Tegeder: > Is that really not working or just "because the Gemfile says so"? > (Ruby ports with their constant breakage and arbitrarily versioned > dependencies... somedey someone will have an idea about that. OTOH > other languages needed to grow until version 5 for being really > usable :)) I created now a new branch: https://gitlab.fechner.net/mfechner/Gitlab/commits/test-grpc-update this branch includes the grpc update, update for rubygem-grpc and all patches required to get gitlab-ce compiled again. Builds are currently running can be seen here: https://pkg.fechner.net/jail.html?mastername=111amd64-gitlab#top All the packages for testing can be found by using this pkg address: https://pkg.fechner.net/packages/111amd64-gitlab/ As I had to patch not only gitlab-ce but also gitaly the risk is very high, that this has broken something in gitlab-ce. As I have no idea for what grpc in gitlab-ce is used, it would be really helpful if I get support to test this patched gitlab to ensure it is working correctly. As I do not use any more advanced feature like dev-ops, pipeline, CI, ... in gitlab I cannot test this. As grpc is a remote call lib I fear that this lib is used for all the stuff in gitlab I do not use and therefor cannot test. I use the following vagrant to spin up a testing server in my home network: https://gitlab.fechner.net/mfechner/Gitlab-vagrant this includes already all modifications required to get the new version 11.1.x running, you only need to modify the link to the pkg repository there. So if anyone is using features in gitlab that uses grpc in background and is willing to help me testing, we can more quickly get the grpc update into the ports again. Thanks a lot. Gruß, Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?192c47a7-ae69-4fd2-a3bf-4b8e31824ed8>