From nobody Wed Oct 13 14:02:24 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 E08AE17F3D1C for ; Wed, 13 Oct 2021 14:02:24 +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 4HTvNw2Cpwz3h67 for ; Wed, 13 Oct 2021 14:02:24 +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 0DD7929113 for ; Wed, 13 Oct 2021 14:02:24 +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 19DE2ND0093646 for ; Wed, 13 Oct 2021 14:02:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 19DE2NUU093645 for ruby@FreeBSD.org; Wed, 13 Oct 2021 14:02:23 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 258108] devel/ruby-gems: Update to 3.2.26 (Fixes for Ruby 3.0) Date: Wed, 13 Oct 2021 14:02:24 +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: needs-qa, patch, regression X-Bugzilla-Severity: Affects Many People 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: attachments.created 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=3D258108 --- Comment #10 from Thibault Jouan --- Created attachment 228667 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D228667&action= =3Dedit Workaround broken --destdir with bundler (In reply to Yasuhiro Kimura from comment #8)=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 > The second one is that since 3.1 --destdir option of setup.rb has been br= oken. \ There are two report about it on upstream repository in GitHub. >=C2=B7=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 > https://github.com/rubygems/rubygems/pull/2768=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20 > https://github.com/rubygems/rubygems/issues/3604=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 >=C2=B7=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 > To make --destdir option work correctly both need to be fixed.=20=20=20= =20=20=20=20 I looked into it, but only for a very short time. If I recall=20=20=20=20= =20=20=20=20 correctly, the new attached patch fix the "duplicated" dest dir in one=20 of the paths, but there was a third dest dir issue in addition to=20=20=20= =20=20=20 those two already reported.=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 Also, I'm worried that even if it get fixed, it will break shortly=20=20= =20 after (it happened multiple times in the past already, still for=20=20=20= =20=20=20=20 `--destdir' option. Some people (myself included) trying to fix it=20=20=20= =20=20 upstream in the past seems to have given up and now prefer to patch=20=20= =20=20 their port directly (especially because they don't have to support=20=20=20= =20=20 Windows too in this case). --=20 You are receiving this mail because: You are the assignee for the bug.=