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

Fix yum-cron exit conditions #9

Merged
merged 2 commits into from Mar 17, 2016
Merged

Conversation

@dmnks
Copy link
Contributor

dmnks commented Mar 16, 2016

No description provided.

andreasf and others added 2 commits Mar 16, 2016
Even if refreshUpdates() returns True, the transaction may still be
empty if some updateinfo filters were applied there and thus a later
call to buildTransaction() would return 0 (success).  This wasn't
handled by findDeps() properly, making it emit an error message in such
a case.

Note that, in the first place, we shouldn't return True from
refreshUpdates() if the transaction becomes empty after applying the
filters.  However, we should handle this particular buildTransaction()
outcome in findDeps() regardless and that's sufficient to fix this bug.

See also:
http://lists.baseurl.org/pipermail/yum/2014-December/024141.html
megaumi added a commit that referenced this pull request Mar 17, 2016
Fix yum-cron exit conditions
@megaumi megaumi merged commit 0c7e89e into rpm-software-management:master Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.