Skip to content
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

[2016.3] Merge forward from 2015.8 into 2016.3 #35903

Merged
merged 9 commits into from
Aug 30, 2016

Conversation

rallytime
Copy link
Contributor

No conflicts.

vutny and others added 9 commits August 29, 2016 18:10
This was initially broken in 75fd92f. The documented behavior of this
function is to return an empty string for the package when the package
is up-to-date. Changing that behavior negatively affects the pkg.latest
state, which relies on the documented behavior.
These comments explain what is being done as we evaluate which packages
need to be added to the install targets and which do not.
In this scenario, ``avail[pkg]`` contains an empty string, we want to
reinstall the current version with new USE flags so the
currently-installed version is what we need to add to the targets.
…st-logic

Add clarifying comments to the pkg.latest state, fix USE flag condition
pacman.py: Fix incorrect return in pkg.latest_version
[BACKPORT 2015.8] salt-cloud: fix path to Salt Master socket dir
@rallytime rallytime merged commit 95b89db into saltstack:2016.3 Aug 30, 2016
@rallytime rallytime deleted the merge-2016.3 branch August 30, 2016 17:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants