For the purposes of cron scripts I use the command: /usr/bin/emerge -quND world > /dev/null I would expect this to only leave me with the stderr output (regardless of the presence of the -q flag). But I routinely get the output from some (not all?) of the wget commands portage executes. No other extra output is observed. I would expect that all of the output from wget should be directed to stdout. Especially when the result of the wget command is successful. I will attach sample output from the above command when run by cron. -Mark
Created attachment 125395 [details] output of: emerge -quDN > /dev/null
This isn't a portage bug, per se. wget automatically sends the output to stderr.
You can try adding the -q option to FETCHCOMMAND and RESUMECOMMAND in make.conf. You can see the current values with portageq: portageq envvar FETCHCOMMAND /usr/bin/wget -t 5 -T 60 --passive-ftp -O ${DISTDIR}/${FILE} ${URI} portageq envvar RESUMECOMMAND /usr/bin/wget -c -t 5 -T 60 --passive-ftp -O ${DISTDIR}/${FILE} ${URI} I think this will work if you do: export FETCHCOMMAND='/usr/bin/wget -q -t 5 -T 60 --passive-ftp -O ${DISTDIR}/${FILE} ${URI}' export RESUMECOMMAND='/usr/bin/wget -q -c -t 5 -T 60 --passive-ftp -O ${DISTDIR}/${FILE} ${URI}' /usr/bin/emerge -quND world > /dev/null HTH.
Thanks for the suggestion Steve L. I will try that. However I still believe that this behavior is a bug. The program is not as useful if extraneous information is being sent to stderr. I'm sure anyone writing bash scripts to wrap emerge will run into all of this wget output where it shouldn't be. I noticed in portage_exec.spawn(), the fd_pipes parameter can be used to redirect stderr to stdout for a particular command. I realize this will of course redirect real wget errors to stdout too, but perhaps portage can send a message to stderr if the wget commmand's return status is an error. -Mark
Created attachment 125529 [details, diff] direct all FETCHCOMMAND output to stdout Thanks, this is fixed in svn r7331.
This has been released in 2.1.3_rc9.
