- openSUSE Ruby

[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

[opensuse-ruby] Ruby on Factory and packaging gems
by Klaus Kaempf 03 Mar '14

03 Mar '14

Hi, since there still is some confusion about Ruby in Factory and building rubygem packages, I have updated http://en.opensuse.org/Ruby and added http://en.opensuse.org/RubyPackaging In case your rubygem package fails to build on Factory http://en.opensuse.org/RubyPackaging#My_rubygem-.2A_package_fails_to_build lists typical problems and their solution. And remember, it's a Wiki ! ;-) Enjoy, Klaus -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

4 4

[opensuse-ruby] http://en.opensuse.org/Ruby
by Martin Vidner 01 Mar '14

01 Mar '14

... does not exist, but maybe it should :) What would you put there? Compare: http://en.opensuse.org/Python http://en.opensuse.org/Perl http://en.opensuse.org/Intercal http://en.opensuse.org/Category:Programming_language https://encrypted.google.com/search?q=en.opensuse.org+ruby -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

7 15

[opensuse-ruby] running gem2rpm on gem sources
by Adam Spiers 26 Feb '14

26 Feb '14

I have a couple of feature suggestions based on a private discussion with Klaus about packaging gems ... In the cases where gem are only available from upstream via a git tag rather than from rubygems.org (e.g. vagrant), gem2rpm only works with these extra steps: git clone git://github.com/mitchellh/vagrant.git cd vagrant gem build vagrant.gemspec gem2rpm vagrant-1.5.0.dev.gem > vagrant.spec It would be nice to automate this, given that tar_scm already builds the tarball from git. Would it be worth extending gem2rpm so that it can also operate on a given directory containing an unpacked gem, or a tarball? Or maybe it would be even nicer to build a gem2rpm source service which can automatically generate a .spec or update an existing .spec? -- 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] documentation for recent Ruby packaging changes?
by Adam Spiers 25 Feb '14

25 Feb '14

[moving this thread to opensuse-ruby because it will almost certainly affect others] Klaus Kaempf (kkaempf(a)suse.de) wrote: > * Adam Spiers <aspiers(a)suse.com> [Feb 25. 2014 15:13]: > > Will do - please can you point me at where the Ruby 2.1 changes are documented? > > The installation path for binary gem extensions and their documentation changed. > That's why all gems with binaries failed to build on d:l:r:e for Ruby > 2.1 > > https://build.opensuse.org/package/view_file/devel:languages:ruby/ruby/ruby… > reflects this in the %gem_base, %gem_extensions, %gem_doc_ext, and > %gem_platform macros. > > The latest rubygem-gem2rpm takes care of all this automatically. On 12.3 I updated to rubygem-gem2rpm-0.9.2-58.1.x86_64 and then got: $ gem2rpm rubygem-vagrant.spec /usr/lib64/ruby/1.9.1/rubygems/package/tar_input.rb:122:in `initialize': no metadata found in rubygem-vagrant.spec (Gem::Package::FormatError) from /usr/lib64/ruby/1.9.1/rubygems/package/tar_input.rb:20:in `new' from /usr/lib64/ruby/1.9.1/rubygems/package/tar_input.rb:20:in `open' from /usr/lib64/ruby/1.9.1/rubygems/package.rb:44:in `open' from /usr/lib64/ruby/1.9.1/rubygems/format.rb:62:in `from_io' from /usr/lib64/ruby/1.9.1/rubygems/format.rb:46:in `block in from_file_by_path' from /usr/lib64/ruby/1.9.1/open-uri.rb:35:in `open' from /usr/lib64/ruby/1.9.1/open-uri.rb:35:in `open' from /usr/lib64/ruby/1.9.1/rubygems/format.rb:45:in `from_file_by_path' from /usr/lib64/ruby/gems/1.9.1/gems/gem2rpm-0.9.2/lib/gem2rpm/package.rb:11:in `rescue in initialize' from /usr/lib64/ruby/gems/1.9.1/gems/gem2rpm-0.9.2/lib/gem2rpm/package.rb:11:in `initialize' from /usr/lib64/ruby/gems/1.9.1/gems/gem2rpm-0.9.2/lib/gem2rpm.rb:35:in `new' from /usr/lib64/ruby/gems/1.9.1/gems/gem2rpm-0.9.2/lib/gem2rpm.rb:35:in `convert' from /usr/lib64/ruby/gems/1.9.1/gems/gem2rpm-0.9.2/bin/gem2rpm:132:in `<top (required)>' from /usr/bin/gem2rpm:23:in `load' from /usr/bin/gem2rpm:23:in `<main>' On 13.1 I updated rubygem-gem2rpm-0.9.2-58.1.x86_64 and then got: $ gem2rpm rubygem-vagrant.spec /usr/lib64/ruby/1.9.1/rubygems/dependency.rb:247:in `to_specs': Could not find gem2rpm (>= 0) amongst [bigdecimal-1.1.0, erubis-2.7.0, io-console-0.3, jist-1.3.1, jist-1.1.0, json-1.5.5, minitest-2.5.1, rack-1.2.5, rake-0.9.2.2, rdoc-3.9.5] (Gem::LoadError) from /usr/lib64/ruby/1.9.1/rubygems/dependency.rb:256:in `to_spec' from /usr/lib64/ruby/1.9.1/rubygems.rb:1231:in `gem' from /usr/bin/gem2rpm:22:in `<main>' $ head -n1 `which gem2rpm` #!/usr/bin/ruby1.9 $ rpm -ql rubygem-gem2rpm | head /usr/bin/gem2rpm /usr/bin/gem2rpm-0.9.2 /usr/bin/gem2rpm-opensuse /usr/lib64/ruby/gems/2.0.0/cache/gem2rpm-0.9.2.gem /usr/lib64/ruby/gems/2.0.0/gems/gem2rpm-0.9.2 /usr/lib64/ruby/gems/2.0.0/gems/gem2rpm-0.9.2/AUTHORS /usr/lib64/ruby/gems/2.0.0/gems/gem2rpm-0.9.2/LICENSE /usr/lib64/ruby/gems/2.0.0/gems/gem2rpm-0.9.2/README /usr/lib64/ruby/gems/2.0.0/gems/gem2rpm-0.9.2/bin /usr/lib64/ruby/gems/2.0.0/gems/gem2rpm-0.9.2/bin/gem2rpm $ ls -l /etc/alternatives/ruby lrwxrwxrwx 1 root root 16 Oct 20 12:42 /etc/alternatives/ruby -> /usr/bin/ruby2.0* $ ruby2.0 `which gem2rpm` rubygem-vagrant.spec package metadata is missing in rubygem-vagrant.spec Maybe I'm doing something wrong? But either way, surely these changes should be communicated on opensuse-ruby and also documented on https://en.opensuse.org/openSUSE:Packaging_Ruby ? It's a worthy goal to maintain a tool which automates everything and makes gem packagers' lives easier. But things will inevitably go wrong, and when they do, pain will be significantly reduced by clear communication and documentation. On a related note, I learned today that there has been some change in approach to handling simultaneous installation of parallel versions of gems, in a way which can involve update-alternatives. But again I have not seen any public documentation or even discussion of this change. I'm very happy to be pointed to anything I missed. Thanks! Adam -- 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] the case of the two rubies
by Stephan Kulow 07 Feb '14

07 Feb '14

Hi, Now that Klaus' ruby merge is done, I switched the OBS project to use it - as a test bed of a "product". It's plain impossible to keep yast and update OBS on 13.1 ;( We have several things required by yast libruby2.0.so.2.0 is required by yast2-ruby-bindings and libstorage-ruby ruby(abi) == 2.0.0 is required by rubygem-ruby-dbus and rubygem-fast_gettext So not to break yast the OBS "product" needs to provide at least 4 packages linking against ruby 2.1. The libruby2.0 problem will be gone for future updates as we now have libruby2_1 as a special package, but the ruby(abi) problem will stay and as I said before: making /usr/bin/ruby an update-alternative is only a solution as long as rubygem-fast_gettext isn't required by OBS with a different ruby abi. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

4 6

[opensuse-ruby] A new packaging scheme for Ruby 2.1
by Klaus Kaempf 30 Jan '14

30 Jan '14

Hi, going forward, Ruby becomes more important in the openSUSE and SLES codebase. This is why Coolo asked me to come up with a new Ruby packaging scheme. Read on to learn about my current thinking in this regard. What are the goals ? 1. revert the ruby, rubyXY, and ruby-common split Initially done to allow multiple Ruby versions in parallel, it wasn't really used and developers use rvm or rbenv to achieve the same effect. From a buildservice perspective, this split cause more headaches than it provided value. 2. Ruby will be part of inst-sys (for YaST) As you know, size matters. Looking at the ruby20 package, it has an install size of 18MB However, 'du -sh /usr/share/doc/packages/ruby20' reports 5.9 MB just for documentation. 3. The new package scheme should support maintenance better A split between binaries, shared libraries, and Ruby stdlib seems desirable Packaging proposal: I'd like to generate the following packages for Ruby 2.1 1. ruby-2.1 This would provide binaries (ruby, irb, rake, gem, ...) and a minimal set of documentation (changelog, readme, news, ...) 2. libruby2 This would only provide the libruby2.1.so.2.0.0 shared library 3. ruby-stdlib This would provide the /usr/lib64/ruby/2.1.0/ directory tree. 4. ruby-doc This would provide the full Ruby documentation including samples. 5. ruby-macros ? This would be a new name for ruby-common, a package only used for building ruby GEM packages. Actually, I'm not happy about the name. It should reflect the package usage. ruby-devel-build or ruby-build-macros could be alternatives. 6. ruby-devel, ruby-devel-extra, ruby-doc-ri These would stay unchanged. Comments ? Thanks, Klaus -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

8 32