Date: Wed, 29 Dec 2021 12:30:22 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: maintainer-feedback requested: [Bug 260794] sysutils/rubygem-bundler: Update to 2.3.0 Message-ID: <bug-260794-21402-G4Akav5rLP@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
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-ruby (Nobody) <ruby@FreeBSD.org> for maintainer-feedback: Bug 260794: sysutils/rubygem-bundler: Update to 2.3.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260794 --- Description --- bundler 2.3.0 was release just shortly more than a week ago https://github.com/rubygems/rubygems/commit/a6889b2122675d77baabcb75e5ff740= 9956 ce32c#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 (si= nce 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260794-21402-G4Akav5rLP>