ruby-sig September 2018

ruby-sig@lists.fedoraproject.org

2 participants
3 discussions

Ruby 2.2
by Vít Ondruch 25 Jan '22

25 Jan '22

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

4 18

Updated shoulda{,-matchers}
by Vít Ondruch 20 Sep '18

20 Sep '18

Hi, After years, I have finally managed to update shoulda and shoulda-matchers. Unfortunately, shoulda-matchers is heavily patched for Rails 5.2 support. Nevertheless, there are sill some deprecation warnings remaining. I have tested things which depends on Shoulda and they seems to be just fine, so hopefully nothing is really broken. Vít

1 0

Applying SSL patch to rpms/ruby f28
by Jun Aruga 17 Sep '18

17 Sep '18

Hi, I built fedora module ruby on all the supported platforms f28, f29 and f30. Because the way is recommended for Fedora modularity. [1] The result is f28 => failed, f29 => maybe random error, f30 => okay. Vit, can you apply the patch for SSL issue to rpms/ruby on f28? Thanks. ``` $ fedpkg module-build The builds 2186, 2187 and 2188 were submitted to the MBS ``` ## On f28 platform $ fedpkg module-build-info 2186 The build is failed on all the architectures. https://koji.fedoraproject.org/koji/taskinfo?taskID=29671575 https://kojipkgs.fedoraproject.org//work/tasks/1611/29671611/build.log 1) Failure: TestNetHTTPS#test_session_reuse [/builddir/build/BUILD/ruby-2.5.1/test/net/http/test_https.rb:78]: <true> expected but was <false>. ## On f29 platform $ fedpkg module-build-info 2187 The build is failed on only 390x. https://koji.fedoraproject.org/koji/taskinfo?taskID=29671605 https://kojipkgs.fedoraproject.org//work/tasks/1622/29671622/build.log 1) Failure: TestThread#test_thread_interrupt_for_killed_thread [/builddir/build/BUILD/ruby-2.5.1/test/ruby/test_thread.rb:1256]: [Bug #8996] pid 31834 killed by SIGKILL (signal 9) ## On f30 platform $ fedpkg module-build-info 2188 The build is succeeded. By the way, right now it is not clear which build_id's build connects to the platform. [2] [1] See email "[modularity] Recommended platform: [] and version 2 format at Fedora devel mailing list [2] https://pagure.io/fm-orchestrator/issue/1020 -- Jun Aruga jaruga(a)redhat.com

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

ruby-sig September 2018