And RubyGems does not generate documentation. Oh my:
Vít
Dne 17. 01. 22 v 16:45 Vít Ondruch napsal(a):
Dne 17. 01. 22 v 16:26 Vít Ondruch napsal(a):
>
> Dne 17. 01. 22 v 16:15 Vít Ondruch napsal(a):
>> 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
>
>
> Hm, I should probably really bump the Release of rubygem-json,
> otherwise we'll be in troubles. Previously, we were typically lucky
> that the independent package had lower NVR, this time, it wins.
>
>
>
>> comes to my mind and possibly rubygem-nokogiri?
Ha, it is not nokogiri but thread_order :facepalm:
V.
>
>
> And Nokogiri is RSpec dependency, that is the reason to prioritize it.
>
>
> Vít
>
>
>
>>
>>
>> Vít
>>
>>
>>
>> [1]
https://bugzilla.redhat.com/show_bug.cgi?id=2040380
>>
>> [2]
https://pagure.io/releng/issue/10538#comment-775197
>>