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#2421 - pacman not reassigning ownership of files on a forced install
Attached to Project:
Pacman
Opened by Mircea Bardac (IceRAM) - Sunday, 20 March 2005, 22:19 GMT
Last edited by Simo Leone (neotuli) - Sunday, 15 October 2006, 19:52 GMT
Opened by Mircea Bardac (IceRAM) - Sunday, 20 March 2005, 22:19 GMT
Last edited by Simo Leone (neotuli) - Sunday, 15 October 2006, 19:52 GMT
|
DetailsMy case (already FlySprayed):
- I have installed kmplayer-0.8.4-1 - trying to install kaffeine-0.6-1 returns a conflict: >> kaffeine: >> /opt/kde/share/mimelnk/application/x-mplayer2.desktop: exists in filesystem - that file is owned by kmplayer After installing kaffeine with -f pacman flag I rechecked the ownership of that file with 'pacman -Qo file'. It still returned kmplayer, even if I forcely told pacman to overwrite the kmplayer file with the kaffeine file. The solution, as I see it, is to remove the conflicting file from the filelist of the previous package and leave it only in the filelist of the new package (which was installed with -f). This would prevent that file being removed from the system if the 1st package is removed. Indeed, conflicts are to be avoided, but taking care of this problem which might occur sometimes would add extra stability for the system. |
This task depends upon
Conflict changes are improved and pacman 3 and this should be fixed. Closing for now. If this comes up under pacman3, we can add a new bug.