public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tony Davison <tony.davison2@ntlworld.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge output
Date: Fri, 26 Aug 2005 01:27:11 +0100	[thread overview]
Message-ID: <200508260127.11405.tony.davison2@ntlworld.com> (raw)
In-Reply-To: <430E58D4.90200@planet.nl>

On Friday 26 August 2005 00:48, Holly Bostick wrote:
> John Dangler schreef:
> > I just did an  emerge –uDv world…
> >
> >
> >
> > during the course of the 22 packages (a lot considering I just
> > loaded this last night), I got some messages saying “please make
> > sure you run … (I couldn’t read it all since it went by so fast)… I
> > got a couple of these before it was over.  Is there a way to view
> > that output after the fact? I didn’t see it in either dmesg or any
> > of the /var/log files…
> >
> >
> >
> > Thanks for the input.
>
> Idea #1: if you know the name of the file or files that had an einfo
> message (if you don't know the names, try looking at the end
> /var/log/emerge.log to see the packages most recently emerged), just
> open the ebuild in a text editor and read it at your leisure.
>
> Idea #2: In whatever console you use, change the size of the
> scrollback buffer to something that seems ridiculously high (my
> buffer is 30000 lines). For most emerges -- even in groups of 20 or
> more-- this should be enough to allow you to scroll back and read any
> einfo messages that you may have noticed. This won't so much work for
> emerges that are themselves more than 30000 lines (for instance, if I
> emerge gcc and then glibc, I won't be able to scroll back and see any
> messages I missed in the gcc emerge once the glibc emerge is an hour
> or so in, but usually it's good enough).
>
> Idea #3: there is a way (and possibly more than one) to tail out the
> einfo messages, either to a file, or to the console, but
> unfortunately I don't remember what they are atm.... Oh, wait,
> they're listed on the Wiki:
>
> http://gentoo-wiki.com/TIP_Portage_utilities_not_in_portage
>
> I think what you might want is portlog-info, which is in the
> Informational Utilities section.
>
There is a little gadget called 'enotice that I use but I';m b*****d if 
I can remember where I got it from, perhaps the above URL.
Just had a look in /usr/sbin/enotice its python script by a guy called 
Eldad Zack <eldad@gentoo.org>  
HTH
-- 
Tony Davison
tony.davison2@ntlworld.com
Its late, I'm tired and out of ciggies, bed time.
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-08-26  0:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25 23:01 [gentoo-user] emerge output John Dangler
2005-08-25 23:48 ` Holly Bostick
2005-08-26  0:27   ` Tony Davison [this message]
2005-08-26  7:49     ` Neil Bothwick
2005-08-26  8:33   ` Mariusz Pękala
2005-08-26 15:49     ` RESOLVED: " John Dangler

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=200508260127.11405.tony.davison2@ntlworld.com \
    --to=tony.davison2@ntlworld.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