Date: Mon, 23 Apr 2018 10:27:00 +0200 From: Torsten Zuehlsdorff <tz@FreeBSD.org> To: Matthias Fechner <idefix@fechner.net>, Steve Wills <swills@FreeBSD.org>, Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org, Matthias Fechner <mfechner@FreeBSD.org> Subject: Re: svn commit: r467510 - head/textproc/rubygem-autoprefixer-rails Message-ID: <c25b2626-d47d-714b-ca85-dcc4aaaa4537@FreeBSD.org> In-Reply-To: <2e5f6201-68ac-730d-b91f-2c0ef206ddc2@fechner.net> References: <201804161833.w3GIXF20069435@repo.freebsd.org> <aed6c32c-0822-0827-b414-13b8b721656f@FreeBSD.org> <8d3b5430-56da-fd8d-fbe4-df791f02b94a@fechner.net> <3cbfa4ca-54ae-7df9-bb7a-8b1a5e724cdd@FreeBSD.org> <2e5f6201-68ac-730d-b91f-2c0ef206ddc2@fechner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23.04.2018 10:11, Matthias Fechner wrote: > Am 20.04.2018 um 23:49 schrieb Steve Wills: >> I think I was mistaken, I deleted Gemfile.lock and it was OK. > > hm, should we maybe put the Gemfile.lock generation into the port itself? > > But that means, that everytime a gem got updated, PORTREVISION of gitlab > must be increased. > But I think that should make the port for a standard user easier to > use/upgrade. > > What do you think? Remko suggested some (long) time ago to delete Gemfile.lock when (re)starting GitLab. This would solve various issues, but i never found time for it. Greetings, Torsten
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c25b2626-d47d-714b-ca85-dcc4aaaa4537>