[gentoo-user] emerge output

[gentoo-user] emerge output

[John Dangler]

[-- Attachment #1: Type: text/plain, Size: 568 bytes --]

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.

 

Regards,

 

John Dangler

GenoFit

800-505-4078 (Corporate)

386-767-3730 (Direct)

866-273-0408 (Fax)

www.genofit.com

jdangler@genofit.com

 


[-- Attachment #2: Type: text/html, Size: 3623 bytes --]

Re: [gentoo-user] emerge output

[Holly Bostick]

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.

HTH,
Holly
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge output

[Tony Davison]

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

Re: [gentoo-user] emerge output

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 678 bytes --]

On Fri, 26 Aug 2005 01:27:11 +0100, Tony Davison wrote:

> 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.

It's in the Gentoo Script Repository at
http://gentooexperimental.org/script/repo/list

An alternative is to set PORT_LOGDIR in /etc/make.conf, and create
whatever directory you set it to. You'll find two log files in here for
each emerge, one contains all the compiler output, the other has the
info and warning messages.

There was a script to mail these to you, but I can't find it now.


-- 
Neil Bothwick

Barnum was wrong....it's more like every 30 seconds!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] emerge output

[Mariusz Pękala]

[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]

On 2005-08-26 01:48:36 +0200 (Fri, Aug), Holly Bostick wrote:
> 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.

...or something dumber^H^H^H^H^Hsimpler:


# ---------------------------------------
#!/bin/bash

COUNT=60

cd /var/log/portage || exit -1

for file in $( ls -1rt | tail -n $COUNT)
do
  if grep $'\e' "$file" | grep -q -v -e " Applying [^ ]*.patch" -e $'\e'"\[32;01mok"$'\e'"\[34;01m"
  then
    tput bold
    echo ' ----------------------------------------------------'
    ls -l "$file"
    echo ' ----------------------------------------------------'
    tput sgr0
    
    grep $'\e' "$file" | grep -v " Applying [^ ]*.patch"
  fi
done
# ---------------------------------------
  
The log files are created when you set the PORT_LOGDIR in /etc/make.conf
(yeah, you replace then that "cd /var/log/portage" with your - possibly
different - location, or do something like eval $(grep "^PORT_LOGDIR="
/etc/make.conf)) .

HTH

-- 
No virus found in this outgoing message.
Checked by 'grep -i virus $MESSAGE'
Trust me.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

RESOLVED: [gentoo-user] emerge output

[John Dangler]

Neil, Mariusz~

Thanks for the input.  Just setting up PORT_LOGDIR has gone a long way to
providing exactly what I'm looking for.  It's a shame that this isn't setup
by default, but I can think of a few reasons why it isn't.

John D 

-----Original Message-----
From: Mariusz Pêkala [mailto:skoot@qi.pl] 
Sent: Friday, August 26, 2005 4:33 AM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge output

On 2005-08-26 01:48:36 +0200 (Fri, Aug), Holly Bostick wrote:
> 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.

...or something dumber^H^H^H^H^Hsimpler:


# ---------------------------------------
#!/bin/bash

COUNT=60

cd /var/log/portage || exit -1

for file in $( ls -1rt | tail -n $COUNT)
do
  if grep $'\e' "$file" | grep -q -v -e " Applying [^ ]*.patch" -e
$'\e'"\[32;01mok"$'\e'"\[34;01m"
  then
    tput bold
    echo ' ----------------------------------------------------'
    ls -l "$file"
    echo ' ----------------------------------------------------'
    tput sgr0
    
    grep $'\e' "$file" | grep -v " Applying [^ ]*.patch"
  fi
done
# ---------------------------------------
  
The log files are created when you set the PORT_LOGDIR in /etc/make.conf
(yeah, you replace then that "cd /var/log/portage" with your - possibly
different - location, or do something like eval $(grep "^PORT_LOGDIR="
/etc/make.conf)) .

HTH

-- 
No virus found in this outgoing message.
Checked by 'grep -i virus $MESSAGE'
Trust me.



-- 
gentoo-user@gentoo.org mailing list