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#10686 - abs: script should only output error messages to STDERR, all the rest should go to STDOUT
Attached to Project:
Pacman
Opened by Glenn Matthys (RedShift) - Wednesday, 18 June 2008, 08:11 GMT
Last edited by Allan McRae (Allan) - Thursday, 10 July 2008, 10:54 GMT
Opened by Glenn Matthys (RedShift) - Wednesday, 18 June 2008, 08:11 GMT
Last edited by Allan McRae (Allan) - Thursday, 10 July 2008, 10:54 GMT
|
DetailsDescription:
The abs script puts all its output in STDERR, while it should only put errors in STDERR, and all other (informational) output should go to STDOUT. This prevents setups like these: abs > /dev/null and if any errors would occur by the abs script itself, you'd still see them. An example application is running the abs script in a cronjob. This bug was found because of Additional info: * package version(s): 2.1-1 * config and/or log files etc. Steps to reproduce: Run abs > /dev/null, and informational messages are still being shown. |
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 10 July 2008, 10:54 GMT
Reason for closing: Fixed
Additional comments about closing: Fix in git commit 8a158d6affff50049c8abf19445ecd0e72bb3ee7
Thursday, 10 July 2008, 10:54 GMT
Reason for closing: Fixed
Additional comments about closing: Fix in git commit 8a158d6affff50049c8abf19445ecd0e72bb3ee7