Fix parsing of uek-next versions for 6.9.0 #92
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The new kernel-ueknext 6.9.0 RPMs include "next" in the extraversion of the uname, which we don't detect. Support this and remove the hack for detecting UEK-next going forward. Signed-off-by: Stephen Brennan <[email protected]>
oracle-contributor-agreement
bot
added
the
OCA Verified
brenns10
changed the title
biger410
approved these changes
Aug 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a branch to handle the change in uek-next version strings:
from: 6.8.0-2.el9uek.x86_64
to: 6.9.0-2.el9ueknext.x86_64
I did go ahead and make fixes for uek-next tests to allow them to pass. However, I've removed those to a branch which will not be part of the v1 milestone as they're not super important.