Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. .spec file without Requires: rubygems
- gems should require rubygems package
Note: Requires: rubygems missing in rubygem-colorize-doc
Requires: rubygems being missing is quite correct
From fedora core 21
* There should not be any rubygem Requires nor Provides listed, since those are autogenerated.
* There should not be Requires: ruby(release), unless you want to explicitly specify Ruby version compatibility. Automatically generated dependency on RubyGems (Requires: ruby(rubygems)) is enough.
The new test would actually be the reverse, emitting a warning if the explicit deps are there although they shouldn't.
What I don't understand if how to handle still long-to-eol f20. The same way?
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Steve: this is a simple fix if it's the same situation f20-f21-f22. But is it? Otherwise, could you outline the conditions?
> this is a simple fix if it's the same situation f20-f21-f22. But is it?
f21 and higher. f20 still needs explicit requires.
I have pushed two feature branches ruby21 (for f21) and ruby22 (f22). At a glance, this solves this problem.
In this branch, the ruby plugin is also a separate package, although still within the same srpm. A small step.
I need help from ruby-knowledged people to review and test this branch (anyone, they are identical from s ruby perspective).
I can confirm that the branches fixes this issue.
Fixed in https://git.fedorahosted.org/cgit/FedoraReview.git/commit/?h=devel&id=992cb0a25d9a71c