From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout
Date: Wed, 17 Nov 2010 12:20:09 +1100 [thread overview]
Message-ID: <AANLkTikxPFA3cJuxQgXco=8fFzfcJ2Wptv7C5Frj-ARG@mail.gmail.com> (raw)
In-Reply-To: <20101117002517.GA18328@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 959 bytes --]
> do so today (115 packages emerge). I normally...
>
> emerge -pv --deep --update world | less
>
> ...before updating, to check for booby-traps. Today, the output on the
> backup machine blasted to screen, and did not stop until finished.
> Meanwhile, the bottom of the screen shows "lines 1-4/4 (END) ".
> Actually, it's 151 lines of output. Similarly...
>
> emerge -pv --deep --update world > x
>
> ...shows only 4 lines in file x, while the output blasted to the screen.
>
> emerge -pv --deep --update world > x 2>&1
>
> ...does work, sending everything to file x. That's how I know there are
> 151 lines of output in file x and output is going to stderr. This
> happens on only the backup machine, not the main machine. It's not a
> showstopper, and I can work around it. Having said that, I'd like to do
> a proper fix.
>
My first guess would be different versions of emerge sending output to
different places. Are the portage versions the same?
[-- Attachment #2: Type: text/html, Size: 1247 bytes --]
next prev parent reply other threads:[~2010-11-17 1:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 0:25 [gentoo-user] One machine sends "emerge" text output to stderr, not stdout Walter Dnes
2010-11-17 1:20 ` Adam Carter [this message]
2010-11-17 13:41 ` Stroller
2010-11-18 0:20 ` Walter Dnes
2010-11-18 0:51 ` Alan McKinnon
2010-11-18 4:46 ` Stroller
2010-11-18 11:25 ` Neil Bothwick
2010-11-18 13:24 ` Vincent Launchbury
2010-11-18 14:27 ` [gentoo-user] tmux vs. screen Stroller
2010-11-18 19:52 ` Paul Hartman
2010-11-18 22:25 ` Florian CROUZAT
2010-11-18 22:44 ` Alan McKinnon
2010-11-18 23:36 ` Dale
2010-11-19 10:33 ` Jesús J. Guerrero Botella
2010-11-18 11:21 ` [gentoo-user] One machine sends "emerge" text output to stderr, not stdout Neil Bothwick
2010-11-19 6:34 ` Walter Dnes
2010-11-19 7:21 ` Dale
2010-11-19 9:25 ` Neil Bothwick
2010-11-20 5:32 ` Walter Dnes
2010-11-20 15:04 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikxPFA3cJuxQgXco=8fFzfcJ2Wptv7C5Frj-ARG@mail.gmail.com' \
--to=adamcarter3@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox