Dne 25. 12. 24 v 13:57 Mamoru TASAKA via ruby-sig napsal(a):
Vít Ondruch via ruby-sig wrote on 2024/12/24 2:09:
Dear Rubyists,
This is likely my last update prior official Ruby 3.4 release. So here I am with update to a11bb36316. The build is available here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=127139135
While the mini mass rebuild is churning here:
https://copr.fedorainfracloud.org/coprs/vondruch/mpb.30/builds/
What I find a bit unfortunate that FESCo was not able to approve the change. But I hope they'll approve in the ticket and we will be able to start with the mass rebuild with the new year. Until then, please give it a try or better, enjoy some well deserve rest.
See you in new year.
Vít
Well, looks like after https://github.com/ruby/ruby/commit/9e0eb9778d557ef59a541a65be658040951de5be...
(this is from: https://github.com/rubygems/rubygems/pull/8340 )
it seems that $ gem install --document=rdoc,ri (in %gem_install) no longer generates rdoc/ri documentation even if the above option is explicitly specified...
(The above commit is after the commit you checked: a11bb36316)
So... how should we handle this? Revert the above change (in lib/rubygems/rdoc.rb) or report rubygems upstream?
Just quickly checking, isn't this the root cause?
https://github.com/ruby/rdoc/pull/1171
The question is if we have everything in the right place? And if the `--document` option works correctly, because it it should not be defined or report some error if e.g. the plugin would not be loaded.
Vít
Regards, Mamoru