Sb clang include epoch in ext #28
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
Black Duck Security ReportMerging #28 into master will not change security risk. |
JakeMathews
approved these changes
May 7, 2019
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.
Clang: DPKG and RPM packages may or may not specify a version string. If specified, it should be be prefixed to the version string as: epoch:version. These changes make that happen. For DPKG, the epoch was already being included (no special code required since it's included in the version string in the pkg mgr command output) so I just added tests to verify that.
For RPM, the pkg mgr command, and the way it is parsed, have changed to include epoch in version. The epoch is not built into the version string by the pkg mgr, so that work needs to be done in Detect code.