-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ELevate Wiki Docs Updates to Include CRB Dependency Information #478
base: master
Are you sure you want to change the base?
ELevate Wiki Docs Updates to Include CRB Dependency Information #478
Conversation
Thank you! |
@sboldyreva you're the elevate docs maven for sure. I'd love your eyes on this! Especially because I think #484 might change some of this, too. |
The cause of this error is that during the upgrade process, ELevate uses a multitude of repositories to migrate and upgrade the system. Among them is the usage of the CRB repository. Importantly, if the CRB repository was not enabled on the system prior to using ELevate, it will remain disabled after the upgrade. This can cause future system updates via dnf to fail as some packages/package dependencies now depend on the CRB repository. | ||
|
||
This issue can be resolved by enabling the CRB repository. Either via `crb enable` if the EPEL repository is already enabeld, or via `dnf config-manager --set-enabled crb`. After the CRB repository is enabled, the dnf cache can be cleared and dnf update should return to normal functionality. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems CRB/PowerTools could be the most popular case, but a similar issue can also be caused by another repo absence. I suggest pointing this to users and redirecting them to the repos page to check enabling commands - https://wiki.almalinux.org/repos/AlmaLinux.html
This issue can be resolved by enabling the CRB repository. Either via `crb enable` if the EPEL repository is already enabeld, or via `dnf config-manager --set-enabled crb`. After the CRB repository is enabled, the dnf cache can be cleared and dnf update should return to normal functionality. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems CRB/PowerTools could be the most popular case, but a similar issue can also be caused by another repo absence. I suggest pointing this to users and redirecting them to the repos page to check enabling commands - https://wiki.almalinux.org/repos/AlmaLinux.html
PR to address issue #477. Includes updates to frequently encounter issues documentation and the documentation for ELevating from CentOS7 to AlmaLinux 8/9.