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

Handle pacman upgrade creating .pacnew files #56

Merged
merged 1 commit into from
Jul 26, 2020

Conversation

lazka
Copy link
Member

@lazka lazka commented Jul 26, 2020

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.

@eine
Copy link
Collaborator

eine commented Jul 26, 2020

Look good. Can you please rebase?

In case a pacman upgrade changes a file that is marked for backup
it leaves it alone and installs it as <name>.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.
@eine eine merged commit d2ba8bd into msys2:master Jul 26, 2020
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.

2 participants