Date: Wed, 27 Oct 2021 20:11:37 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: maintainer-feedback requested: [Bug 259491] devel/ruby-gems: it should be updated to 3.1.4 Message-ID: <bug-259491-21402-Rw8bUXGI1L@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-259491-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-259491-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 259491: devel/ruby-gems: it should be updated to 3.1.4 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259491 --- Description --- Hi! I'm one upstream maintainer of rubygems. We've been getting some reports recently from freebsd users about some annoying warnings when using bundler= in freebsd. For example: https://github.com/rubygems/rubygems/issues/4283. I investigated the cause, and why only freebsd users have reported this iss= ue. The explanation is that the warning only happens when using bundler in ruby= 2.7 in combination with an old rubygems version (the issue was fixed by https://github.com/rubygems/rubygems/commit/2fcde0f4e0153ab9cc2152908bed5b4= 085d 82ce5#diff-8f51ef27aa7c1bf289ef010df42fb4a5f0635d0149776e57bc86985c98bc6480, which was released with rubygems 3.1). In general, we never noticed this because upstream policy is to only support using a rubygems version higher than or equal to the rubygems version inclu= ded with each upstream ruby version. So the support policy would be: * Ruby 2.5 ships with Rubygems 2.7, so only rubygems versions between 2.7 a= nd the latest rubygems are supported there. * Ruby 2.6 ships with Rubygems 3.0, so only rubygems versions between 3.0 a= nd the latest rubygems are supported there. * Ruby 2.7 ships with Rubygems 3.1, so only rubygems versions between 3.1 a= nd the latest rubygems are supported there. The devel/ruby-gems package follows our policy on ruby 2.5 and 2.6 but ship= s an out of date rubygems version in the case of ruby 2.7. This causes issues like the one above, since we don't support that combinat= ion at all. Would it be possible to get the package upgraded to 3.1.x? Thanks so much!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259491-21402-Rw8bUXGI1L>