Policy re Gems that don't have RPMs yet?
by Philip Rhoades
People,
A while ago I posted a note on the Devise forum asking if anyone was
going to build an RPM for Fedora but didn't get any responses at all -
no-one even viewed the post! What happens with Gems in this category?
Am I supposed to do anything? Add a request somewhere? Use the Gem
instead of an RPM while I wait for someone to do the work for creating
the RPM? Should I bite the bullet and see how to produce the RPM
myself?
Regards,
Phil.
--
Philip Rhoades
GPO Box 3411
Sydney NSW 2001
Australia
E-mail: phil(a)pricom.com.au
9 years, 11 months
JRuby 1.7.2 built
by Bohuslav Kabrda
Hi all,
I've finally finished building JRuby 1.7.2 [1]. Hoooraaay!
For now, it is only built in the f19-ruby tag, so if you want to try (please do!), you have to install from there.
If you find anything that doesn't seem right about the package, let me know and I'll try to fix ASAP.
In the meantime, I'll start looking into updating to 1.7.3, which needs some dependencies that aren't in Fedora yet (since I was not sure that I'd have enough time to package these, I thought it would be safer to build 1.7.2 first).
--
Regards,
Bohuslav "Slavek" Kabrda.
[1] http://koji.fedoraproject.org/koji/taskinfo?taskID=5060699
10 years, 3 months
patch: ruby 2.0.0 on el6
by Kaj Niemi
Hi,
In case anyone is interested, attached is a trivial patch which makes it easy to use Fedora's ruby.spec on EL6. The diff is against Fedora's master branch ruby.spec. One also needs to build libyaml and rubypick on EL6, both build fine. I hope the patch is useful to someone else than me. :-)
Kaj
--
Kaj J. Niemi
BaseN Corporation
<kajtzu(a)basen.net>
FI +358 45 63 12000
10 years, 3 months
Ruby 2.0.0 rebuild status
by Vít Ondruch
Hi,
As you might noticed [1], I already build some packages. However, I
cannot continue, since between Ruby 2.0.0 rev39237 and rev39387 I build
in Koji was introduced regression, i.e. shebangs in rubygems's stubs are
wrongly expanded to /bin/ruby instead of /usr/bin/ruby, which causes
issues such as:
DEBUG util.py:314: Executing command: ['/usr/bin/yum-builddep',
'--installroot', '/var/lib/mock/f19-ruby-1607698-272256/root/',
'/var/lib/mock/f19-ruby-1607698-272256/root///builddir/build/SRPMS/rubygem-ffi-1.4.0-1.fc19.src.rpm']
with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash',
'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'echo -n "<mock-chroot>"', 'HOME':
'/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'}
DEBUG util.py:264: Getting requirements for rubygem-ffi-1.4.0-1.fc19.src
DEBUG util.py:264: --> ruby-devel-2.0.0.0-0.1.r39387.fc19.x86_64
DEBUG util.py:264: --> rubygems-devel-2.0.0-0.1.r39387.fc19.noarch
DEBUG util.py:264: --> libffi-devel-3.0.11-2.fc19.x86_64
DEBUG util.py:264: --> rubygem-rspec-2.12.0-3.fc19.noarch
DEBUG util.py:264: Error: Package:
rubygem-diff-lcs-1.1.3-2.1.fc19.noarch (build)
DEBUG util.py:264: Requires: /bin/ruby
DEBUG util.py:264: Error: Package:
rubygem-rspec-core-2.12.2-2.fc19.2.noarch (build)
DEBUG util.py:264: Requires: /bin/ruby
DEBUG util.py:264: Error: Package: rubygem-rake-10.0.3-2.fc19.noarch
(build)
DEBUG util.py:264: Requires: /bin/ruby
I suspect that rev39320 is the offending patch, but it needs to be
investigated. I am really sorry for the delays. Any help is appreciated.
Vít
[1]
https://koji.fedoraproject.org/koji/builds?inherited=0&tagID=232&order=-b...
10 years, 3 months
Fwd: Re: #5463: Koji tag for Ruby 2.0.0 / JRuby 1.7
by Vít Ondruch
Hi everybody,
We obtained side tag for Ruby 2.0.0 rebuild. So these are steps which
will follow:
1) Build rubypick
2) Merge my ruby-2.0 branch into master, update to the latest revision
available in ruby_2_0_0 branch. I would like to ask you for a review of
the spec. There are not all patches, namely the webrick test suite
failure [1] (on the other hand, I did not met this issue recently).
3) Bootstrap RSpec
4) Bootstrap other test frameworks
5) Build all other libraries.
Please do not update your libraries or build them into the side tag
during this period.
Please note that there might arise need to upgrade or fix your library
to fix the compatibility or other build issues. If needed, I will do so.
If you don't want me to touch your packages, please speak out now.
And of course, any help with rebuild is appreciated, since the rebuild
should be done before branching F19, it is roughly in 3 weeks.
I'll try to keep you informed about all steps I'll do.
Thank you
Vít
[1] https://bugs.ruby-lang.org/issues/6573
-------- Původní zpráva --------
Předmět: Re: #5463: Koji tag for Ruby 2.0.0 / JRuby 1.7
Datum: Wed, 20 Feb 2013 15:46:36 -0000
Od: Fedora Release Engineering <rel-eng(a)fedoraproject.org>
Komu: undisclosed-recipients:;
#5463: Koji tag for Ruby 2.0.0 / JRuby 1.7
------------------------------+----------------------
Reporter: vondruch | Owner: ausil
Type: task | Status: assigned
Milestone: Fedora 19 Alpha | Component: koji
Resolution: | Keywords:
Blocked By: | Blocking:
------------------------------+----------------------
Changes (by ausil):
* owner: rel-eng@… => ausil
* status: new => assigned
Comment:
f19-ruby tag and target created, you will need to do "fedpkg build
--target=f19-ruby" please let us know when you are done so we can merge
it back in
--
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/5463#comment:1>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project
10 years, 3 months
Mass rebuild script and %gem_install macro
by Vít Ondruch
Hi,
I have pushed repository [1] with script I am going to use to migrate
Ruby packages in Fedora. It is pretty rough at now, but will see what
can we do with it. The most important is the f19.rb script [1], which is
responsible for the conversion of your .spec file to F19 compliant one.
In short, it does following changes:
1) ruby(abi) -> ruby(release)
2) gem install -> %gem_install
You my wonder what is the 2nd point. I am going to introduce
%gem_install macro [3], which will be responsible for gems installation
(as the name imply ;). The main reason is that RubyGems 2.0 changes how
the documentation is generated. I.e. by default, only RI documentation
is generated while we used to have RI as well as RDoc. This macro allows
us to specify various installation defaults globally, without need of
editing each .spec file every time.
You might admit, that it would be nice to macroize other parts .spec
file as well (such as 'gem build' or 'gem spec'), but I am running out
of time, so it will need to wait for next Fedora release.
As always, any feedback is welcome.
Vít
[1] https://github.com/voxik/fermig
[2] https://github.com/voxik/fermig/blob/master/f19.rb
[3] https://fedorahosted.org/fpc/ticket/256
10 years, 3 months
warning: rspec.rb provided by rubygem-rspec
by Mo Morsi
rspec1 shipped rspec.rb as part of the rubygem-rspec package
rspec2 shipped rspec.rb as part of rubygem-rspec-core, so to assist in
that migration we left rubygem-rspec at 1.x for the time, and converted
packages to depend on rspec-core. When the migration was done, we
updated rubygem-rspec.
rubygem-rspec was just updated in rawhide to 2.11.0 which again provides
rspec.rb (which was removed from rspec-core 2.11.0). So packages just
depending on rspec-core will now need to pull in rspec to be able to use
rspec.rb
The fix is easy enough, just a word of warning if you see related errs
in broken builds w/ gem packages starting in rawhide.
rspec also depends on an updated version of diff-lcs, which is available
in rawhide (thanks mamoru & vit!)
-Mo
10 years, 3 months