Dear Mamoru,Sorry for being non-responsive. I was pondering what to do about this, because frankly, we have not used the opportunity to update the `rubygems` package for ages. But since you have already spend the time to update the .spec, it makes easy to put off the retirement :) Thanks for the PR, it looks good to me and please proceed.
Vít Dne 16. 02. 26 v 15:15 Mamoru TASAKA via ruby-sig napsal(a):
Mamoru TASAKA via ruby-sig wrote on 2026/02/11 22:42:Hello, ruby-sig folks: -------- Forwarded Message -------- Subject: List of long term FTBFS packages to be retired in March Date: Tue, 10 Feb 2026 12:42:12 +0100 From: Miro Hrončok <[email protected]>Reply-To: Development discussions related to Fedora <[email protected]> To: Development discussions related to Fedora <[email protected]>, [email protected]Dear maintainers.Based on the current fail to build from source policy, the following packageswill be retired frrom rawhide cca on 2026-03-03. This is the third reminder. Policy:https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/The packages in rawhide were not successfully built at least since Fedora 41.This report is based on dist tags. Packages collected via:https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynbIf you see a package that was built, please let me know. If you see a package that should be exempted from the process,please let me know and we can work together to get a FESCo approval for that.If you see a package that can be rebuilt, please do so. Package (co)maintainers================================================================================ rubygems @ruby-packagers-sig, mtasaka, vondruchHow will we handle this?Although fixing rubygems.src FTBFS may not strictly needed (which means rubygems.src is to be retired on 2026-Mar), I think it is good (or not bad) that keeping rubygems.src alone buildableso that when desired we can update rubygems.src alone. For now I've prepared for updating rubygems.src to 4.0.6: https://src.fedoraproject.org/rpms/rubygems/pull-request/5 Mass rebuild for the above rubygems seems in good state: https://src.fedoraproject.org/rpms/rubygems/pull-request/5Note that 2026-Feb-17 is Fedora 44 beta freeze, and if possible I want to put inrubygems 4.0.6 into Fedora 44 before the above day.For now, once I am going to update rubygems.src to 4.0.3 to resolve FTBFS + keep currentrubygems behavior unchanged compared to rubygems.noarch from ruby.src, maybe tomorrow before F43-beta-freeze. Regards, Mamoru
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ 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://forge.fedoraproject.org/infra/tickets/issues/new
