Hello, again:
Vít Ondruch wrote on 2023/09/18 17:24:
Dne 17. 09. 23 v 15:42 Mamoru TASAKA napsal(a):
Okay, so with my initial builds for rubygem-XXXX packages, among 456 packages,
50 packages failed to build (1 just fixed one of them, so currently 49).
https://copr.fedorainfracloud.org/coprs/mtasaka/rubygem-newruby-test-3-2/packages/
Some types of errors (I noticed) which is affecting several packages are:
* minitest 5.19 side change: MiniTest class support deprecated:
example:
test/test_async.rb:28:in `<main>': uninitialized constant MiniTest (NameError)
https://github.com/minitest/minitest/commit/a2c6c18570f6f0a1bf6af70fe3b6d9599a13fdd6
While I am aware of this issue in rubygem-async_sinatra, I have let this
package deliberately unfixed, because I don't think it is maintained. So either
their maintainer will fix it or it will be later automatically removed from
Fedora. I don't really intend to prolong life of such packages.
* ruby logger change.
example:
NoMethodError: undefined method `[]' for nil
https://github.com/ruby/logger/pull/85
-> affects like https://github.com/resque/resque/issues/1856
* Regexp.new now rejects 3rd argument:
example:
wrong number of arguments (given 3, expected 1..2)
https://github.com/ruby/ruby/pull/7039
* mocha being updated from 1.15.0 to 2.1 - perhaps some adjustment is needed
example:
`require': cannot load such file -- mocha/setup (LoadError)
Assuming this is about rubygem-rack-cors, this is similar case to the
rubygem-async_sinatra. I have submitted fix upstream:
https://github.com/cyu/rack-cors/pull/266
and put @valtri on CC. So he should be aware.
* Some packages expect that there are no warnings, but now with ruby3.3
when trying to load default gems which are going to be gemified,
warnings are generated like:
$ ruby -e "require 'csv'"
-e:1: warning: csv which will be not part of the default gems since Ruby 3.4.0
I think that this was reported here:
https://bugs.ruby-lang.org/issues/19885
Thank you for info. This is actually what I want to track.
https://github.com/ruby/ruby/pull/8126 , and the above warnings cause
some tests fail.
So this may mean that we have to package those default gems into separated
rubygem-XXX srpm , at least before ruby 3.4 lands.
* And, currently some tests segfault.
* (Just note that there are some other reasons which cause test failure:
I have not investigated them yet.)
Some topics:
* rubygem-nifti sees test failure on s390x, this is perhaps big endian issue.
Interesting. nifti failed during mass rebuild, but later it was update by its
maintainer. So it would probably deserve bug report and maybe some
`ExcludeArch`?
Okay, I will check rubygem-nifti commit on Fedora dist-git (and perhaps I will
probably file bugzilla ticket for rubygem-nifti).
(Well, rubygem-nifti is actually noarch, but I often wonder if we should always
try to build packages for all arches even if the srpm itself is noarch:
sometimes I see endian issue like this, for example.)
* rubygem-byebug fails to build (on test suite), however it seems this needs
the undestanding of ruby internal change, and seems very difficult for me....
Is there any future in byebug? Wasn't it obsoleted/replaced by the `debug` gem
which is shipped with Ruby?
Thank you for info.
Well, it seems that actually my usage of byebug gem can be enough satisfied
with debug gem.
So now I incline to orphan byebug rather than spending time to fix byebug test
failure...
but what I've found is that power_assert testsuite depends on byebug:
https://github.com/ruby/power_assert/blob/297fa68908c45c4ca6c41e0940ebcc069744d580/power_assert.gemspec#L26
Before I orphan byebug, first I will try to contact with power_assert upstream.
I may post some detailed results (if I have time), however as I wrote above
the results can be shown on:
https://copr.fedorainfracloud.org/coprs/mtasaka/rubygem-newruby-test-3-2/packages/
Thank you for the initial tests. I'll look into your findings later in more
detail. These were just quick notes mostly just from my memory :)
Vít
Mamoru
_______________________________________________
ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org
To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
