FS#2332 - pacman doesn't check for moving files on upgrade

Attached to Project: Pacman
Opened by Tobias Powalowski (tpowa) - Monday, 07 March 2005, 14:01 GMT
Last edited by Judd Vinet (judd) - Monday, 07 March 2005, 19:42 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

hi
i add this, that i can do a link to the bug that is already known.
problem:
if files move between packages pacman doesn't recognize it and updates packages in wrong order.

example:
packaga A provides: testfile-A
package B provides: testfile-B
now testfile-A moves to package-B:
on upgrade this will happen:
package B gets first updated, provides testfile-A
after it package A gets updated --> testfile A gets removed
--> missing files will happen

problem is the upgrade order of packages.

hope it was clear enough :)
This task depends upon

Closed by  Judd Vinet (judd)
Friday, 22 April 2005, 00:25 GMT
Reason for closing:  Fixed
Additional comments about closing:  I've fixed this using Paul's suggestion. 2.9.6 will be released soon.
Comment by Paul Mattal (paul) - Wednesday, 16 March 2005, 11:43 GMT
I wonder if changing the upgrade order is the only solution here. At the file conflict checking step, one might also be able to make a "skip list" of files that shouldn't be removed later on. My gut tells me this might be easier than having the order determined by this sort of "dependency" created between the packages.

I *think* this might be easier to implement and also accomplishes what is needed.
Comment by Glenn Matthys (RedShift) - Monday, 21 March 2005, 16:10 GMT
This cleary states the need for functionality in pacman to see if all files have been installed. In short, we need a big update to pacman :-D

Loading...