-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Fix rpm version comparison #70231
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
Open
vzhestkov
wants to merge
3
commits into
saltstack:3006.x
Choose a base branch
from
vzhestkov:fix-rpm-version-comparison
base: 3006.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+44
−34
Open
Fix rpm version comparison #70231
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
According to rpmdev-vercmp, these should be 0 not
1and-1There 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.
And it's wrong just to call it this way. I mean
rpmdev-vercmpshold compare separately eitherepochorversionorrelease. In case of using2.0-in reality it should be treated as the release with empty string value, while2.0is just a version with no release at all. In this particular call actually2.0-as version value is compared to2.0as a version value only, assuming there is no release in both cases.rpmdev-vercmpmust be called separatelly forepochand if it's equal or omitted,versions should be compared and if identical,releases. But for2.0-in this context it's version where-is just dropped byrpmlogic as it shouldn't be there.zypperhere is intended to compare full[epoch]:version-releasestrings.For some reason different version comparison libs are using slightly different logic causing some mess. In this exable above
zypperis usinglibsolvinternally which is using exact copy of logic fromrpmitself.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.
From all research that I have done, an rpm without a release is not a valid case. An rpm that does not have a release field is invalid and I believe the tool should be rejecting it.
https://rpm.org/docs/latest/man/rpm-version.7#Comparing
The release is not required to be in the EVR but the RPM information is still required to have the release field.
What is the actual use case where you are even running into this problem? It seems these RPMs may be invalid and whatever tool is building them needs to be fixed?
The lua rpm.vercmp does seem to agree with your comparison though: