April 2014 - openSUSE Ruby - openSUSE Mailing Lists

[opensuse-ruby] how to make gem package depend on specific Ruby version?
by Adam Spiers 02 May '14

02 May '14

Vagrant 1.5.4 depends on Ruby >= 2.0.0: https://github.com/mitchellh/vagrant/pull/3581 What's the correct way to ensure that rubygem-vagrant builds against ruby20 on openSUSE 12.3 and 13.1? On 12.3, by default (i.e. without any explicit dependencies on a Ruby version) it builds against 1.9 and then fails as soon as it encounters use of ** keyword parameters. If I use the dependencies suggested by gem2rpm via the .spec template: BuildRequires: ruby-macros >= 3 Requires: ruby >= 2.0.0 BuildRequires: ruby >= 2.0.0 (I guess the >= 2.0.0 might have come from my patch in the above pull request) then I get: $ osc build openSUSE_13.1 Building rubygem-vagrant.spec for openSUSE_13.1/x86_64 Getting buildinfo from server and store to /home/adam/SUSE/OBS/home/aspiers/branches/devel/languages/ruby/extensions/rubygem-vagrant/.osc/_buildinfo-openSUSE_13.1-x86_64.xml Getting buildconfig from server and store to /home/adam/SUSE/OBS/home/aspiers/branches/devel/languages/ruby/extensions/rubygem-vagrant/.osc/_buildconfig-openSUSE_13.1-x86_64 buildinfo is broken... it says: unresolvable: nothing provides ruby >= 2.0.0 and the same for 12.3. Weirdly, if I drop the patch-level from the dependencies, i.e. Requires: ruby >= 2.0 BuildRequires: ruby >= 2.0 then it builds fine. I'm guessing that this is because Ruby on vanilla 13.1 was packaged with version 2.0 rather than version 2.0.0. What was the reason for that decision? If instead I try building against d:l:r ... $ osc build devel_languages_ruby_openSUSE_12.3 or $ osc build devel_languages_ruby_openSUSE_13.1 then it builds against 2.1.0 and fails to install: $ sudo rpm -ihv /var/tmp/build-root/devel_languages_ruby_openSUSE_13.1/x86_64/home/abuild/rpmbuild/RPMS/x86_64/rubygem-vagrant-1.5.4-0.x86_64.rpm error: Failed dependencies: ruby >= 2.0.0 is needed by rubygem-vagrant-1.5.4-0.x86_64 ruby(abi) = 2.1.0 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:bundler) >= 1.5.2 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:childprocess:0.5) >= 0.5 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:erubis:2.7) >= 2.7 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:i18n:0.6) >= 0.6 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:listen:2.7) >= 2.7.1 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:log4r) < 1.1.11 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:log4r:1.1) >= 1.1.9 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:net-scp:1.1) >= 1.1 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:net-ssh) >= 2.6.6 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:net-ssh) < 2.8.0 is needed by rubygem-vagrant-1.5.4-0.x86_64 rubygem(2.1.0:rb-kqueue:0.2) >= 0.2 is needed by rubygem-vagrant-1.5.4-0.x86_64 $ sudo zypper in /var/tmp/build-root/devel_languages_ruby_openSUSE_13.1/x86_64/home/abuild/rpmbuild/RPMS/x86_64/rubygem-vagrant-1.5.4-0.x86_64.rpm Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides rubygem(2.1.0:bundler) >= 1.5.2 needed by rubygem-vagrant-1.5.4-0.x86_64 Solution 1: do not install rubygem-vagrant-1.5.4-0.x86_64 Solution 2: break rubygem-vagrant-1.5.4-0.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): Thanks! -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

2 2

[opensuse-ruby] update-alternatives with gems
by Adam Spiers 30 Apr '14

30 Apr '14

Please can someone document how update-alternatives works with our d:l:r:e gem packaging strategy, and also *why* we are using it? I heard good explanations already (thanks darix), so personally I am now convinced (even though my tired brain already forgot some of the details), but other people have a right to know too. Previously I had to rely on a combination of guesswork and pestering busy people, and this approach does not scale. It's not enough to say "just use gem2rpm", because guess what ;) things go wrong, and then it's really hard to debug without fully understanding the design. Also, it's not a real policy until it's documented. Yes it's an annoying / boring up-front cost, but the break-even will be quick. I suggest https://en.opensuse.org/openSUSE:Packaging_Ruby as a suitable location. Thanks a lot in advance! -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

1 0

[opensuse-ruby] bug in rubygems dependency strategy
by Adam Spiers 30 Apr '14

30 Apr '14

I think I found a bug in our current rubygems automatic dependency system[0]. It's similar to the problem darix mentioned almost 3 years ago[1], and I can demonstrate with the real world example I just found ... vagrant's upstream .gemspec file contains this dependency range: s.add_dependency "net-ssh", ">= 2.6.6", "< 2.8.0" This translates to the following rpm Requires: auto: rubygem(1.9.1:net-ssh) >= 2.6.6 auto: rubygem(1.9.1:net-ssh) < 2.8.0 Unfortunately the only versions available on 12.3 from d:l:r:e and the base OS are as follows: S | Name | Type | Version | Arch | Repository --+---------------------+---------+-------------+--------+-------------------------------- i | rubygem-net-ssh | package | 2.8.0-26.1 | x86_64 | Ruby Extensions (openSUSE_12.3) v | rubygem-net-ssh | package | 2.6.1-2.1.1 | x86_64 | openSUSE-12.3-Oss | rubygem-net-ssh-2_1 | package | 2.1.4-2.7 | x86_64 | Ruby Extensions (openSUSE_12.3) | rubygem-net-ssh-2_2 | package | 2.2.2-3.7 | x86_64 | Ruby Extensions (openSUSE_12.3) So in this situation, if I zypper install my vagrant package, I end up with the following simultaneously installed: rubygem-net-ssh-2_1-2.1.4-2.7.x86_64 rubygem-net-ssh-2.8.0-26.1.x86_64 The first satisfies the < 2.8.0 requirement, and the second satisfies the >= 2.6.6 requirement, but neither of them give vagrant what it really wants. So when I run it, I get: /usr/lib64/ruby/1.9.1/rubygems/dependency.rb:247:in `to_specs': Could not find net-ssh (< 2.8.0, >= 2.6.6) amongst [RedCloth-4.2.9, [...snipped...], net-ssh-2.8.0, net-ssh-2.1.4, [...snipped...], vagrant-1.5.4, [...snipped...]] (Gem::LoadError) from /usr/lib64/ruby/1.9.1/rubygems/specification.rb:777:in `block in activate_dependencies' from /usr/lib64/ruby/1.9.1/rubygems/specification.rb:766:in `each' from /usr/lib64/ruby/1.9.1/rubygems/specification.rb:766:in `activate_dependencies' from /usr/lib64/ruby/1.9.1/rubygems/specification.rb:750:in `activate' from /usr/lib64/ruby/1.9.1/rubygems.rb:1232:in `gem' from /usr/bin/vagrant:22:in `<main>' This looks like a fundamental limitation of rpm's version requirement system, and I can't think of a good workaround right now :-/ Does anyone have a good idea how to fix this? The upstream docs seem blissfully unaware of the problem[2]. [0] as described by https://en.opensuse.org/openSUSE:Packaging_Ruby#How_gem_dependencies_are_au… [1] http://lists.opensuse.org/opensuse-ruby/2011-07/msg00000.html [2] http://www.rpm.org/wiki/PackagerDocs/MultipleVersions -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

4 10

[opensuse-ruby] [SOLVED] spurious rpmlint warnings for /usr/share/ri/*
by Adam Spiers 29 Apr '14

29 Apr '14

Hi all, I'm working on updating rubygem-vagrant, and I'm getting some spurious warnings from rpmlint when building on 12.3: [ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Environment/default_private_key_path-i.ri [ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Errors/VagrantError/extra_data-i.ri [ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/UI/Interface/opts-i.ri [ 23s] rubygem-vagrant-doc.x86_64: W: wrong-file-end-of-line-encoding /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Environment/home_path-i.ri [ 23s] This file has wrong end-of-line encoding, usually caused by creation or [ 23s] modification on a non-Unix system. It could prevent it from being displayed [ 23s] correctly in some circumstances. [snipped] [ 23s] rubygem-vagrant-doc.x86_64: W: unexpanded-macro /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Util/Downloader/download%21-i.ri %21 [ 23s] rubygem-vagrant-doc.x86_64: W: unexpanded-macro /usr/lib64/ruby/gems/1.9.1/doc/vagrant-1.5.4/ri/Vagrant/Registry/has_key%3f-i.ri %3f [ 23s] This package contains a file whose path contains something that looks like an [ 23s] unexpanded macro; this is often the sign of a misspelling. Please check your [ 23s] specfile. [ 23s] [ 23s] 4 packages and 0 specfiles checked; 0 errors, 78 warnings. I eventually tracked them down to a bug in rpmlint 1.4 (which got propagated to rpmlint-mini) which was fixed before rpmlint 1.5: http://sourceforge.net/p/rpmlint/code/ci/7ebdb2a This explains why the warnings don't appear when building on 13.1 (which has rpmlint 1.5). I thought I had seen these explained somewhere else before; maybe it was: https://bugzilla.redhat.com/show_bug.cgi?id=850786 but unfortunately I get an error when I visit the upstream ticket: http://rpmlint.zarb.org/cgi-bin/trac.cgi/ticket/569 Anyway, I couldn't find any openSUSE-related references to the issue, so I thought it was worth posting about it here for reference, in case other people google the issue in the future (unlikely since 12.3 is old now, but you never know ...) Would it be worth updating rpmlint on 12.3 to address these? -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

1 0