Vít Ondruch via ruby-sig wrote on 2024/11/28 18:10:
Dne 27. 11. 24 v 1:07 Mamoru TASAKA via ruby-sig napsal(a):
Vít Ondruch via ruby-sig wrote on 2024/11/27 0:48:
Currently the failures I feel difficult to fix are:
- rubygem-websocket
https://copr.fedorainfracloud.org/coprs/vondruch/mpb/build/8312136/
Due to https://bugs.ruby-lang.org/issues/20265 change, NEWOBJ macro is removed, then currently rubygem-websocket really fails to compile. For now I have no idea how to replace this macro.
I can see just the `base64` issue. Does the NEWOBJ thing pops up once the `base64` issue is fixed?
Sorry, I was completely confused. Actually this is rubygem-serialport . https://copr.fedorainfracloud.org/coprs/vondruch/mpb/build/8312122/
- I have asked upstream for migration path:
https://bugs.ruby-lang.org/issues/20265#note-5
- The question is if there is future in this project:
https://github.com/hparra/ruby-serialport/discussions/77
We have rubygem-serialport in Fedora due to rubygem-icaro dependency. However, this also seems to be dead. Maybe the most meaningful step ATM is to open ticket against rubygem-serialport with all the information and warning we are going to break the packages.
I think opening a ticket against rubygem-serialport (on bugzilla) can be the first step for the time being. For now "me" have no idea how to fix rubygem-serialport srpm (even if I have read the above ruby-lang issue/ticket...)
Regards, Mamoru
Thoughts?
Vít
Regards, Mamoru