FS#12101 - pacman does not output the "no targets specified" error to stderr

Attached to Project: Pacman
Opened by Brad Conte (B-Con) - Wednesday, 12 November 2008, 10:16 GMT
Last edited by Allan McRae (Allan) - Sunday, 22 April 2012, 11:52 GMT
Task Type Bug Report
Category Output
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 3.2.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
When a -S or -R is performed to add or remove a package, the error "error: no targets specified (use -h for help)" is outputted to stdout, not stderr.


Additional info:
pacman v3.2.1


Steps to reproduce:

$ sudo pacman -R 2> /dev/null
error: no targets specified (use -h for help)
$ sudo pacman -S 2> /dev/null
error: no targets specified (use -h for help)
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 22 April 2012, 11:52 GMT
Reason for closing:  Fixed
Additional comments about closing:  Appears fixed a long time ago
Comment by Allan McRae (Allan) - Thursday, 13 November 2008, 13:45 GMT
The seems to be a lot of stuff at using pm_printf at PM_LOG_ERROR level. Should this all be using pm_fprintf(stderr,...)?
Comment by Nagy Gabor (combo) - Saturday, 15 November 2008, 14:19 GMT
Or modify pm_printf to print PM_LOG_ERROR messages to stderr... In this case probably we could also remove pm_*fprintf functions.

Btw, PM_LOG_ERROR messages sent by alpm are also printed to stdout (callback.c/cb_log).

Loading...