Dne 14.12.2017 v 19:03 Vít Ondruch napsal(a):
Dne 14.12.2017 v 18:41 Vít Ondruch napsal(a):
Dne 14.12.2017 v 18:23 Jun Aruga napsal(a):
OK thanks for the info.
Comparing the result of "gem list" command between upstream and our Fedora package, I found the difference. That can be confusing people.
Some of the gem are not shown in the result such as cmath for Fedora package ruby.
When running below command on mock, we can load cmath that is not in "gem list" on mock, maybe those are only shown as a result of "gem list".
irb(main):003:0> require 'cmath' => trueIs it possible to add those gems in the result as a compatibility for upstream Ruby? Hidden gems such as cmath are confusing users.
Interesting. That is definitely unintentional. Will take a look into it.
This appears to be related to the default location of where the gems are installed. Upstream Ruby installs the gems into their directory, we install the gems into home directory. And therefore RubyGems on Fedora are trying to load the specifications for the default gems from the home directory "/builddir/.gem/ruby/specifications/default" (testing in mock). So far, we never had the default gem specifications, so this was not issue.
Here is updated build, which should fix the issues:
https://koji.fedoraproject.org/koji/taskinfo?taskID=23793602
The patch used to fix this in attachment. I'd love some feedback prior I push this into git. Mainly, I'd like you to test:
1) If "gem install" as a regular user still works the same. 2) If "gem install" as root still works the same. 3) If the RPM packages in Fedora (probably just noarch) still installs and runs just fine. 4) If rubygem- RPM packages build using this ruby are still build and installed correctly. 5) Any additional scenario you can think of ...
Thx for testing.
Vít