From nobody Wed Oct 27 20:11:37 2021 X-Original-To: ports-bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 760D81824489 for ; Wed, 27 Oct 2021 20:11:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HffwT2kssz3rQm for ; Wed, 27 Oct 2021 20:11:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 3FD45167AA for ; Wed, 27 Oct 2021 20:11:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 19RKBb97072687 for ; Wed, 27 Oct 2021 20:11:37 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 19RKBblL072686 for ports-bugs@FreeBSD.org; Wed, 27 Oct 2021 20:11:37 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 259491] devel/ruby-gems: it should be updated to 3.1.4 Date: Wed, 27 Oct 2021 20:11:37 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: deivid.rodriguez@riseup.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ruby@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259491 Bug ID: 259491 Summary: devel/ruby-gems: it should be updated to 3.1.4 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: ruby@FreeBSD.org Reporter: deivid.rodriguez@riseup.net Flags: maintainer-feedback?(ruby@FreeBSD.org) Assignee: ruby@FreeBSD.org 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= 085d82ce5#diff-8f51ef27aa7c1bf289ef010df42fb4a5f0635d0149776e57bc86985c98bc= 6480, 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! --=20 You are receiving this mail because: You are the assignee for the bug.=