ruby-sig January 2016

ruby-sig@lists.fedoraproject.org

5 participants
5 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

BASH completion for Ruby
by Vít Ondruch 25 May '16

25 May '16

Hi guys, Anybody have any experience with some scripts for bash completion? Have you tried any? Should we integrate any? Just a quick googling gave me two results: https://github.com/mernen/completion-ruby https://github.com/pdkl95/rubygems-completion And there are probably others. I did not tried them yet. Have you? Do you have other/better tips? Thank you Vit

2 3

Ruby 2.3 - Mass rebuild
by Vít Ondruch 02 Mar '16

02 Mar '16

Hi all, You have probably noticed, that Ruby 2.3 was released during Christmas so we can move forward with the change proposal [1] and get Ruby 2.3 for F24. Actually, I already obtained build target for Ruby 2.3 [2] 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 [4] 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: http://koji.fedoraproject.org/koji/builds?inherited=0&tagID=331&order=-buil… or using: $ koji list-tagged f24-ruby As always, any help/testing/feedback is welcome. Vít [1] https://fedoraproject.org/wiki/Changes/Ruby_2.3 [2] https://fedorahosted.org/rel-eng/ticket/6324 [3] https://koji.fedoraproject.org/koji/buildinfo?buildID=709430 [4] https://github.com/fedora-ruby/fermig

4 16

Review Swap
by Greg Hellings 21 Jan '16

21 Jan '16

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. https://bugzilla.redhat.com/show_bug.cgi?id=1298622 --Greg

1 0

Re: Package name for EPEL7 branch
by Mamoru TASAKA 14 Jan '16

14 Jan '16

Hello: 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? > > --Greg If you would accept review swap, when you submit a review request I can review it. Regards, Mamoru

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

ruby-sig January 2016