rubygem-openssl is going to be bundled in Ruby
by Vít Ondruch
Hi,
Following the bundling of Racc [1] and did_you_mean [2], I am forced to
bundle also OpenSSL. This is due to the StdLib symlinks together with
`require_relative` [3] causing double loading issues, e.g.:
~~~
$ ruby --disable-gems -e 'require "openssl"; require "openssl/digest"'
/usr/share/ruby/openssl/digest.rb:45: warning: already initialized
constant OpenSSL::Digest::MD4
/usr/share/gems/gems/openssl-2.2.0/lib/openssl/digest.rb:45:
warning: previous definition of MD4 was here
/usr/share/ruby/openssl/digest.rb:45: warning: already initialized
constant OpenSSL::Digest::MD5
/usr/share/gems/gems/openssl-2.2.0/lib/openssl/digest.rb:45:
warning: previous definition of MD5 was here
/usr/share/ruby/openssl/digest.rb:45: warning: already initialized
constant OpenSSL::Digest::RIPEMD160
/usr/share/gems/gems/openssl-2.2.0/lib/openssl/digest.rb:45:
warning: previous definition of RIPEMD160 was here
/usr/share/ruby/openssl/digest.rb:45: warning: already initialized
constant OpenSSL::Digest::SHA1
/usr/share/gems/gems/openssl-2.2.0/lib/openssl/digest.rb:45:
warning: previous definition of SHA1 was here
/usr/share/ruby/openssl/digest.rb:45: warning: already initialized
constant OpenSSL::Digest::SHA224
/usr/share/gems/gems/openssl-2.2.0/lib/openssl/digest.rb:45:
warning: previous definition of SHA224 was here
/usr/share/ruby/openssl/digest.rb:45: warning: already initialized
constant OpenSSL::Digest::SHA256
/usr/share/gems/gems/openssl-2.2.0/lib/openssl/digest.rb:45:
warning: previous definition of SHA256 was here
/usr/share/ruby/openssl/digest.rb:45: warning: already initialized
constant OpenSSL::Digest::SHA384
/usr/share/gems/gems/openssl-2.2.0/lib/openssl/digest.rb:45:
warning: previous definition of SHA384 was here
/usr/share/ruby/openssl/digest.rb:45: warning: already initialized
constant OpenSSL::Digest::SHA512
/usr/share/gems/gems/openssl-2.2.0/lib/openssl/digest.rb:45:
warning: previous definition of SHA512 was here
/usr/share/ruby/openssl/digest.rb:52:in `<class:Digest>':
superclass mismatch for class Digest (TypeError)
from /usr/share/ruby/openssl/digest.rb:16:in `<module:OpenSSL>'
from /usr/share/ruby/openssl/digest.rb:15:in `<top (required)>'
from -e:1:in `require'
from -e:1:in `<main>'
~~~
This is the reason why rubygem-net-ssh is broken ATM [4]. Not sure if
upstream is really able to resolve the double loading issue [5]. While I
could revert the [3] to resolve the original state, we would need to
maintain this patch for the foreseeable future. Therefore it is probably
better to keep openssl bundled. This at least will provide experience
closer to upstream.
Vít
[1]
https://src.fedoraproject.org/rpms/ruby/c/baf046a6a4d17fa309c9d20fa3db949...
[2]
https://src.fedoraproject.org/rpms/ruby/c/ca69f778a9169c7ff172d2cc9c9d31c...
[3]
https://github.com/ruby/openssl/commit/74e03b588f58bcac007d7145c3bb6c4754...
[4] https://koschei.fedoraproject.org/package/rubygem-net-ssh
[5] https://bugs.ruby-lang.org/issues/16978#note-11
6 months
Ruby 3.0 - Mass rebuild
by Vít Ondruch
Hi everybody,
So here we go. I have asked for side tag for Ruby 3.0 rebuild:
~~~
$ fedpkg request-side-tag
Side tag 'f34-build-side-35577' (id 35577) created.
Use 'fedpkg build --target=f34-build-side-35577' to use it.
Use 'koji wait-repo f34-build-side-35577' to wait for the build repo to
be generated.
~~~
and Ruby 3.0 is already built there as you can see at:
https://koji.fedoraproject.org/koji/builds?inherited=0&tagID=35577&order=...
or using:
~~~
$ koji list-tagged f34-build-side-35577
~~~
Now this is a list of packages, which very likely needs rebuild:
~~~
$ dnf repoquery --disablerepo=* --enablerepo=rawhide
--enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel' |
sort | uniq
~~~
You can take the package and just fire rebuild, but please ensure that
you are using f34-build-side-35577 build target, i.e. the build command
should look like:
~~~
$ fedpkg build --target f34-build-side-35577
~~~
Please be careful, because if you, by a chance, omit the
f34-build-side-35577 target, you'll be building against Ruby 2.7 which
is not what you want.
If you won't do it by yourself, I'll be rebuilding all packages after I
am finished with my packages. I'll be using fermig [1] to help me with
that. If you don't want me to touch your packages for whatever reason,
please let me know.
As always, any help/testing/feedback is welcome.
Vít
[1] https://github.com/fedora-ruby/fermig
6 months, 1 week
Ruby 3.0 change proposal
by Vít Ondruch
Hi Rubyists,
The release of Ruby 3.0 is coming close and to be ready for rebuild
after Christmas, I have submitted the Ruby 3.0 change proposal [1]. It
is already in `ChangeReadyForWrangler` state, since I don't expect any
controversy. But anyway, please review and let me know if you have any
concerns.
Vít
[1] https://fedoraproject.org/wiki/Changes/Ruby_3.0
6 months, 3 weeks
