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#57191 - pacman -Qdt misses optional dependency cycles
Attached to Project:
Pacman
Opened by Yakumo Ran (kitsunyan) - Monday, 22 January 2018, 13:19 GMT
Last edited by Allan McRae (Allan) - Monday, 22 January 2018, 21:10 GMT
Opened by Yakumo Ran (kitsunyan) - Monday, 22 January 2018, 13:19 GMT
Last edited by Allan McRae (Allan) - Monday, 22 January 2018, 21:10 GMT
|
DetailsPacman 5.0.2
# pacman -S --asdeps npm npm depends on nodejs while nodejs optionally depends on npm. In this case $ pacman -Qdt npm prints nothing and exits with 1. I'm used to use `pacman -Qdtq | sudo pacman -Rsn -` to remove orphans but it doesn't work for npm package which I install sometimes to build some packages. |
This task depends upon
pacman -Qttd lists npm.
Both npm and nodejs installed as dependencies, there are no explicit packages dependent on them. But they aren't listed with pacman -Qdt. The behavior I'm talking about in the report is definitely incorrect.
nodejs is a dependency for for npm semver
"pacman -Qtd" will not show it as both packages are required or optionally required by other packages.
"pacman -Qttd" does show it, because npm is not directly required by anything.
So this is working completely as documented.