Handle pacman upgrade creating .pacnew files #56
Merged
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.
In case a pacman upgrade changes a file that is marked for backup
it leaves it alone and installs it as .pacnew instead and warns
the user.
In our case we change pacman.conf to skip CheckSpace. If pacman would
then update itself it would save any new pacman.conf as pacman.conf.pacnew.
Fix this by replacing the file manually.