FS#33077 - Reliance on local db in conflict checking
Attached to Project:
Pacman
Opened by Allan McRae (Allan) - Thursday, 13 December 2012, 11:09 GMT
Last edited by Allan McRae (Allan) - Thursday, 15 December 2022, 01:15 GMT
Opened by Allan McRae (Allan) - Thursday, 13 December 2012, 11:09 GMT
Last edited by Allan McRae (Allan) - Thursday, 15 December 2022, 01:15 GMT
|
Details
When upgrading a package, we compare the new file list to
the file list in the local db and only look at the
difference when looking for conflicts. This can miss issues
and cause pacman to abort part way through.
e.g. filesystem has file "/var/run" and a user replaces it with a directory. Next filesystem update, pacman refuses to extract the /var/run file over a directory and bails. We can address this by checking the file types of the intersection of the file lists, but that may be slow... But perhaps the extraction phase might speed up in compensation due to all files being previously accessed? |
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 15 December 2022, 01:15 GMT
Reason for closing: Won't fix
Additional comments about closing: pacman is the system package manager. Changes outside of that will not be supported
Thursday, 15 December 2022, 01:15 GMT
Reason for closing: Won't fix
Additional comments about closing: pacman is the system package manager. Changes outside of that will not be supported