FS#24543 - pacman loses track for backup entries while renaming packages(replaces)

Attached to Project: Pacman
Opened by Ionut Biru (wonder) - Thursday, 02 June 2011, 08:56 GMT
Last edited by Allan McRae (Allan) - Monday, 20 February 2012, 06:05 GMT
Task Type Bug Report
Category General
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 3.5.2
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


Summary and Info:
I know that this behavior seems reasonable while handling backups because we cannot really know that the files should be preserved but there are situations when you want backup to preserved across renaming like kernel26->linux without doing any hacks in a .install

maybe a new option should be added specifying that we want to preserve this file while replacing package1 with package2

lets do this test with two simple builds

package1 and package2
package1 has a backup entry etc/test
package2 has a backup entry etc/test

add some text in etc/test after installing package1
Steps to Reproduce:

pacman -Syu
(1/1) removing package1
warning: /etc/test saved as /etc/test.pacsave
(1/1) installing package2
This task depends upon

Comment by Dan McGee (toofishes) - Thursday, 02 June 2011, 13:09 GMT
At least this is pactest-able. I'll whip it up into one and get it into our tree.
Comment by Dan McGee (toofishes) - Thursday, 02 June 2011, 22:16 GMT
Fixing FS#23011 would make the pieces fall into place to fix this, but short of that the solution would be a big hack, unfortunately. I did create a test case that will be committed to the codebase so we can eventually fix this, but it isn't going to happen before this non-issue with having to rename the kernel26 package.