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#29002 - [archlinux-keyring] produces too verbose output
Attached to Project:
Arch Linux
Opened by Alexander (AlexanderR) - Monday, 19 March 2012, 10:06 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 21:58 GMT
Opened by Alexander (AlexanderR) - Monday, 19 March 2012, 10:06 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 21:58 GMT
|
DetailsDescription:
Output of pacman during archlinux-keyring installation/update increases 5-fold in log and approximately 10-fold in console. Number of developers can potentionally increase over time, making this worse. Steps to reproduce: pacman -S archlinux-keyring Possible solution: Modify archlinux-keyring/pacman-key to limit output to total number of imported/updated keys and instead of listing every developer's status and reformat/reduce "Locally signing" messages verbosity. |
This task depends upon
Closed by Pierre Schmitz (Pierre)
Saturday, 02 November 2013, 21:58 GMT
Reason for closing: Upstream
Saturday, 02 November 2013, 21:58 GMT
Reason for closing: Upstream
Comment by Greg (dolby) -
Tuesday, 13 November 2012, 22:15 GMT
Additionally it doesnt make sense logging the output of pacman-key --populate archlinux to pacman.conf.
Comment by Pierre Schmitz (Pierre) -
Saturday, 02 November 2013, 21:58 GMT
This can only be fixed in pacman-keyring (part of the pacman package)