You have probably noticed, that Ruby 2.3 was released during Christmas
so we can move forward with the change proposal  and get Ruby 2.3 for
F24. Actually, I already obtained build target for Ruby 2.3  and
build ruby-2.3 package and now its time for you to help :)
What does it means? This is the list of packages which very likely needs
to be rebuild:
$ dnf repoquery --disablerepo=* --enablerepo=rawhide
--enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel' |
sort | uniq
You can take the and just fire rebuild, but please, you should be using
f24-ruby build target, i.e. the build command should look like:
$ fedpkg build --target f24-ruby
If you forget to specify the target, you'll do build against Ruby 2.2,
which is not what you want.
If you don't make it soon enough, I'll very likely rebuild your package
sooner or later. I'll be using fermig  to do that as I did during
previous rebuilds. If you don't like me to touch you package for
whatever reason, please let me know (Mamoru, I suppose you are going to
rebuild your packages yourself, right?).
You can follow the progress at:
$ koji list-tagged f24-ruby
As always, any help/testing/feedback is welcome.
As has been discussed and described elsewhere, I've created a review
for doubling up the rubygem-minitest packages in EPEL by creating a
new rubygem-minitest5 package to target EPEL7. This will bring the 5.x
series of minitest to EPEL7 without colliding with the core EL
rubygem-minitest package which is still back on the 4.x series.
I've created a new review for this, if anyone wouldn't mind taking a
look at it. I'm going to have a small raft of other reviews coming in
the next week or two's time to finish building out the dependency tree
for my target package, but for the moment I could really use a review
swap on the rubygem-minitest(5) package as it is blocking very many of
the existing dependencies.
Greg Hellings wrote on 01/14/2016 01:30 PM:
> I'm working with a package (rubygem-minitest) which already exists in
> the core EL packages on the 4.x series. In order to enable a whole
> slew of new packages to be created in EPEL7, it will be necessary to
> package the 5.x series. However, since we don't want to mask the EL
> package it has been proposed and agreed to that the EPEL package be
> named rubygem-minitest5.
> In order to bring this about, would I need to submit a Review Request
> for a new package named rubygem-minitest5 and go through the normal
> new package process? Or is there an expedited way I can just get
> rubygem-minitest5 added to the tags for epel7 in koji?
If you would accept review swap, when you submit a review request
I can review it.