You probably noticed, that there is ongoing build of all Python packages
in Copr  and today, I was approached by Miroslav Suchý, that he'd
like to do the same for rubygems. And this in turn triggered these
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 , 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?
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:
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.
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
I am thinking about retiring therubyracer from Fedora. Please let me
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-18.104.22.168 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  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.
-------- Přeposlaná zpráva --------
Předmět: Broken dependencies: rubygem-therubyracer
Datum: Tue, 10 May 2016 12:37:21 +0000 (UTC)
rubygem-therubyracer has broken dependencies in the rawhide tree:
rubygem-therubyracer-0.11.0-13.fc24.x86_64 requires libv8.so.3()(64bit)
rubygem-therubyracer-0.11.0-13.fc24.i686 requires libv8.so.3
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.