FS#1396 - backup files must not be checked for conflicts

Attached to Project: Pacman
Opened by Mircea Bardac (IceRAM) - Tuesday, 07 September 2004, 20:58 GMT
Last edited by Judd Vinet (judd) - Wednesday, 08 September 2004, 20:02 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

My situation:
I had a damaged dnsmasq package (ver: 2.13-2).
I had to rename by hand /etc/dnsmasq/dnsmasq.conf to /etc/dnsmasq.conf to make it work.
The backup=() line contained /etc/dnsmasq/dnsmasq.conf in 2.13-2. It changed in 2.13-4 to the correct path /etc/dnsmasq.conf.
Unfortunately, when updating from 2.13-2 to 2.13-4, pacman reports /etc/dnsmasq.conf as a file conflict.

IMO, when checking for conflicts for a package, the files marked for backup should be excluded IF the file did NOT belong to any package BEFORE.
This task depends upon

Closed by  Judd Vinet (judd)
Saturday, 18 September 2004, 03:23 GMT
Reason for closing:  Won't implement
Comment by Judd Vinet (judd) - Saturday, 18 September 2004, 03:23 GMT
I think it's better that pacman take the pragmatic (and predictable) route and report the conflict. --force is quick and easy to use, and pacman will always report the full list of file conflicts, so you can sure --force isn't overwriting other files.

Loading...