This update got my CS8 systems out of the conflicted states!
Doing so at the cost of installing Python 3.11 seems odd, but it Did The Right Thing and didn't disturb the system python 3.6.8, because "alternatives" works.
An additional question: is epel-next the right repo to be fixing problems with epel (-not-next) packages, or should this be pushed to the same repo as the original ones? Otherwise all the breakages won't fix themselves.
This update has been submitted for testing by gotmax23.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
I'm setting the karma requirement to 1 and submitting. Currently, the lack of this update is causing conflicts and breaking users' systems [1]
[1] https://www.reddit.com/r/CentOS/comments/12cmd2j/comment/jf479jn/
gotmax23 edited this update.
This update has been submitted for stable by gotmax23.
This update has been pushed to stable.
This update got my CS8 systems out of the conflicted states! Doing so at the cost of installing Python 3.11 seems odd, but it Did The Right Thing and didn't disturb the system python 3.6.8, because "alternatives" works.
An additional question: is epel-next the right repo to be fixing problems with epel (-not-next) packages, or should this be pushed to the same repo as the original ones? Otherwise all the breakages won't fix themselves.