Created attachment 230535 [details] Version bump - sysutils/rubygem-bundler => 2.3.0 bundler 2.3.0 was release just shortly more than a week ago https://github.com/rubygems/rubygems/commit/a6889b2122675d77baabcb75e5ff7409956ce32c#diff-bef499567a8a175684070da2d559099eace44fb40871b82f080b6abd4ce6cb3f A patch is attached for the version bump This update may serve to bring the installed Bundler version up to a version newer than what's installed (or partially installed) with Ruby 3.0. As such, it may serve to prevent some errors that might be encountered with the bundler port and Ruby 3.0, if ruby-gems tries to use the bundler under Ruby 3.0 (since it has a newer version) while it's only partially installed. I'm afraid that's not as easy to backtrace, but I think that's what was happening there. This update seemed to have worked around that ... for now. Health, all - Sean
For clarification, the partial bundler installation was part of a local patch 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=--debug` which 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 bundler 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
It is 2.3.10 now.