From nobody Fri Oct 29 00:25:30 2021 X-Original-To: ruby@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 12480181A3AB for ; Fri, 29 Oct 2021 00:25:31 +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 4HgNVy72gDz4Rm3 for ; Fri, 29 Oct 2021 00:25:30 +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 D25A65743 for ; Fri, 29 Oct 2021 00:25:30 +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 19T0PU9E000548 for ; Fri, 29 Oct 2021 00:25:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 19T0PUtu000547 for ruby@FreeBSD.org; Fri, 29 Oct 2021 00:25:30 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: ruby@FreeBSD.org Subject: [Bug 259491] devel/ruby-gems: it should be updated to 3.1.4 Date: Fri, 29 Oct 2021 00:25:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed 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: tj+freebsd_ports@a13.fr 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: cc Message-ID: In-Reply-To: References: 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: FreeBSD-specific Ruby discussions List-Archive: https://lists.freebsd.org/archives/freebsd-ruby List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ruby@freebsd.org X-BeenThere: freebsd-ruby@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259491 Thibault Jouan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tj+freebsd_ports@a13.fr --- Comment #2 from Thibault Jouan --- hi, I think it has to do with Ruby 2.7.1 (port lang/ruby27), which printed keyword arguments warnings by default but it was fixed with Ruby 2.7.2 (#250050). If I'm correct, it happened even when using RubyGems (via `gem' command, not bundler calling RubyGems API). The current version of RubyGems is old indeed, some people have worked on the update since a while. From what I experienced and have seen (other PRs on the bug tracker, efforts on other RubyGems ports), the update to 3.1 is a little more involved than some past ones. There is of course the removal of `USE_BUNDLER_FOR_GEMDEPS', but also slightly more changes to the setup command than usual, the repository and history getting bigger, and there are the changes to the plugin system which aren't that big, but whatever solution we chose to adapt the port(s) there are many gems to check (ports of gems which depends on devel/ruby-gems). That may explain some delay. The most recent PR was #258108. However it targets RubyGems 3.2.30 (patches for 3.2.26, 3.2.29, and 3.2.30 attached), because it seemed that most difficulties were related to 3.0 -> 3.1, so once it's done, better use the last one than an old branch I think. Is 3.1 "actively" maintained and should we use that, or keep working on last 3.2? We have Ruby 2.6, 2.7, and 3.0 in ports (maybe 3.1 soon) so it has to work on all of them too. Note: I'm speaking from my point of view of RubyGems user and occasional patch writer or gem porter, not as someone making the actual changes and managing ports in FreeBSD. --=20 You are receiving this mail because: You are the assignee for the bug.=