Date: Wed, 06 Oct 2021 19:25:34 +0000 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) Message-ID: <bug-258108-21402-TRG9U4jHEK@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 #6 from mikeg@bsd-box.net --- The crazy long list of bundler orphans are expected(ish) per my second QA n= ote - I pulled these from the package in favor of the current status quo of "If= you want bundler install sysutils/rubygem-bundler." since that was more current that what's packaged with gem. (The stuff it's staging under /wrkdir is also an artifact of building Bundl= er.) If you think it makes sense to install the Bundler that comes with gems ins= tead to quiet the poudriere I can re-patch to pack Bundler and mark the two port= s as conflicting - that might need a dependencies audit though. I could also have the Makefile clean all of this up in a post-install if you think that's sensible, seemed dirty to me though. If I could get it to stop building Bundler entirely it should be a clean packing list. --=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-TRG9U4jHEK>