dev-ruby/asciidoctor-2.0.12 has RUBY_TARGETS="ruby26 ruby25" Upstream says Ruby 3.0 should work. Please bump RUBY_TARGETS. Reproducible: Always
We also need all dependencies (and test dependencies) to work correctly on newer ruby versions so this is not as straightforward as just adding the target.
> We also need all dependencies (and test dependencies) to work correctly on > newer ruby versions so this is not as straightforward as just adding the > target. Agreed. I have scars from spelunking into Ruby dependencies. Could be worse, could be Erlang...
This now becomes more important because >=sys-apps/util-linux-2.37_rc1 requires dev-ruby/asciidoctor to build its man-pages: https://github.com/karelzak/util-linux/blob/master/Documentation/releases/v2.37-ReleaseNotes#L7 Can you please consider giving this some higher priority?
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1a4a08e6bcf96ec1af5e4dc5af4d3675f1e0c19d commit 1a4a08e6bcf96ec1af5e4dc5af4d3675f1e0c19d Author: Hans de Graaff <graaff@gentoo.org> AuthorDate: 2021-04-18 06:13:07 +0000 Commit: Hans de Graaff <graaff@gentoo.org> CommitDate: 2021-04-18 06:13:22 +0000 dev-ruby/asciidoctor: add ruby27 Bug: https://bugs.gentoo.org/764515 Package-Manager: Portage-3.0.17, Repoman-3.0.2 Signed-off-by: Hans de Graaff <graaff@gentoo.org> dev-ruby/asciidoctor/asciidoctor-2.0.12.ebuild | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
(In reply to Gary E. Miller from comment #0) > dev-ruby/asciidoctor-2.0.12 has RUBY_TARGETS="ruby26 ruby25" > > Upstream says Ruby 3.0 should work. ruby27 has now been added and was long overdue. ruby30 is still quiet a way off due to the huge dependency tree that needs to be checked and updates.
When I tried to bump ruby_target of dev-ruby/asciidoctor. I should also update dev-ruby/asciimath, dev-util/cucumber, dev-ruby/erubis, dev-ruby/haml, dev-ruby/rouge, dev-ruby/slim, dev-ruby/tilt, dev-ruby/temple, dev-ruby/abstract, dev-ruby/builder, dev-util/cucumber-core, dev-util/cucumber-expressions, dev-util/cucumber-wire, dev-ruby/diff-lcs, dev-ruby/gherkin, dev-ruby/multi_json, multi_test/multi_test, dev-util/cucumber-tag_expressions Should I try to update that packages and create bugs and PR? --- Marcin
(In reply to Marcin Woźniak from comment #6) > When I tried to bump ruby_target of dev-ruby/asciidoctor. > > I should also update dev-ruby/asciimath, dev-util/cucumber, dev-ruby/erubis, > dev-ruby/haml, dev-ruby/rouge, dev-ruby/slim, dev-ruby/tilt, > dev-ruby/temple, dev-ruby/abstract, dev-ruby/builder, > dev-util/cucumber-core, dev-util/cucumber-expressions, > dev-util/cucumber-wire, dev-ruby/diff-lcs, dev-ruby/gherkin, > dev-ruby/multi_json, multi_test/multi_test, dev-util/cucumber-tag_expressions > > Should I try to update that packages and create bugs and PR? In this case the dependency chain seems to hang on dev-ruby/builder and dev-ruby/tilt not having ruby30-compatible releases yet. I'm already tracking these because they also block a large group of other packages. Helping these upstreams release new ruby30-compatible versions is probably the most impactfull thing to do right now.
Has ruby27/ruby30/ruby31 nowadays.
