Bug 1730031
Summary: | Ruby module upgrade UX is not the best | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Honza Horak <hhorak> |
Component: | ruby-2.6-module | Assignee: | Jun Aruga <jaruga> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 8.1 | CC: | jaruga |
Target Milestone: | rc | ||
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-02-18 07:30:58 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
Honza Horak
2019-07-15 15:57:03 UTC
There are 2 document to think about the best way to switch modules/ruby's stream to upgrade Ruby 2.5 to 2.6. 1. https://docs.fedoraproject.org/en-US/modularity/using-modules/#_updating_the_system 2. https://developers.redhat.com/blog/2019/05/16/modular-perl-in-red-hat-enterprise-linux-8/ I am testing to think the best way. But right now I have some comments. For document 1, `dnf update` is written on the page. But `dnf update` is deprecated according to `man dnf`. `dnf upgrade` is better. When running `yum --help | less` on ubi8 container. `yum update` is not on the page. So, when we use `yum update`, `yum upgrade` is better. For document 2, `# yum --allowerasing distrosync` is used as a tutorial of module. * `yum --allowerasing upgrade <RPM files>` might give you better experience than `yum upgrade <RPM files>`. * `yum --allowerasing downgrade <RPM files>` might work when downgrading Ruby such as switch modules/ruby:2.6 to 2.5. * `yum --allowerasing distrosync` might be better than `yum distrosync`. I think below is the better steps to upgrade Ruby rather than "yum update" and "yum distro-sync" if the RPM is included in the existing profile of modules/ruby:2.6. Maybe we have to create the profile "all" that means all the RPMs in modules/ruby:2.6, other profile that means all the binary RPM of rpms/ruby SRPM for the best user experience. Right now there is only one profile "default" that is default profile that means ruby, ruby-devel, ruby-libs RPMs. Below "yum module install ruby:2.6" enables ruby:2.6 too when there is no enabled ruby stream. ``` 1. # yum install ruby\* 2. # yum module reset ruby 3. # yum module install ruby:2.6 ``` If the upgraded RPM is not included in the profile, I think below steps are currently best. ``` 1. # yum install ruby\* 2. # yum module reset ruby 3. # yum module enable ruby:2.6 4. # yum --allowerasing distro-sync <RPMs> ``` I also commented below about Fedora. https://pagure.io/fm-orchestrator/issue/1342#comment-582911 I have not tested ruby:2.6 on RHEL 8.1 yet. This is just my predictions based on the tests on Fedora. Yesterday we released the documentation about the use case to switch module stream (upgrade module stream). Now remaining task for this ticket is to add Ruby specific notes with examples to new chapter. https://projects.engineering.redhat.com/browse/RHELPLAN-17911 https://bugzilla.redhat.com/show_bug.cgi?id=1672575#c33 |