At all 12 tinderbox images I experienced here sth like: /home/tinderbox/run/17.1_systemd-j3-20210601-172026/var/log/emerge.log 2021-06-02T00:24:04 >>> dev-util/ragel-7.0.4: 2 minutes, 12 seconds 2021-06-03T18:40:00 >>> dev-util/ragel-6.10: 55 seconds 2021-06-03T20:24:54 >>> dev-util/ragel-7.0.4: 2 minutes, 15 seconds 2021-06-03T21:52:21 >>> dev-util/ragel-6.10: 57 seconds 2021-06-03T22:06:18 >>> dev-util/ragel-7.0.4: 2 minutes, 10 seconds 2021-06-04T17:26:50 >>> dev-util/ragel-6.10: 1 minute, 15 seconds 2021-06-04T20:22:22 >>> dev-util/ragel-7.0.4: 2 minutes, 31 seconds I'll attach all log files of emerge of that image here too. The issue is generic and seems not to be related to special USE flag combos. All images are ~amd64.
Created attachment 713754 [details] task.20210602-003925.dev_ruby_ruby_rc4.log
Created attachment 713757 [details] task.20210603-184137.dev_ruby_ecma_re_validator.log
Created attachment 713760 [details] task.20210603-202737.dev_ruby_rspec_json_expectations.log
Created attachment 713763 [details] task.20210603-220357._world.log
Created attachment 713766 [details] task.20210603-220853.dev_ruby_blinkstick.log
Created attachment 713769 [details] task.20210604-173317._world.log
Created attachment 713772 [details] task.20210604-202803.dev_ruby_ruby_gtksourceview3.log
The problem is that some packages still declare dependencies on the older version, so we probably need to file bugs for them instead.
(In reply to Sam James from comment #8) > The problem is that some packages still declare dependencies on the older > version, so we probably need to file bugs for them instead. My understanding is (at least for the ruby packages depending on ragel) that ragel 7 is not compatible with ragel 6 and required functionality is no longer present, so these dependencies won't be able to upgrade to ragel 7. One thing to consider is to put ragel 6 and 7 in separate slots (with e.g. the ragel 6 slot providing a ragel-6 binary to run). I haven't looked at the feasibility of this. We would also need to consider desirability, especially if upstream no longer maintains ragel 6.
at least booth versions should block each other IMO if they can't coexists at the same system
FWIW dev-ruby/capybara still wants ragel-6
dev-ruby/parser wants ragel-6
and: =dev-util/ragel-6* required by (dev-ruby/regexp_parser-2.7.0:2/2::gentoo, installed) USE="-doc -test" RUBY_TARGETS="ruby31 -ruby30 -ruby32"
dev-ruby/redcloth-4.3.2-r4:0/0 depends on old ragel too
and dev-ruby/parser-3.2.2.3:0/0 too
*** Bug 933240 has been marked as a duplicate of this bug. ***
Bug 933240 makes the comment that ragel 7.0.4 does have a ragel-ruby command. This wasn't there in earlier 7.0 versions. It also isn't backward compatible with how ragel 6 handles ruby, but it does seem to work to generate ruby code. We could patch all the existing ruby gems to use it to generate ruby code. The current list of packages to update is: dev-ruby/json dev-ruby/parser dev-ruby/regexp_parser dev-ruby/redcloth
(In reply to Hans de Graaff from comment #17) > dev-ruby/json Doesn't use ragel for ruby code so there is no need to restrict this. > dev-ruby/parser Crashes the ragel 7.0.4 ragel-ruby command (segmentation fault). > dev-ruby/regexp_parser Generates ruby code but fails all its tests with it. > dev-ruby/redcloth Haven't investigated anymore. So it looks like the ruby support in ragel 7.0.4 doesn't work and we can't use it. :-(
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1b25a69077f514882b5039e763c5bcbc5841b757 commit 1b25a69077f514882b5039e763c5bcbc5841b757 Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2024-06-04 04:26:28 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2024-06-04 04:26:28 +0000 dev-ruby/json: allow all ragel versions It turns out dev-ruby/json does not use ragel to generate ruby code and using ragel 7 works fine for this case. Bug: https://bugs.gentoo.org/794235 Signed-off-by: Hans de Graaff <graaff@gentoo.org> dev-ruby/json/json-2.7.2-r1.ebuild | 51 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 51 insertions(+)
Could someone stabilize dev-ruby/json/json-2.7.2-r1.ebuild to fix this in gentoo stable?
(In reply to Andreas Nyback from comment #20) > Could someone stabilize dev-ruby/json/json-2.7.2-r1.ebuild to fix this in > gentoo stable? not fixed (at least at a recent tinderbox image 23.0_no_multilib-20241106-235501)
(In reply to Toralf Förster from comment #21) > not fixed (at least at a recent tinderbox image > 23.0_no_multilib-20241106-235501) Note that this is only fixed for dev-ruby/json, not for other dev-ruby packages like dev-ruby/parser or dev-ruby/regexp_parser. So depending on the dependency list you'll still see up/downgrades, just a lot less of them.
