ruby-sig April 2022

ruby-sig@lists.fedoraproject.org

2 participants
3 discussions

Ruby 2.2
by Vít Ondruch 22 Sep '23

22 Sep '23

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 19

Latest RSpec issues?
by Vít Ondruch 18 Jan '23

18 Jan '23

Dear Mamoru, Could you please check the following two packages which recently started to fail? https://koschei.fedoraproject.org/package/rubygem-webmock?collection=f36 https://koschei.fedoraproject.org/package/rubygem-websocket-extensions?coll… I suspect that this is related to the RSpec update, but the errors are quite strange on the first look: ~~~ 1) WebMock::RequestSignature initialization assigns normalized headers Failure/Error: @headers = WebMock::Util::Headers.normalize_headers(headers) #<WebMock::Util::Headers (class)> received :normalize_headers with unexpected arguments expected: ({"A"=>"a"}) got: ({"A"=>"a"}) # ./lib/webmock/request_signature.rb:25:in `headers=' # ./lib/webmock/request_signature.rb:49:in `assign_options' # ./lib/webmock/request_signature.rb:11:in `initialize' # ./spec/unit/request_signature_spec.rb:23:in `new' # ./spec/unit/request_signature_spec.rb:23:in `block (3 levels) in <top (required)>' # ./lib/webmock/rspec.rb:37:in `block (2 levels) in <top (required)>' ~~~ Thx a lot Vít P.S. Sorry for not being more helpful, I have to spent some time with CentOS Stream 9 to get Ruby into shape there, especially the problematic SystemTap support [1]. [1] https://bugs.ruby-lang.org/issues/18257

2 23

rawhide hits rpm-4.18.0 alpha - affecting gem based packaging
by Mamoru TASAKA 29 Apr '22

29 Apr '22

Hello, all: Now I was going to update rubygem-kramdown, resulting in build failure. Then I've noticed that on rawhide, "rpm" was updated to rpm 4.18.0 alpha . This seems to affect current gem based packaing of ours. Mainly: "%setup -q" for foo-%version.gem places foo-%version.gemspec on %{_sourcedir} with rpm 4.18.0 alpha . Previously (with rpm 4.17.x), gemspec file was placed on %{_builddir}. Maybe we may have to update packaging guideline, or modify gem2rpm. Regards, Mamoru

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

ruby-sig April 2022