It is about the time to start with mass rebuild of packages for Ruby
2.6, since the change proposal was already accepted in advance. Finally,
after more then week of waiting, I was also able to obtain side-tag ,
so we won't disrupt Rawhide a lot. The Ruby 2.6 is already build there
as well as a few other packages. Now it is time for your help.
This is the list of packages, which very likely needs rebuild:
$ dnf repoquery --disablerepo=* --enablerepo=rawhide
--enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel' |
sort | uniq
You can take the package and just fire rebuild, but please ensure that
you are using f30-ruby build target , i.e. the build command should
$ fedpkg build --target f30-ruby
Please be careful, because if you, by a chance, omit the f30-ruby
target, you'll be building against Ruby 2.5 which is not what you want.
If you won't do it by yourself, I'll be rebuilding all packages after I
am finished with my packages. I'll be using fermig  to help mi with
that. If you don't want me to touch your packages for whatever reason,
please let me know.
Also, Pavel Valena built some packages against Ruby 2.6 in his Copr
repository , so please check if other packages needs some adjustments.
You can follow the progress at:
$ koji list-tagged f30-ruby
As always, any help/testing/feedback is welcome.
I am using:
- Fedora 29 x86_64
but when I run as user phil:
rails new pam
Using rake 12.3.2
Fetching concurrent-ruby 1.1.4
Shouldn't I be able to use all the gems I need from installed RPMs?
PO Box 896
Cowra NSW 2794
I just created PR with .spec file updated to build Ruby 2.6.0.preview3:
It is very much WIP, but it builds at least. I have even not tried to
install or run the package. Pagure is so nice, that it should provide
the recent scratch builds via simple-koji-ci, so I am not going to link
So far, there are 3 things missing/ignored:
1. Bundler is completely removed. I am afraid the situation has not
improved much since last year. E.g. Molinillo, the dependency solver is
included in Ruby twice, once via RubyGems, second time via Bundler, etc.
2. IRB was gemified, therefore it should be moved into rubygem-
subpackage and the original ruby-irb should be obsoleted.
3. I am still undecided how to go forward with JIT. It requires compiler
and it has to be explicitly required, therefore we should do nothing
IMO. Later, we should probably Suggest or even Require the compiler? Not
And as always, please let me know any feedback, either here or in PR.