Vít Ondruch wrote on 2022/01/18 0:15:
Hi,
It is time of the year when new version of Ruby was released upstream and we should land
it in Fedora. Unfortunately, the change proposal was approved just last Thursday and on
top of that, rebase of libffi broke Ruby (I am going to disable the failing test cases
for the moment and hope for the best). So this brings us into situation, where won't have
enough time prior Fedora Mass rebuild. I have discussed this a bit with relengs and one
of the options would be to build Ruby early during the mass rebuild and fix the outfall
later. I shared the proposal in the Fedora Mass rebuild ticket [2]. One downside would be
that in case of problems, we could not trigger our contingency plan, which is "drop
our side tag". But I hope we won't need that.
Any thoughts?
My fist concern is that maybe we should build more then just Ruby. rubygem-json
comes to my mind and possibly rubygem-nokogiri?
Vít
[1] https://bugzilla.redhat.com/show_bug.cgi?id=2040380
[2] https://pagure.io/releng/issue/10538#comment-775197
My light idea is that as "Change Checkpoint" and "Branch Fedora Linux 36 from
Rawhide" happends
on 2022/Feb/08 (Tue), I think we have enough time even if we start rebuilding
with ruby31 beginning at,
say, 2022/Jan/24 (Mon) or Jan/25 (if mass rebuild "really" begins tomorrow).
Regards,
Mamoru
_______________________________________________
ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org
To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.org
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/ruby-sig@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
