Date: Wed, 29 Dec 2021 13:02:00 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 260794] sysutils/rubygem-bundler: Update to 2.3.0 Message-ID: <bug-260794-21402-lWn7SE7vWv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260794-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-260794-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260794 --- Comment #1 from Sean Champ <lab+bsd@thinkum.space> --- For clarification, the partial bundler installation was part of a local pat= ch on the Ruby 3.0 port build. The version of Bundler from that source - newer than the version presently in ports - would not have been normally installed with a Ruby 3.0 installation from ports. The error message it was displaying may have been due to an incorrect build configuration, however. I'd ran the build under `env RUBYOPT=3D--debug` whi= ch provided a little more information, working on renewing and updating the rubinius port. It doesn't provide any bundler gemfiles under the latest rubinius release. That may be where the error message was originating from, which I'd encountered. Hopefully, it may be possible to develop some more succinct test cases for = gem resolution under ruby-gems and bundler, under any local installation. Maybe= a TracePoint could be of some use there, e.g for determining exactly what bun= dler can't find when it emits a message that it can't find a thing. The updated bundler uses TTY color coding now. Its error messages may appear fairly different than in some previous versions --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260794-21402-lWn7SE7vWv>