FS#31344 - Special handling of conflicting backup files

Attached to Project: Pacman
Opened by Thomas Bächler (brain0) - Thursday, 30 August 2012, 19:50 GMT
Last edited by Thomas Bächler (brain0) - Thursday, 30 August 2012, 21:53 GMT
Task Type Feature Request
Category Backend/Core
Status Closed
Assigned To Dan McGee (toofishes)
Allan McRae (Allan)
Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version 4.0.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Suppose you install or upgrade a package that contains a file that
1) is new in the package
2) is not contained in any other package
3) is marked as a backup file
4) already exists in the file system

Right now, this will result in a conflict and the installation is aborted. I propose that pacman will extract the file as .pacnew instead in this case.

Optionally, the user could also be asked to a) abort, b) overwrite, c) extract as .pacnew, but c) should be the default behaviour.
This task depends upon

Closed by  Thomas Bächler (brain0)
Thursday, 30 August 2012, 21:53 GMT
Reason for closing:  None
Additional comments about closing:  I'm an idiot.
Comment by Allan McRae (Allan) - Thursday, 30 August 2012, 21:48 GMT
It works in git... The file on the filesystem gets moved to .pacorig and the new one installed.

warning: /etc/foobar.conf saved as /etc/foobar.conf.pacorig

I was sure this is an old, old behaviour...

Loading...