Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 73824 - emerge --info spits garbage on stderr
Summary: emerge --info spits garbage on stderr
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: All All
: High minor (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks:
 
Reported: 2004-12-08 10:57 UTC by Aron Griffis (RETIRED)
Modified: 2005-07-14 06:58 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 Aron Griffis (RETIRED) gentoo-dev 2004-12-08 10:57:26 UTC
When capturing output of emerge --info into a variable, the crap at the top is unexpected.

$ emerge --info 2>&1 | cat -v
^[]2;Started emerge on: Dec 08, 2004 13:54:20^G^[]2; *** emerge  info^GGentoo Base System version 1.6.7
^[]2; *** terminating.^G^[]2;xterm^GPortage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.8-gentoo-r4-kt600 i686)
=================================================================
System uname: 2.6.8-gentoo-r4-kt600 i686 AMD Athlon(tm) XP 1800+
...
Comment 1 Nicholas Jones (RETIRED) gentoo-dev 2005-01-10 18:51:12 UTC
--nocolor ?
Comment 2 Aron Griffis (RETIRED) gentoo-dev 2005-01-12 13:41:21 UTC
$ emerge --info --nocolor
!!! Error: --nocolor is an invalid option.

Besides, if you look at that output carefully, it's not color stuff.
Comment 3 Jason Stubbs (RETIRED) gentoo-dev 2005-01-29 19:47:21 UTC
That's the codes to change the xterm title.. Disabling that when the terminal is not a tty would suffice?
Comment 4 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 05:47:48 UTC
Fixed on or before 2.0.51.22-r1 
Comment 5 Jason Stubbs (RETIRED) gentoo-dev 2005-07-14 06:58:34 UTC
Looking through the batch of bugs, I'm not sure that some of these are 
actually fixed in stable. Others, the requirements have possibly changed after 
the initial fix was committed. 
 
If you think this bug has been closed incorrectly, please reopen or ask that 
it be reopened.