Date: Wed, 26 Jan 2022 17:06:03 +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-6Flv7miNAG@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 #61 from Thibault Jouan <tj+freebsd_ports@a13.fr> --- (In reply to Dan Langille from comment #60) Yes sorry about that, my own port tree always lag one or two days behind because I do those updates on a "desktop" computer, and when some ports are updated (say rust for example), I need a whole night or more to rebuild all. And I want to work on the RubyGems update with up to date ports to be sure it's correct. My last patch is based on 2e1fdc173831debc50f2c25b86e202c0a4967334 (Mon Jan 24 17:41:06 2022 -0600). textproc/rubygem-nokogiri was updated few hours ago (Wed Jan 26 11:43:00 2022 +0100). Thankfully, this last update is the gemspec patch removal, which is great news: you can safely ignore failure to apply for this specific file (but only this one), and it will also simplify next patch update. Hopefully I submit an updated patch tomorrow (if I can rebuild my ports next night). --=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-6Flv7miNAG>