Created attachment 232255 [details] Patch file devel/ruby-gems has been updated to 3.3.7 and it works fine with Ruby 3.0 and later. On the other hand Ruby 2.6 will reach its EoL on March 31, and after that Ruby 2.7 will became oldest supported version of Ruby and enter security only maintenance phase. So now is the time to switch default version of Ruby from 2.7 to 3.0.
Some new failure logs on 12.2 amd64: http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-libarchive-0.1.2_1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/klayout-0.27.3_1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-mysql-2.9.1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/ruby-subversion-1.14.1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-heapy-0.1.4.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-iobuffer-1.1.2.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-jenkins_api_client-1.5.3.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-ruby_dep-1.5.0.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-strptime-0.2.4.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-xdg3-3.1.1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-xdg4-4.5.0.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/kross-interpreters-21.12.3.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/milter-manager-2.1.6.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-tmail-1.2.7.1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-rb-gsl-2.1.0.2_5.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/sdformat-8.0.0_4.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-pcaprub-0.13.0.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/arirang-2.03_1,1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubywarden-0.0.0.20200226.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/mcollective-2.12.5.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/puppet6-6.26.0.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-bolt-3.21.0.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-ferret-0.11.8.7.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/redmine4-4.1.6.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-adsf-1.4.1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-nanoc-core-4.11.19.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/unit-ruby3.0-1.26.1_1.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/rubygem-tk-0.2.0.log http://package18.nyi.freebsd.org/data/122amd64-default-foo/2022-03-05_09h02m46s/logs/errors/subtle-0.11.3224.log
All build errors listed in comment #1 is either fixed or marked BROKEN with Ruby 3.x. So I would like to another exp-run to check if there is any new build error.
(In reply to Yasuhiro Kimura from comment #2) > So I would like to another exp-run to check if there is any new build error. Oops, I mean "I would like to request another exp-run". Best Regards.
Created attachment 232900 [details] Updated patch file * Chase update of ports tree. * Add entry to UPDATING.
More failure logs: http://package23.nyi.freebsd.org/data/130i386-default-foo/2022-03-31_08h49m42s/logs/errors/h2o-2.2.6.log http://package23.nyi.freebsd.org/data/130i386-default-foo/2022-03-31_08h49m42s/logs/errors/h2o-devel-2.3.0.d.20220210.log
Created attachment 233296 [details] Updated patch file Chase update of ports tree.
(In reply to Antoine Brodin from comment #5) Both www/h2o and www/h2o-devel are marked BROKEN with Ruby 3.x when MRUBY option is enabled. So I'd like to request another exp-run to check if any build errors are still left.
Exp-run looks fine
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=eca58e3768122a0ef093f62ad91760e4341f5df1 commit eca58e3768122a0ef093f62ad91760e4341f5df1 Author: Yasuhiro Kimura <yasu@FreeBSD.org> AuthorDate: 2022-03-05 04:08:26 +0000 Commit: Yasuhiro Kimura <yasu@FreeBSD.org> CommitDate: 2022-04-21 14:08:24 +0000 Mk/bsd.default-versions.mk: Switch default version of Ruby from 2.7 to 3.0 How to upgrade is described in the entry of 20220421 in UPDATING. PR: 262350 Exp-run by: antoine Mk/bsd.default-versions.mk | 2 +- UPDATING | 24 ++++++++++++++++++++++++ 2 files changed, 25 insertions(+), 1 deletion(-)