Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42948 - [pacman] explicit install doesn't reset Install Reason

Attached to Project: Arch Linux
Opened by Carl Saṃpūrṇa (crs) - Saturday, 29 November 2014, 03:51 GMT
Last edited by Allan McRae (Allan) - Saturday, 29 November 2014, 05:15 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

A package that was originally installed as a dependency
and is then explicitly reinstalled continues to have an Install Reason (as reported by "pacman -Qi") of "Installed as a dependency". For example:

# pacman -Qi syslinux | grep Reason
Install Reason : Installed as a dependency for another package
# pacman -S syslinux
warning: syslinux-6.03-2 is up to date -- reinstalling
...
# pacman -Qi syslinux | grep Reason
Install Reason : Installed as a dependency for another package
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 29 November 2014, 05:15 GMT
Reason for closing:  Not a bug
Comment by Dave Reisner (falconindy) - Saturday, 29 November 2014, 04:28 GMT
This is by design. If you want to change the install reason, you must do so explicitly, or mark is as explicitly installed:

$ pacman -S --asexplicit $somepkg

# or

$ pacman -D --asexplicit $somepkg
Comment by Doug Newgard (Scimmia) - Saturday, 29 November 2014, 04:29 GMT
Of course not, pacman will not change that when simply reinstalling a package. If you want to change it, you need to specify it with --asexplicit, or using pacman's -D option.
Comment by Carl Saṃpūrṇa (crs) - Saturday, 29 November 2014, 04:47 GMT
Thank you for the explanations, I now understand that this behavior is intentional, though I don't understand the reason for it. To me, it's surprising not to set the install reason to "explicit" when a package is explicitly (re)installed.

Loading...