FS#673 - Pacman: replaces=() is not honored for 'pacman -U' updates

Attached to Project: Pacman
Opened by Benjamin Bytheway (bytheway) - Thursday, 01 April 2004, 23:59 GMT
Task Type Bug Report
Category
Status Closed
Assigned To No-one
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.6 Widget
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

Details

When trying to update a package directly via a 'pacman -U,' which is meant to replace another package, the update fails with file conflicts. If the package is instead moved to a repository and updated via a 'pacman -S,' replaces is honored and the package updates correctly.

The replaces flag should be honored when updating directly from the file.
This task depends upon

Closed by  Judd Vinet (judd)
Friday, 02 April 2004, 01:15 GMT
Reason for closing:  Not a bug
Comment by Judd Vinet (judd) - Friday, 02 April 2004, 01:14 GMT
This is not a bug, it was implemented that way on purpose. Only --sync pays attention to replaces or provides fields, since they rely on the sync database. -U and -A operations do not rely on a sync database, so they can be used offline.
Comment by Hector Mtz-Seara Monne (hseara) - Friday, 09 December 2011, 09:25 GMT
Well honestly it is an odd implementation. I would have never assumed this behaviour unless I have read it here. I guess that some note when using pacman with -U or -A flags should be added to the pacman log when the package contains a replace line.
Still I do not see the point for such behaviour, as at least in normal installations one always have access to the local pacman database and therefore you can check if the replaces affect anything in your system.

Loading...