On Tue, 24 Feb 2015 17:44:38 +0100
Josef Reidinger
On Tue, 24 Feb 2015 09:52:15 +0100 Ancor Gonzalez Sosa
wrote: On 02/24/2015 09:20 AM, Stephan Kulow wrote:
Hi,
As an experiment I changed ruby in Factory to be default ruby, but leave 2.1 gems around. This is supposed to work, but in reality it's a mess :)
See the comments in https://build.opensuse.org/project/show/openSUSE:Factory:Staging:H
25 build failures and yast modules crash in installed system.
To my inexperienced eye, all the YaST failures seem to have a common root: yast2-ruby-bindings not building properly. 99% of YaST relies on those bindings.
I leave this staging prj open for the rest of the week in case someone wants to get active, after that I will pull back ruby 2.2 as default.
Greetings, Stephan
Yes, problem is that we have helper that collide with new ruby macro in 2.2. Working on fix.
Josef
Fix is in review now[1] and after merge we can check if it helps. But at least for yast2-bootloader I see crash of yardoc tool to generate documentation, so maybe there will be more problems. Josef [1] https://github.com/yast/yast-ruby-bindings/pull/138 -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org