On Mon, 23 Mar 2015 12:44:27 +0100 Josef Reidinger <[email protected]> wrote:
> On Mon, 23 Mar 2015 12:42:48 +0100 > Josef Reidinger <[email protected]> wrote: > > > On Mon, 23 Mar 2015 12:27:10 +0100 > > Stephan Kulow <[email protected]> wrote: > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > On 26.02.2015 22:40, Josef Reidinger wrote: > > > > On Thu, 26 Feb 2015 16:40:46 +0100 Stephan Kulow <[email protected]> > > > > wrote: > > > > > > > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > > >> > > > >> On 24.02.2015 19:48, Josef Reidinger wrote: > > > >>> > > > >>> 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. > > > >>> > > > >> > > > >> There are still plenty of problems: > > > >> > > > > > > > > for remaining stuff I found that reason is that > > > > rubygem-ruby-dbus do not build, so it use old version which do > > > > not work. As result yast2-storage do not work and all stuff > > > > depending on it even transitively do not work. > > > > > > > > rubygem-ruby-dbus do not work due to nokogiri do not build. So I > > > > try to fix nokogiri building and see if it helps. > > > > > > > nokogiri builds now but the yast modules show different failures > > > now > > > > > > Greetings, Stephan > > > > > > > > > > > > > will check it > > Martin - problem is failure in ruby-dbus, quite strange. Do you have > time to check it? > /usr/bin/ruby.ruby2.2 > [ 85s] ./test_env rake bare:spec > [ 85s] /usr/bin/ruby.ruby2.2: No such file or directory -- > (LoadError) [ 85s] rake aborted! > > > Josef Hi, Martin have more priority work, so I look at it and file /usr/bin/ruby.ruby2.2 is there, but problem looks like that /usr/bin/ruby is ruby 2.2 and /usr/bin/rake is rake for ruby 2.1. Is possible to make it somehow consistent? Or is possible to say rake to use ruby 2.1? Thanks Josef -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
