Mamoru TASAKA via ruby-sig wrote on 2025/12/21 22:55:
Mamoru TASAKA via ruby-sig wrote on 2025/12/20 22:24:
Mamoru TASAKA via ruby-sig wrote on 2025/12/16 0:01:
Hello, ruby-sig folks

Again I tried rebuilding rubygem-XXX packages with 4.0.0dev (2025-12-12 master 
2f151e76b5) .
Currently (ignoring rubygem-jekyll related packages) 9 packages FTBFS, which is 
in better state
than before.


Then:

minitest 6.0.0 landed on ruby4.0.0dev 3 days ago (from 5.27.0), this now seems 
to cause new FTBFS for 47 packages.
rdoc 7.0.0 (then 7.0.1) launded 2 days ago (from 6.17.0), this now seems to 
cause new FTBFS for 6 packages.

Honestly I am at a loss...

For minitest, since many packages are not ready for minitest6, I submitted a 
review request for
minitest5:
https://bugzilla.redhat.com/show_bug.cgi?id=2424184

I would appreciate it if someone would review this (review swap is welcomed).


A.
Build errors with new rdoc 7.0.0 "changes" is now fixed in rdoc side (I've 
verified):
https://github.com/ruby/rdoc/pull/1531

With ruby4.0, rdoc should be upgraded to 7.0.3 + applying the above PR.

B.
Now looking into build failures with minitest 6.

For rubygem-rack and its series (like rubygem-rack-XXX and rubygem-rackup),
due to minitest 6 change with removing minitest/spec expectations from
ruby's "generic" Object:

https://github.com/minitest/minitest/blob/edd37ce7240a645054485b8c470927765e65351b/History.rdoc?plain=1#L30

this causes lots of errors with "plain" rubygem-minitest 6
(with "plain" minitest 5, these were warnings).

Since rack and its series already uses minitest-global_expectations, I've 
submitted review requet for this:
https://bugzilla.redhat.com/show_bug.cgi?id=2425714

I would appreciate it if someone would review the above (as before, review swap 
is appreciated.)
(Again, for maintainers using rubygem-rack, perhaps the above package should 
ease maintenance.)

Regards,
Mamoru
--
_______________________________________________
ruby-sig mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to