Date: Fri, 30 Nov 2018 07:05:14 +0100 From: Matthias Fechner <idefix@fechner.net> To: Po-Chuan Hsieh <sunpoet@freebsd.org>, Matthias Fechner <mfechner@freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r486196 - in head/devel: . rubygem-grape11 Message-ID: <c737fec4-61be-88f4-3b60-22d84b3e7625@fechner.net> In-Reply-To: <CAMHz58S1BUVnAZ6awYdEDQEH-iD7%2B8t9HTijm6iqu=xZoBg7sg@mail.gmail.com> References: <201811291649.wATGnjNH037720@repo.freebsd.org> <CAMHz58S1BUVnAZ6awYdEDQEH-iD7%2B8t9HTijm6iqu=xZoBg7sg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 29.11.2018 um 18:25 schrieb Po-Chuan Hsieh: > Upstream should fix it (gem 'grape', '~> 1.1') if they do not support > grape 1.2. > already reported upstream, please see commit message in gitlab-ce > I'm not sure what problem you got. > Did you try the latest version (rubygem-grape 1.2.1, committed within > an hour)? problem was also reported by a user after I committed the fix: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233640 No I have not tested the new version, but the changelog for this version: https://github.com/ruby-grape/grape/blob/v1.2.1/CHANGELOG.md does not mention anything that I see could fix the problem. 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?c737fec4-61be-88f4-3b60-22d84b3e7625>