Pacman

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.
Tasklist

FS#19567 - Explicitly reinstalling a package installed as a dependency doesn't change the install reason

Attached to Project: Pacman
Opened by Wieland Hoffmann (Mineo) - Sunday, 23 May 2010, 14:41 GMT
Last edited by Dan McGee (toofishes) - Thursday, 08 July 2010, 05:14 GMT
Task Type Bug Report
Category Backend/Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 3.3.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
If one explicitly installs a package which is already installed (as a (make-)dependency for some other package the install reason for the package doesn't change. This causes the package to appear in the output of e.g. pacman -Qdt.

Steps to Reproduce:
Install a package A with dependencies.
Decide you want to keep one of the dependencies B (git/hg/some useful app/...)
Remove package A
Run pacman -Qdt - it shows package B
Run pacman -Qi B - the install reason will be: "Install Reason : Installed as a dependency for another package"
This task depends upon

Closed by  Dan McGee (toofishes)
Thursday, 08 July 2010, 05:14 GMT
Reason for closing:  Not a bug
Additional comments about closing:  See comments.
Comment by Xavier (shining) - Sunday, 23 May 2010, 15:14 GMT
- Decide you want to keep one of the dependencies B (git/hg/some useful app/...)

Well that's not done automatically, you simply need to tell pacman about it :
pacman -S --asexplicit B
Comment by Dan McGee (toofishes) - Thursday, 08 July 2010, 05:13 GMT
This is intended behavior, and with the new -D options in 3.4, you don't even need to reinstall (but you of course can).

Loading...