Bug 2119964
| Summary: | rubygem-irb does not pull rubygem-rdoc as dependency | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alex <aleksq> |
| Component: | ruby | Assignee: | Jun Aruga <jaruga> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 36 | CC: | jaruga, jprokop, lutter, mastahnke, mo, mtasaka, pvalena, ruby-packagers-sig, s, strzibny, vanmeeuwen+fedora, vondruch |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ruby-3.1.2-168.fc38 ruby-3.1.2-169.fc37 ruby-3.1.2-169.fc36 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-09-01 20:27:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Alex
2022-08-20 11:02:26 UTC
Good catch. This dependency seems to be introduced by [1]. But it also appears that it should have been optional, but it is not. I have send PR with proposed fix upstream. Lets see what is their response. [1]: https://github.com/ruby/irb/commit/026700499dfd640b2072d7bf0370247a98d5ac40 (In reply to Vít Ondruch from comment #1) > Lets see what is their response. I should probably elaborate that in current state, there would need to be `Require: rubygem(rdoc)` added for rubygem-irb. But if the patch is accepted upstream, it could be just `Recommends: rubygem(rdoc)`. > But if the patch is accepted upstream, it could be just `Recommends: rubygem(rdoc)`. As the patch was accepted, and merged at <https://github.com/ruby/irb/pull/393 >, I think the `Recommends: rubygem(rdoc)` is the best solution on Fedora ruby. I am working on it. I sent the PR. https://src.fedoraproject.org/rpms/ruby/pull-request/130 FEDORA-2022-7b269a84e6 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7b269a84e6 FEDORA-2022-7b269a84e6 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-53358fd5c8 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-53358fd5c8 FEDORA-2022-53358fd5c8 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-53358fd5c8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-53358fd5c8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-53358fd5c8 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-9f08ba013b has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9f08ba013b FEDORA-2022-9f08ba013b has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-9f08ba013b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-9f08ba013b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-9f08ba013b has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |