From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] One machine sends "emerge" text output to stderr, not stdout
Date: Thu, 18 Nov 2010 04:46:16 +0000 [thread overview]
Message-ID: <B755D414-84AF-4CFA-B387-D56BF41DDE09@stellar.eclipse.co.uk> (raw)
In-Reply-To: <20101118002025.GA23732@waltdnes.org>
On 18/11/2010, at 12:20am, Walter Dnes wrote:
> On Wed, Nov 17, 2010 at 01:41:45PM +0000, Stroller wrote
>
>> It's probably fixed in one of the updates! Why are you posting before
>> you checked that!?!?
>
> It started happening suddenly And yes, I did search bugzilla,
> although I admit my searches aren't always perfect. And if "emerge
> --sync" output ends up telling me there is a portage update, I do run
> it first.
You can't properly check if your bug is fixed in the updates by checking bugzilla. You need to check by *applying* the updates.
In your previous message you didn't tell us that you'd upgraded Portage to the latest before getting this error on 115 remaining updates, and if you did actually do that, it doesn't really matter, because you still need to run the other updates first.
If you phoned HP or Dell tech support and said you had a problem, they would ask if you had the latest version(s) of the software on your machine. They might well expect you to run system update to ensure all system packages are up to date, too. You shouldn't expect more support effort from the list than you would from a company you're paying for help! You might *get* more support effort from the folks here on the list, but that's because we're nice people (well, we all are except me and Alan) - make it easier for us!
I'm sorry if this comes across as rude, but I think it's daft to ask the list for help when your system isn't up to date. It might not fix the problem on this occasion, but don't sneer at me if that's the case because plenty of times it will. You've got more than one easy workaround that will overcome this problem and allow you to review the `emerge --pretend` output for the duration of this emerge. The effort of writing an email asking for help (and giving all the information) is so much more than that of just running the update, that even if the update doesn't fix the problem 95% of the time, it's still less effort cumulatively to always update the system before looking into the problem!
Incidentally: in your original message you stated that you pipe the output of `emerge -pv --update` to less. This will remove colour from the output, cause it to be rendered in black and white, and make it harder to read. I have one machine that doesn't do terminal colours - I don't use it that much, so I'm not sure that it's worth fixing, but only the other day I was marvelling at how much easier it is to read stuff on my Gentoo boxes with with syntax highlighting sprinkled throughout my terminal. For instance I use `export MANPAGER="/usr/bin/most"`. If you're not using a GUI terminal emulator with a scrollbar, then may I respectfully suggest you install `tmux` (a replacement for GNU `screen`) and use it. It takes a little while to get familiar with it, and with its keybindings and stuff, and perhaps even to get into the habit and mindset of using it, but it really is brilliant, and it will allow you to page through output of `emerge --pretend` whilst retaining the colours that portage applies to the USE flag information.
Stroller.
next prev parent reply other threads:[~2010-11-18 4:47 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
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 [this message]
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=B755D414-84AF-4CFA-B387-D56BF41DDE09@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--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