Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 126111 - emerge's 'performing global update' output should not go to stderr
Summary: emerge's 'performing global update' output should not go to stderr
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks: 115839
  Show dependency tree
 
Reported: 2006-03-13 21:07 UTC by Matthew Marlowe (RETIRED)
Modified: 2006-03-14 18:07 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Marlowe (RETIRED) gentoo-dev 2006-03-13 21:07:24 UTC
All of emerge's normal output goes to stdout, except for 'performing global updates' which is being written to stderr.  This is wrong and can impact user automation scripts for portage.
Comment 1 Zac Medico gentoo-dev 2006-03-14 14:01:25 UTC
Thanks for reporting.  This is now in svn r2888 for the next release.
Comment 2 Jason Stubbs (RETIRED) gentoo-dev 2006-03-14 16:19:31 UTC
Of course, moving it to stdout is just as likely to break scripts that parse portage's output. revdep-rebuild perhaps?

In the long run it should probably be going to stdout anyway, though.
Comment 3 Zac Medico gentoo-dev 2006-03-14 16:37:46 UTC
(In reply to comment #2)
> Of course, moving it to stdout is just as likely to break scripts that parse
> portage's output. revdep-rebuild perhaps?

Good point.  I've routed all the output through writemsg_stdout, which defaults to noiselevel=0 and thus will not output when --quiet is enabled (which sets portage_util.noiselimit=-1).  The current version of revdep-rebuild uses --quiet so at least that should not break because of this.
Comment 4 Zac Medico gentoo-dev 2006-03-14 18:07:29 UTC
Released in 2.1_pre6-r3.