-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
ignore_epoch needs to be passed through to version_cmp functions #34397
Comments
@jaredhanson11 thanks for the heads up. ping @terminalmage looks like there is some problems here when using what i believe is an epoch number when comparing packages. Do you think this is a bug/issue? |
@jaredhanson11 As of 2015.8.9 there is an |
@terminalmage I loop through all the local packages that are gathered with |
pkg.version_cmp
edge case
@jaredhanson11 OK, then I just need to adjust the code to pass through the |
@jaredhanson11 This is implemented in #34531. |
#34531 has been merged, closing. |
just a heads up. If you update to 2016.3.2 and do not restart the minions this merge will cause and error message:
It goes away once you restart the minion |
Description of Issue/Question
Not necessarily an issue or bug, but just as something I've noticed while working with
pkg.version_cmp
that you guys may or may not want to address. I've been working on a cve scan for HubbleStack, and sometimes the vulnerable package version number I grab from an outside source will not correspond exactly to the format given bypkg.list_pkgs
. It can happen that local version number is1:6.6p1-2ubuntu2.4
while the source of the cve's returns the vulnerable version number as6.6p1-2ubuntu2.7
, omitting the prefix1:
. This can cause unwanted behavior by thepkg.version_cmp
command. I work around it by getting rid of allx:
prefixes, but it would be nice to havepkg.version_cmp
handle the discrepancy, or at least returnNone
representing an error comparing the versions.Steps to Reproduce Issue
Versions Report
The text was updated successfully, but these errors were encountered: