Ruby 2.2
by Vít Ondruch
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...
[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
4 months
Self Introduction Axel Delahaye
by Delahaye Axel
Hello everyone,
I'm a computer science enginner from France.
I'm in fond of computer science since my childhood.
I discover Linux and Opensource in 2008 when I join the University Institute of Technology of Lille.
Since this day, I try a large number of Linux distributions and I very like the opensource philosophy.
I now use Fedora as personal use distribution.
Anyway, today I work in Software engineering company and we use RedHat and CentOS.
For our needs, we also use the epel repository and we think about contribute to this repo.
First we would like to use the rubygem-bundler package from epel6 but at this time it is in testing because of the rubygem-thor dependency error
I test rebuild rubygem-thor from fedora21 with epel-6-x86_64 mock profile and it works.
I'm in touch with Mo Morsi who is maintainer of rubygem-thor and the builder of rubygem-bundler in epel-testing 6.
So I'll send request for commit rights to the http://pkgs.fedoraproject.org/cgit/rubygem-thor.git/ and push to the el6 branch.
I hope you now know more about me and I hope I can help you to purpose more and maintained packages
Axel Delahaye
________________________________
Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis.
This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
6 years, 10 months
Introduction and Rack update to 4.2.3
by Sourav Moitra
Hello everyone,
I am Student of Bachelor of Engineering, stream Information Technology at
University Institute of Technology, Burdwan. I am a ruby enthusiast. I have
done some projects on Rails with amahi.org.
I am trying to update rack to latest 1.6.4 so that rails could be updated
to latest 4.2.3 in EPEL.
Regards
Sourav Moitra
6 years, 10 months
dnf, jruby, and mock
by Ken Dreyer
mock with dnf pulls in jruby to satisfy "Requires: ruby(release)" on
Rawhide. I've found that several (all?) of my local Rawhide mock
builds fail due to jruby issues. This makes maintaining gem packages
pretty tedious, and breaks fedora-review runs, etc.
Can we remove the "Provides: ruby(release)" from Fedora's jruby in
F23? That seems like it would be easier than switching all rubygem
packages that FTBFS to "Require: ruby-mri", and besides, it often it
is not my noarch gem itself that breaks with jruby, but some other
build dependency somewhere in the chain. I think it makes sense to
just remove the virtual provide from jruby until jruby is more stable.
- Ken
6 years, 10 months
Action needed - mass rebuild FTBFS
by Vít Ondruch
Hi all,
There is plenty of packages which failed to build during F23 mass rebuild:
http://alt.fedoraproject.org/pub/alt/mass-rebuild/f23-failures.html
If I counted correctly, there is currently 93 ruby packages failing out
of 567 failing packages in total. IOW, it is more then 16 % currently
failing packages. That is a lot.
So is there any volunteer who would help fixing this bugs? The typical
issue is due to changes in testing frameworks in recent Ruby, so these
are typically easyfixes. In case you have updated SRPM, please just send
me a link and I can do official build for Fedora.
Thanks
Vít
6 years, 10 months
