Date: Thu, 02 Dec 2021 16:28:22 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 258108] [exp-run] devel/ruby-gems: Update to 3.2.30 (Fixes for Ruby 3.0) Message-ID: <bug-258108-21402-u5leMfqPdl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258108-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-258108-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258108 --- Comment #37 from Dan Langille <dvl@FreeBSD.org> --- When I send fixes upstream, I also implement them in the port until upstream issues a new release which contains those fixes. Is there anything holding us up now? I'd love to get this into the tree. I = have developers at $WORK who would love to test it. I tried the current patch and it stops patching here. Is there anything I c= an do to help please? .... Patching file www/rubygem-addressable25/files/patch-gemspec using Plan A... Hunk #1 succeeded at 1. Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -------------------------- |--- www/rubygem-em-websocket/files/patch-gemspec=20=20=20=20=20=20=20 |+++ www/rubygem-em-websocket/files/patch-gemspec=20=20=20=20=20=20=20 -------------------------- File to patch: --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-258108-21402-u5leMfqPdl>