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#72999 - IgnorePkg affects also not installed dependencies
Attached to Project:
Pacman
Opened by Tomas (Tomaqa) - Monday, 13 December 2021, 15:18 GMT
Last edited by Allan McRae (Allan) - Sunday, 04 December 2022, 02:18 GMT
Opened by Tomas (Tomaqa) - Monday, 13 December 2021, 15:18 GMT
Last edited by Allan McRae (Allan) - Sunday, 04 December 2022, 02:18 GMT
|
DetailsSummary and Info:
A package `<pkg>` that is in IgnorePkg needs a dependency `<dep_pkg>`, that is also in IgnorePkg. None of these packages is installed yet (!) In this case, it is not possible to install the package without specifying its dependency explicitly. I suppose that this is not correct behavior, since IgnorePkg is not for preventing packages from being installed, but it is for preventing packages from being upgraded. Steps to Reproduce: pacman --ignore <pkg> --ignore <dep_pkg> -S <pkg> This would work: pacman --ignore <pkg> --ignore <dep_pkg> -S <pkg> <dep_pkg> |
This task depends upon
Comment by Tomas (Tomaqa) -
Monday, 13 December 2021, 15:53 GMT
Note: the approach with explicitly installing `<dep_pkg>` "works", but marks the package as explicit, not as a dependency.
Comment by Allan McRae (Allan) -
Monday, 13 December 2021, 22:53 GMT
This seems to be expected behaviour to me.