The rubygems subpackage built from this appears to break something important. Both vagrant and irb begin to fail once this version's rubygems package is installed:
$ dnf upgrade rubygems-3.2.33-152.fc35
$ irb
Ignoring json-2.3.0 because its extensions are not built. Try: gem pristine json --version 2.3.0
/usr/share/rubygems/rubygems/specification.rb:1406:in rescue in block in activate_dependencies': Could not find 'reline' (>= 0.1.5) among 70 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/home/badger/.gem/ruby:/usr/share/gems:/usr/local/share/gems' at: /usr/share/gems/specifications/irb-1.3.5.gemspec, executegem envfor more information
from /usr/share/rubygems/rubygems/specification.rb:1403:inblock in activate_dependencies'
from /usr/share/rubygems/rubygems/specification.rb:1392:in each'
from /usr/share/rubygems/rubygems/specification.rb:1392:inactivate_dependencies'
from /usr/share/rubygems/rubygems/specification.rb:1374:in activate'
from /usr/share/rubygems/rubygems.rb:299:inblock in activate_bin_path'
from /usr/share/rubygems/rubygems.rb:298:in synchronize'
from /usr/share/rubygems/rubygems.rb:298:inactivate_bin_path'
from /usr/bin/irb:23:in <main>'
/usr/share/rubygems/rubygems/dependency.rb:311:into_specs': Could not find 'reline' (>= 0.1.5) among 70 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/home/badger/.gem/ruby:/usr/share/gems:/usr/local/share/gems' , execute gem env for more information
from /usr/share/rubygems/rubygems/specification.rb:1404:in block in activate_dependencies'
from /usr/share/rubygems/rubygems/specification.rb:1392:ineach'
from /usr/share/rubygems/rubygems/specification.rb:1392:in activate_dependencies'
from /usr/share/rubygems/rubygems/specification.rb:1374:inactivate'
from /usr/share/rubygems/rubygems.rb:299:in block in activate_bin_path'
from /usr/share/rubygems/rubygems.rb:298:insynchronize'
from /usr/share/rubygems/rubygems.rb:298:in activate_bin_path'
from /usr/bin/irb:23:in<main>'
Downgrading just the rubygems subpackage to rubygems-3.2.22-151.fc35 appears to fix the issue.
At first glance, the symptoms look like this: https://github.com/rubygems/rubygems/issues/5156 but since you reported that and a fix was merged upstream last year, this might be a red herring.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update has been submitted for testing by vondruch.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
vondruch edited this update.
The rubygems subpackage built from this appears to break something important. Both vagrant and irb begin to fail once this version's rubygems package is installed:
$ dnf upgrade rubygems-3.2.33-152.fc35
$ irb
Ignoring json-2.3.0 because its extensions are not built. Try: gem pristine json --version 2.3.0 /usr/share/rubygems/rubygems/specification.rb:1406:in
rescue in block in activate_dependencies': Could not find 'reline' (>= 0.1.5) among 70 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/badger/.gem/ruby:/usr/share/gems:/usr/local/share/gems' at: /usr/share/gems/specifications/irb-1.3.5.gemspec, executegem envfor more information from /usr/share/rubygems/rubygems/specification.rb:1403:inblock in activate_dependencies' from /usr/share/rubygems/rubygems/specification.rb:1392:ineach' from /usr/share/rubygems/rubygems/specification.rb:1392:inactivate_dependencies' from /usr/share/rubygems/rubygems/specification.rb:1374:inactivate' from /usr/share/rubygems/rubygems.rb:299:inblock in activate_bin_path' from /usr/share/rubygems/rubygems.rb:298:insynchronize' from /usr/share/rubygems/rubygems.rb:298:inactivate_bin_path' from /usr/bin/irb:23:in<main>' /usr/share/rubygems/rubygems/dependency.rb:311:into_specs': Could not find 'reline' (>= 0.1.5) among 70 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/badger/.gem/ruby:/usr/share/gems:/usr/local/share/gems' , executegem envfor more information from /usr/share/rubygems/rubygems/specification.rb:1404:inblock in activate_dependencies' from /usr/share/rubygems/rubygems/specification.rb:1392:ineach' from /usr/share/rubygems/rubygems/specification.rb:1392:inactivate_dependencies' from /usr/share/rubygems/rubygems/specification.rb:1374:inactivate' from /usr/share/rubygems/rubygems.rb:299:inblock in activate_bin_path' from /usr/share/rubygems/rubygems.rb:298:insynchronize' from /usr/share/rubygems/rubygems.rb:298:inactivate_bin_path' from /usr/bin/irb:23:in<main>'Downgrading just the rubygems subpackage to rubygems-3.2.22-151.fc35 appears to fix the issue.
At first glance, the symptoms look like this: https://github.com/rubygems/rubygems/issues/5156 but since you reported that and a fix was merged upstream last year, this might be a red herring.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Och, good catch. Thx for testing. I'll take a look.
vondruch edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by vondruch.
It was indeed the BZ#2027099. The -153 includes patch to fix this. @toshio thx once again for discovering this.
This update has been pushed to testing.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.