Description of problem: Several gem specs under /usr/share/gems/specifications are referencing the directory /usr/share/ruby/lib which doesn't exist. Version-Release number of selected component (if applicable): - ruby-default-gems-3.1.2-164.fc36.noarch - rubygems-3.3.7-164.fc36.noarch Steps to Reproduce: 1. $ grep -r -l 's.files = \[\"lib/' /usr/share/gems/specifications /usr/share/gems/specifications/default/benchmark-0.2.0.gemspec /usr/share/gems/specifications/default/delegate-0.2.0.gemspec /usr/share/gems/specifications/default/did_you_mean-1.6.1.gemspec /usr/share/gems/specifications/default/drb-2.1.0.gemspec /usr/share/gems/specifications/default/error_highlight-0.3.0.gemspec /usr/share/gems/specifications/default/forwardable-1.3.2.gemspec /usr/share/gems/specifications/default/getoptlong-0.1.1.gemspec /usr/share/gems/specifications/default/logger-1.5.0.gemspec /usr/share/gems/specifications/default/net-http-0.2.0.gemspec /usr/share/gems/specifications/default/net-protocol-0.1.2.gemspec /usr/share/gems/specifications/default/observer-0.1.1.gemspec /usr/share/gems/specifications/default/open3-0.1.1.gemspec /usr/share/gems/specifications/default/optparse-0.2.0.gemspec /usr/share/gems/specifications/default/ostruct-0.5.2.gemspec /usr/share/gems/specifications/default/pstore-0.1.1.gemspec /usr/share/gems/specifications/default/reline-0.3.0.gemspec /usr/share/gems/specifications/default/rinda-0.1.1.gemspec /usr/share/gems/specifications/default/set-1.0.2.gemspec /usr/share/gems/specifications/default/singleton-0.1.1.gemspec /usr/share/gems/specifications/default/timeout-0.2.0.gemspec /usr/share/gems/specifications/default/uri-0.11.0.gemspec /usr/share/gems/specifications/default/weakref-0.1.1.gemspec /usr/share/gems/specifications/default/yaml-0.2.0.gemspec /usr/share/gems/specifications/bundler-2.3.7.gemspec Expected results: $ rpm -ql ruby-libs | grep benchmark.rb /usr/share/ruby/benchmark.rb Actual results: $ gem contents benchmark /usr/share/ruby/lib/benchmark.rb /usr/share/ruby/lib/benchmark/version.rb Additional info: Bug not present in Fedora 35 - ruby-default-gems-3.0.2-150.module_f35+12410+172cbfa4.noarch - rubygems-3.2.22-150.module_f35+12410+172cbfa4.noarch
Thx for reporting. Good catch! BTW, could you please share what is your use case. I wonder how you actually hit this?
Hi Vit, I'm currently in the process of currently studying the feasibility of namespacing ruby RPMs so we at Amazon can support both ruby 3.1 and 3.2 runtimes being installed concurrently on our Fedora-based 2022 distro. I was in middle of dealing with conflicting/overlapping gemspec files in my two sets of ruby test packages when I came across this inconsistency.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.