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#747 - Bad Pacman Behavior with provides=() packages
Attached to Project:
Pacman
Opened by Mike B (tehdely) - Tuesday, 13 April 2004, 22:05 GMT
Last edited by Judd Vinet (judd) - Tuesday, 13 April 2004, 22:11 GMT
Opened by Mike B (tehdely) - Tuesday, 13 April 2004, 22:05 GMT
Last edited by Judd Vinet (judd) - Tuesday, 13 April 2004, 22:11 GMT
|
DetailsWhen installing a package that provides=() a package that is already installed pacman should treat this is a conflict and offer to remove the already installed package. Instead, it attempts to install the new one, which inevitably leads to file conflicts.
Of course a simple pacman -R existing-package, followed by pacman -S/A new-package works, but this behavior should be automatic. Two packages that provide the same thing should always be considered conflicts. |
This task depends upon
for example, x and xfree86 would both have this:
provides=('x-server')
conflicts=('x-server')