FS#47993 - .pacnew config files are removed, if modified files exist

Attached to Project: Pacman
Opened by This Account (and mail) is dead. (macaronyde) - Tuesday, 02 February 2016, 13:21 GMT
Last edited by Allan McRae (Allan) - Monday, 22 February 2016, 01:30 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Andrew Gregory (andrewgregory)
Architecture All
Severity Low
Priority Normal
Reported Version 5.0.0
Due in Version 5.0.1
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
lib/libalpm/add.c has a different handling.
In Version 4.2.1 was a checkfile (.paccheck) created to test, if the config has changed. The unlink for the .paccheck is fine.
Now the .pacnew is used to check for any changes, and it got unlinked afterwards.

I don't know, if this is intended, but I liked to have the original config file.
This task depends upon

Closed by  Allan McRae (Allan)
Monday, 22 February 2016, 01:30 GMT
Reason for closing:  Fixed
Additional comments about closing:  git commit fd936c9e
Comment by This Account (and mail) is dead. (macaronyde) - Monday, 08 February 2016, 16:36 GMT
As I've seen by now, if a changed config is in the package, then a .pacnew file is created otherwise the .pacnew file is removed.

Loading...