Skip to content
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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

cyclops26
Copy link

PR to address issue #477. Includes updates to frequently encounter issues documentation and the documentation for ELevating from CentOS7 to AlmaLinux 8/9.

@bennyvasquez
Copy link
Sponsor Member

Thank you!

@bennyvasquez
Copy link
Sponsor Member

@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.

@bennyvasquez bennyvasquez added documentation Improvements or additions to documentation enhancement New feature or request labels Sep 2, 2024
Comment on lines +125 to +127
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.
Copy link
Contributor

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

Comment on lines +237 to +238
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.

Copy link
Contributor

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

@bennyvasquez bennyvasquez added the question Further information is requested label Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request question Further information is requested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants