Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#12293 - When replacing packages pacman removes old packages before checking file conflicts
Attached to Project:
Pacman
Opened by Andrew Eikum (ColdPie) - Sunday, 30 November 2008, 21:18 GMT
Last edited by Dan McGee (toofishes) - Monday, 13 April 2009, 15:08 GMT
Opened by Andrew Eikum (ColdPie) - Sunday, 30 November 2008, 21:18 GMT
Last edited by Dan McGee (toofishes) - Monday, 13 April 2009, 15:08 GMT
|
DetailsA package upgrade today said to replace esd with extra/esound. After downloading all of the packages, it removed esd as expected. After removing the old package, it checked for file conflits, and found a conflict in catalyst-utils, which caused no packages to be upgraded. Since the new esound package was not installed, it doesn't seem right that the old esd package (which was intended to be replaced) should remain removed -- my system is now missing a package. Thankfully it printed a warning about one of the config files moving, otherwise it likely would've slipped under the radar.
Attached is pacman output from the failed upgrade. |
This task depends upon
Closed by Dan McGee (toofishes)
Monday, 13 April 2009, 15:08 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#9088
Monday, 13 April 2009, 15:08 GMT
Reason for closing: Duplicate
Additional comments about closing:
pacman-esd-log
FS#9088?I don't know that part of the code that well, but can we just schedule the actual removal for after the conflict checking? It would require conflict checking to know what files were belonging to the removed packages.