Disable automated package upgrades on Debian-like boxes #612
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
|
Don't see any reason not to merge this one at present. +1 |
|
@cheeseplus when is the next release planned? I'd need this fix for my ubuntu 16.04 basebox. |
|
@Ma27 Me too |
|
This fix is also incomplete, it requires an additional fix as well - see #609 (comment) The releases aren't planned and are based on the amount of free time I have as an open source maintainer. I'm sorry but life and work are very busy for me at the moment. |
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.
Currently unattended upgrades are enabled, causing unexpected behavior when the daily apt upgrade job runs (with cron.daily on sysv/upstart hosts, and at-boot plus semi-randomly twice a day on hosts with systemd).
Setting this value to none disables the upgrade jobs, in favor of package upgrades only happening when explicitly requested. This would resolve issue #609