Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Jan 2022 14:59:14 +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-JHVpSaI7Kw@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 #59 from Thibault Jouan <tj+freebsd_ports@a13.fr> ---
(In reply to Dan Langille from comment #58)
Thank you for the very fast feedback.

Here is a list of ports:
http://vault.a13.fr/media/rg-test_build-ports_list.txt

I don't even need the build logs. Only the list of port "origin" (like in my
list) that fail to build. Then I investigate the failing ones, if there are,
99% should be about gem spec patches conflicts and I will redo them.

This way IMO we should catch most errors as in an exp-run, but with less po=
rts
to build (2600 gem ports=E2=80=A6 and probably substantially more for depen=
dencies). If
this is still too much, we could decrease the list by keeping only ports wh=
ich
have a gemspec 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-JHVpSaI7Kw>