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!
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!
FS#19857 - Very good idea for pacman and pacman.log!
Attached to Project:
Arch Linux
Opened by trusktr (trusktr) - Saturday, 19 June 2010, 02:30 GMT
Last edited by Allan McRae (Allan) - Saturday, 19 June 2010, 03:18 GMT
Opened by trusktr (trusktr) - Saturday, 19 June 2010, 02:30 GMT
Last edited by Allan McRae (Allan) - Saturday, 19 June 2010, 03:18 GMT
|
DetailsIt'd be very useful if pacman also included in pacman.log the actual command used (e.g. "pacman -Syu") before actually listing the chain of actions (installed, upgraded, removed, etc).
Currently we see in the log a continuous list of "installed, upgraded, removed, etc". So if you do pacman -Syu, for example, pacman would add many "upgraded" lines to the log. What would be neato is if pacman added one single line that showed the command used (e.g. pacman -Syu) before all of the rest of the lines were added. This would help a ton when researching through the pacman log (which i had to do to figure out why/when/how something was installed on my system. pacman.log provided useful hints, but seeing the command used would definitely confirm the fact that someone else (not me) installed XXX package manually and not as part of a group, etc). |
This task depends upon
[2010-06-19 11:45] synchronizing package lists
[2010-06-19 11:45] starting full system upgrade
Already done in pacman-3.4