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 -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org

-----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: yast2-storage: [ 151s] /usr/lib64/ruby/vendor_ruby/2.2.0/yast/yast.rb:162:in `import_pure': component cannot import namespace 'Storage' (NameError) [ 151s] from /usr/lib64/ruby/vendor_ruby/2.2.0/yast/yast.rb:162:in `import' [ 151s] from /home/abuild/rpmbuild/BUILD/yast2-storage-3.1.52/test/storage_utils_configure_snapper_test.rb:8:in `' yast2-packager: [ 157s] 1) #Yast::SpaceCalculationClass:0x00000002990b18 #size_from_string converts string without units bytes [ 157s] Failure/Error: expect(Yast::SpaceCalculation.size_from_string("42.00")).to eq(42) [ 157s] [ 157s] expected: 42 [ 157s] got: false rubygem-yast-rake: error: File not found: /home/abuild/rpmbuild/BUILDROOT/rubygem-yast-rake-0.1.10-2.2.x86_64/usr/lib64/ruby/gems/cache/yast-rake-0.1.10.gem yast2-iscsi-client: [ 117s] /usr/lib64/ruby/gems/2.2.0/gems/yard-0.8.7.6/lib/yard/parser/ruby/ruby_parser.rb:460:in `block (2 levels) in on_params': undefined method `type' for 54616:Fixnum (NoMethodError) yast2-kdump: [ 89s] 1) #use_fadump returns true if fadump is supported on this architecture [ 89s] Failure/Error: expect(Yast::Kdump.use_fadump(true)).to eq(true) [ 89s] NoMethodError: [ 89s] undefined method `[]=' for nil:NilClass [ 89s] # ./src/modules/Kdump.rb:967:in `use_fadump' [ 89s] # ./test/fadump_test.rb:25:in `block (2 levels) in ' yast2-network: [ 153s] 1) LanItemsClass#BuildLanOverview returns translated network device textual description for wlan device [ 153s] Failure/Error: overview = Yast::LanItems.BuildLanOverview [ 153s] NoMethodError: [ 153s] undefined method `CheckEmptyName' for #Yast::LanItemsClass:0x000000023661c0 libsolv: [ 192s] found conflict of libsolv-demo-0.6.8-3.3.x86_64 with ruby-solv-0.6.8-3.3.x86_64: [ 192s] - /usr/bin/solv autoyast2: [ 122s] 1) Yast::AutoInstallRules #ProbeRules reads installed product properties from content file [ 122s] Failure/Error: expect(Yast::Kernel).to receive(:GetPackages).and_return([]) [ 122s] NameError: [ 122s] uninitialized constant Yast::Kernel rubygem-nokogiri: [ 141s] error: File not found: /home/abuild/rpmbuild/BUILDROOT/rubygem-nokogiri-1.6.6.2-3.3.x86_64/usr/lib64/ruby/gems/2.2.0/doc/extensions/x86_64-linux/2.2.0 Greetings, Stephan -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org

On Thu, 26 Feb 2015 16:40:46 +0100 Stephan Kulow 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:

What I found so far: there is bug in yardoc that cause failure on ruby2.2. Result is that these packages failed: yast2-iscsi-client yast2-bootloader It turns out that it is actually bug in ruby 2.2 itself. see https://github.com/lsegal/yard/issues/825 Other packages are in progress. -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org

On Thu, 26 Feb 2015 22:40:05 +0100 Josef Reidinger wrote:

On Thu, 26 Feb 2015 16:40:46 +0100 Stephan Kulow 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.

Josef

Root of issue is that rubygem no longer place these files under doc. I think we need to modify our macros to not expect it there: [ 132s] 1737838 4 drwxr-xr-x 3 abuild abuild 4096 Feb 22 15:52 /home/abuild/rpmbuild/BUILDROOT/rubygem-nokogiri-1.6.6.2-3.3.x86_64/usr/lib64/ruby/gems/2.1.0/doc/extensions [ 132s] 1737839 4 drwxr-xr-x 3 abuild abuild 4096 Feb 22 15:52 /home/abuild/rpmbuild/BUILDROOT/rubygem-nokogiri-1.6.6.2-3.3.x86_64/usr/lib64/ruby/gems/2.1.0/doc/extensions/x86_64-linux [ 132s] 1737840 4 drwxr-xr-x 3 abuild abuild 4096 Feb 22 15:52 /home/abuild/rpmbuild/BUILDROOT/rubygem-nokogiri-1.6.6.2-3.3.x86_64/usr/lib64/ruby/gems/2.1.0/doc/extensions/x86_64-linux/2.1.0 [ 132s] 1737841 4 drwxr-xr-x 2 abuild abuild 4096 Feb 22 15:52 /home/abuild/rpmbuild/BUILDROOT/rubygem-nokogiri-1.6.6.2-3.3.x86_64/usr/lib64/ruby/gems/2.1.0/doc/extensions/x86_64-linux/2.1.0/nokogiri-1.6.6.2 [ 132s] 1737843 4 -rw-r--r-- 1 abuild abuild 209 Feb 22 15:52 /home/abuild/rpmbuild/BUILDROOT/rubygem-nokogiri-1.6.6.2-3.3.x86_64/usr/lib64/ruby/gems/2.1.0/doc/extensions/x86_64-linux/2.1.0/nokogiri-1.6.6.2/page-gem_make_out.ri [ 132s] 1737842 4 -rw-r--r-- 1 abuild abuild 215 Feb 22 15:52 /home/abuild/rpmbuild/BUILDROOT/rubygem-nokogiri-1.6.6.2-3.3.x86_64/usr/lib64/ruby/gems/2.1.0/doc/extensions/x86_64-linux/2.1.0/nokogiri-1.6.6.2/page-gem_build_complete.ri [ 132s] 1737844 40 -rw-r--r-- 1 abuild abuild 40192 Feb 22 15:52 /home/abuild/rpmbuild/BUILDROOT/rubygem-nokogiri-1.6.6.2-3.3.x86_64/usr/lib64/ruby/gems/2.1.0/doc/extensions/x86_64-linux/2.1.0/nokogiri-1.6.6.2/page-mkmf_log.ri ^^^ see that it is only for 2.1.0 but not for 2.2.0. I think it need some modifications in /usr/lib/rpm/gem_packages.template which is part of ruby-common and it is not obvious source codes, so I let modifications for darix. Josef -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org

On 2015-03-04 09:25:39 +0100, Stephan Kulow wrote:

Any ETA? I don't like the staging prj idling around - so if there is no light at the horizon I would close the ruby 2.2 case ;(

ruby 2.2 support is now in devel:languages:ruby. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org

On Mon, 23 Mar 2015 12:27:10 +0100 Stephan Kulow 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 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 -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org

On Mon, 23 Mar 2015 12:44:27 +0100 Josef Reidinger wrote:

On Mon, 23 Mar 2015 12:42:48 +0100 Josef Reidinger wrote:

...

On Mon, 23 Mar 2015 12:27:10 +0100 Stephan Kulow 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 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: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org