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#57011 - "replaces" ignored if package being replaced exists in higher priority repo
Attached to Project:
Pacman
Opened by Doug Newgard (Scimmia) - Monday, 08 January 2018, 16:47 GMT
Last edited by Andrew Gregory (andrewgregory) - Monday, 08 January 2018, 17:18 GMT
Opened by Doug Newgard (Scimmia) - Monday, 08 January 2018, 16:47 GMT
Last edited by Andrew Gregory (andrewgregory) - Monday, 08 January 2018, 17:18 GMT
|
DetailsCurrently in Arch, we have glew-wayland which (erroneously) replaces glew. I would expect a prompt to replace glew with glew-wayland, but it doesn't happen because glew-wayland is in community and glew is in extra.
This is a good thing in this case since it's a mistake, and the package being replaced wouldn't exist if it were legit. A situation could happen, though, where a package was added to community-testing which correctly replaces something that still exists in extra. In that case, pacman would fail. |
This task depends upon
Closed by Andrew Gregory (andrewgregory)
Monday, 08 January 2018, 17:18 GMT
Reason for closing: Not a bug
Additional comments about closing: Reorder repos so that community-testing has priority.
Monday, 08 January 2018, 17:18 GMT
Reason for closing: Not a bug
Additional comments about closing: Reorder repos so that community-testing has priority.