Except I have bumped Psych release instead of Json :facepalm: Here is
another attempt:
Vít
Dne 18. 01. 22 v 17:29 Vít Ondruch napsal(a):
This is the build which should be ready for mass rebuild:
https://koji.fedoraproject.org/koji/taskinfo?taskID=81407116
Dne 18. 01. 22 v 16:45 Pavel Valena napsal(a):
> Also, latest changes for Ruby 3.1 PR (106; commit
> a81f20ad712c29df4c847919cc46bb7bc19ca455) fail to build for me:
>
https://copr.fedorainfracloud.org/coprs/pvalena/ruby-testing/builds/
>
> Failures like:
> ```
> Expected #<Process::Status: pid 89350 SIGABRT (signal 6) (core
> dumped)> to be success?.
> ```
This is, I believe, the FFI issue I have mentioned somewhere.
Vít
>
> Not sure what's the cause.
> Pavel
>
> On Tue, Jan 18, 2022 at 12:53 PM Vít Ondruch <vondruch(a)redhat.com>
> wrote:
>> So this was (my) fault of missing dependencies on our side:
>>
>>
https://src.fedoraproject.org/fork/vondruch/rpms/ruby/c/f0b9944594f3ec768...
>>
>>
>>
https://src.fedoraproject.org/fork/vondruch/rpms/ruby/c/a81f20ad712c29df4...
>>
>>
>> Handling of default gems should be generally improved to prevent such
>> issues in the future. Not sure if and when I should phase out the
>> independent default gems, that could also improve the situation at
>> least
>> a bit.
>>
>> But it still leaves bitter taste behind, because the issue was not
>> properly reported IMO. This line [1] completely hides the issue. Not
>> sure how to properly handle such situations. I have just left a few
>> notes behind [2].
>>
>>
>> Vít
>>
>>
>> [1]
>>
https://github.com/rubygems/rubygems/blob/12aeef6ba9a3be0022be9934c1a3e4c...
>>
>>
>> [2]
>>
https://github.com/rubygems/rubygems/issues/5295#issuecomment-1015329337
>>
>>
>>
>>
>> Dne 17. 01. 22 v 18:27 Vít Ondruch napsal(a):
>>> And RubyGems does not generate documentation. Oh my:
>>>
>>>
>>>
https://github.com/rubygems/rubygems/issues/5295
>>>
>>>
>>>
>>> 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
>>>>>>
>> _______________________________________________
>> ruby-sig mailing list -- ruby-sig(a)lists.fedoraproject.org
>> To unsubscribe send an email to ruby-sig-leave(a)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.fedoraprojec...
>> Do not reply to spam on the list, report it:
>>
https://pagure.io/fedora-infrastructure
> _______________________________________________
> ruby-sig mailing list -- ruby-sig(a)lists.fedoraproject.org
> To unsubscribe send an email to ruby-sig-leave(a)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.fedoraprojec...
> Do not reply to spam on the list, report it:
>
https://pagure.io/fedora-infrastructure