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
Hi everybody,
I started early this time and therefore, there is already PR with
changes for upcoming Ruby version:
https://src.fedoraproject.org/rpms/ruby/pull-request/55
and the build should be available (if succeeds) here:
https://koji.fedoraproject.org/koji/taskinfo?taskID=41848663
So far, there are changes in bundled gems. The RSS and REXML gems are
not bundled gems, therefore I extracted them into separate subpackages,
while Net::Telnet and XMLRPC were dropped from Ruby and therefore
ruby-libs now obsoletes these two packages.
As always, any feedback is welcome.
Vít
Hi all,
Ruby upstream is implementing more and more stuff directly in Ruby. We
already had issues, that build of Ruby required Ruby when we did some
modifications [1]. In subsequent ticket, one of Ruby committers said [2]:
> ... snip ...
> BASERUBY is already a build requirement
> ... snip ...
> I would like to implement more of Ruby using Ruby, so miniruby may
depend on prelude one day.
With recent changes, such as [3], I am afraid that the day has come.
Previously, if you wanted to patch lets say "gem_prelude.rb", it was
enough to patch it. But now you *need* Ruby to process it into
miniprelude.c. There are possibly 4 ways out of this.
1) Build Ruby in two stages. a) build (mini)ruby, apply patches b) build
Ruby using the previously built (mini)ruby.
2) Use previous version of Ruby available in Fedora to bootstrap Ruby.
But this does not work ATM, at least when RubyGems are installed. And
upstream is doing what they can to make RubyGems inseparable [4].
3) Prepare patches locally and apply the required changes also to the
pregenerated files. But the problem here is, that the patches might
unpredictably fail between updates. I don't think that they keep any
API/ABI promises for the tools used to generate those files.
4) Don't use the upstream tarball, but generate it from sources with
patches integrated.
I think we should probably start to take look at 1), specifically into
the *miniruby* variant if that is enough. If that is done, the 2) could
optionally blend in. And in the mean time use 3) because otherwise I
really don't know how to integrate the ABRT hook support. I don't like
4) at all, unless we have some Fedora standardized way of doing so.
On the positive side, 1(2) would allow us to stay better in line with
"Pregenerated code" guidelines [5], because there is already quite a lot
of pre-generated code shipped in Ruby release tarball.
Thoughts?
Vít
[1]
https://src.fedoraproject.org/rpms/ruby/c/c0513dfb8c81a228619c6142195c5117a…
[2] https://bugs.ruby-lang.org/issues/15306#note-1
[3] https://github.com/ruby/ruby/pull/2655
[4] https://bugs.ruby-lang.org/issues/16431
[5]
https://docs.fedoraproject.org/en-US/packaging-guidelines/what-can-be-packa…
I observed the FTBFS on rpm/ruby rawhide.
You can see Koschei.
https://koschei.fedoraproject.org/package/ruby
Do you know what causes the error? Is it a temporary issue?
If you like, I open the bugzilla ticket for that.
https://kojipkgs.fedoraproject.org/work/tasks/3309/45363309/build.log
```
1) Failure:
Psych::TestNil#test_array_nil
[/builddir/build/BUILD/ruby-2.7.1/test/psych/test_nil.rb:14]:
--- expected
+++ actual
@@ -1,3 +1,3 @@
"---
--
+-
"
2) Failure:
Psych::TestNil#test_nil
[/builddir/build/BUILD/ruby-2.7.1/test/psych/test_nil.rb:8]:
Expected /--- \n(?:\.\.\.\n)?/ to match "---\n".
3) Error:
Psych_Unit_Tests#test_spec_domain_prefix:
Psych::SyntaxError: (<unknown>): did not find expected whitespace or
line break while scanning a tag at line 2 column 10
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse_stream'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:390:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:277:in `load'
/builddir/build/BUILD/ruby-2.7.1/test/psych/helper.rb:66:in
`assert_parse_only'
/builddir/build/BUILD/ruby-2.7.1/test/psych/test_yaml.rb:622:in
`test_spec_domain_prefix'
4) Error:
Psych_Unit_Tests#test_spec_application_family:
Psych::SyntaxError: (<unknown>): did not find expected whitespace or
line break while scanning a tag at line 1 column 3
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse_stream'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:390:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:277:in `load'
/builddir/build/BUILD/ruby-2.7.1/test/psych/helper.rb:66:in
`assert_parse_only'
/builddir/build/BUILD/ruby-2.7.1/test/psych/test_yaml.rb:750:in
`test_spec_application_family'
5) Error:
Psych_Unit_Tests#test_spec_float_explicit:
Psych::SyntaxError: (<unknown>): did not find expected whitespace or
line break while scanning a tag at line 5 column 3
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse_stream'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:390:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:277:in `load'
/builddir/build/BUILD/ruby-2.7.1/test/psych/helper.rb:66:in
`assert_parse_only'
/builddir/build/BUILD/ruby-2.7.1/test/psych/test_yaml.rb:768:in
`test_spec_float_explicit'
6) Error:
Psych_Unit_Tests#test_spec_explicit_families:
Psych::SyntaxError: (<unknown>): did not find expected whitespace or
line break while scanning a tag at line 8 column 6
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse_stream'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:390:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:277:in `load'
/builddir/build/BUILD/ruby-2.7.1/test/psych/helper.rb:66:in
`assert_parse_only'
/builddir/build/BUILD/ruby-2.7.1/test/psych/test_yaml.rb:711:in
`test_spec_explicit_families'
7) Error:
TestPsych#test_domain_types:
Psych::SyntaxError: (<unknown>): did not find expected whitespace or
line break while scanning a tag at line 1 column 5
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse_stream'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:390:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:277:in `load'
/builddir/build/BUILD/ruby-2.7.1/test/psych/test_psych.rb:185:in
`test_domain_types'
8) Error:
TestPsych#test_callbacks:
Psych::SyntaxError: (<unknown>): did not find expected whitespace or
line break while scanning a tag at line 1 column 3
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:456:in `parse_stream'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:390:in `parse'
/builddir/build/BUILD/ruby-2.7.1/.ext/common/psych.rb:277:in `load'
/builddir/build/BUILD/ruby-2.7.1/test/psych/test_psych.rb:300:in
`test_callbacks'
Finished tests in 978.698829s, 21.4785 tests/s, 2781.3173 assertions/s.
21021 tests, 2722072 assertions, 2 failures, 6 errors, 62 skips
```
Cheers,
Jun
--
Jun | He - His - Him
