Hi everybody,
Since Ruby 2.2 is going to be released during Christmas and -preview1
release is imminent (this Wednesday?), it is probably time to start
looking into its packaging. So here is the updated .spec file [1] and
scratch build [2], which can be finally build on all platforms. Sorry,
no Copr for you, since Ruby's build fails there due to old RHEL kernel :/.
What has changed from packaging point of view? Luckily, not much, but
here are a few bullets which comes to my mind:
* RPM 4.12 introduces new %load function, which is used to load RPM
macros during RPM build. This allowed to drop my custom RPM macro [3].
On the other hand, you'll be able to build the Ruby only on F21+
(luckily, you should be able to build SRPM everywhere).
* The RubyGems filesystem was not explicit enough, so there might be
something accidentally packages. This is now more explicit, so we should
be safer.
* Ruby now ships with MiniTest and Test::Unit. The very good news is
that they are installed so far as a regular gems. This means that you
have to always specify them in your Gemfile, if you are using Bundler,
but this is generally step in good direction. I hope that upstream will
not change their mind :) Due to this change, we have new subpackages
rubygem-test-unit (and rubygem-power_assert, which is now Test::Unit's
dependency). No more %{_bindir}/testrb (but nobody is using it these
days anyway, right? ;)
* Some prevailing test failures were resolved, some others introduced,
but hopefully they'll get resolved prior stable release.
Generally, I'd say that not much has changed since 2.1, which is good news.
Please test the packaging if you can and let me know about any issues
you encountered.
Also, if you have any other suggestions about Ruby packaging in general,
what we could improve etc, this is probably good time to share. It seems
that OpenSUSE guys are improving their packaging, so you might want to
get some inspiration there [4, 5, 6] ;)
Vít
[1] http://pkgs.fedoraproject.org/cgit/ruby.git/log/?h=private-ruby-2.2
[2] http://koji.fedoraproject.org/koji/taskinfo?taskID=7578843
[3]
http://pkgs.fedoraproject.org/cgit/ruby.git/commit/?h=private-ruby-2.2&id=8…
[4] https://build.opensuse.org/package/show/home:darix:ruby/ruby-common
[5] https://build.opensuse.org/package/show/home:darix:ruby/ruby2.2
[6] https://github.com/openSUSE/gem2rpm/commits/master
Hi everybody,
You probably noticed, that there is ongoing build of all Python packages
in Copr [1] and today, I was approached by Miroslav Suchý, that he'd
like to do the same for rubygems. And this in turn triggered these
questions:
1) Would you be interested to create ruby-sig group in FAS? We could
make the group owner of some packages and in turn, the members of the
group could maintain the packages, without explicitly asking for some ACLs.
2) For the Copr rebuild of rubygems, there needs to be some FAS group
again. Python guys are asking for "pypi-builds-sig" group [2], hence
following their lead, I'd like to ask for "rubygems-builds-sig" group
(note that although I don't like the '-sig' suffix in this case, it is
mandated by the infrastructure ticket template).
So what are your thoughts?
Vít
[1]
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
[2] https://fedorahosted.org/fedora-infrastructure/ticket/5311
Hi everybody,
Time is running past and it is almost 6 months of development of Ruby
2.4. So I started to prepare some test build again. I am pushing all the
changes into private-ruby-2.4 branch of dist-git if you are interested
and here is the build of r55184:
http://koji.fedoraproject.org/koji/taskinfo?taskID=14278233
One notable change is that XMLRPC library was extracted into separate
gem, so rubygem-xmlrpc is now available as Ruby subpackage.
Please give it a try and let me know if anything goes wrong.
Vít
FYI:
http://frostyx.cz/posts/copr-rubygems
tl;dr version - you can submit name of module from rubygems.org and Copr will create rpm package for you.
I will be grateful for any feedback (either positive or negative).
--
Miroslav Suchy, RHCA
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
Hi all,
I am thinking about retiring therubyracer from Fedora. Please let me
explain.
It was always pain to have therubyracer in Fedora. First issue was to
get it working with system v8. We did that, but later, there were issues
with compatibility after v8 updates. Later, upstream split the v8 from
therubyrace into separate libv8 (!!!) rubygem, which made the situation
even worse, since I can't imagine to have rubyge-libv8-4.5.95.5 which
will use on the background different version of system v8. This kept us
with old version of therubyracer and old version of v8. Recently, after
introduction of gcc 6.x, there were some issues with compilation of v8
and hence therubyracer was not working. Now, Spot updated system v8
without asking into some recent version, which is not compatible with
our version of therubyracer [1] and moreover, therubyracer upstream
seems to be stalled (there is no activity since September 2015 as far as
I can say).
We introduced therubyracer in the times, when NodeJS had not been
available in Fedora yet, when now it seems NodeJS is in Fedora and does
not go away any time soon.
Upcoming version of RHSCL are going to use NodeJS in place of
therubyracer as well.
All this means, that we should update all rubygems that needs some JS
engine to depends on NodeJS instead of therubyracer and retire therubyracer.
Any thoughts?
Vít
[1] https://apps.fedoraproject.org/koschei/package/rubygem-therubyracer
-------- Přeposlaná zpráva --------
Předmět: Broken dependencies: rubygem-therubyracer
Datum: Tue, 10 May 2016 12:37:21 +0000 (UTC)
Od: buildsys(a)fedoraproject.org
Komu: rubygem-therubyracer-owner(a)fedoraproject.org
rubygem-therubyracer has broken dependencies in the rawhide tree:
On x86_64:
rubygem-therubyracer-0.11.0-13.fc24.x86_64 requires libv8.so.3()(64bit)
On i386:
rubygem-therubyracer-0.11.0-13.fc24.i686 requires libv8.so.3
On armhfp:
rubygem-therubyracer-0.11.0-13.fc24.armv7hl requires libv8.so.3
rubygem-therubyracer-0.11.0-13.fc24.armv7hl requires v8
Please resolve this as soon as possible.
Hi guys,
Anybody have any experience with some scripts for bash completion? Have
you tried any? Should we integrate any? Just a quick googling gave me
two results:
https://github.com/mernen/completion-rubyhttps://github.com/pdkl95/rubygems-completion
And there are probably others. I did not tried them yet. Have you? Do
you have other/better tips?
Thank you
Vit