Re: [gentoo-user] Need coaching with emerge failure logs (Understanting the problem)

2017-02-27 Thread Neil Bothwick
On Mon, 27 Feb 2017 07:31:22 +, Thomas Mueller wrote:

> > On Sat, 25 Feb 2017 21:58:05 +0100, Miroslav Rovis wrote:  
> 
> > > On 170225-09:19-0500, Harry Putnam wrote:  
> > > > Setup: VBox vm running gentoo(amd64) guest on a win-10 (64bit)
> > > > host Hardware: HP xw8600 - 2x Xeon  CPU X5450 @ 3.00GHz - 32 GB
> > > > ram  
> 
> > >  [ some cca. 80k text cut here ]  
> 
> > > Go for the guides, in which you will find that sending 5.5M log in
> > > an email is plain wrong.  
> 
> > On this list, it is preferred to attach logs rather than post them
> > elsewhere with a link. That way all the information stays together.  
> 
> > However, as Stroller mentioned, the escape codes make a bit of a mess.
> > Logs this large could be gzipped before attaching.  

> A 5.5M log is too much for most people, myself included, to read.

Reading it is a separate issue from how you provide it, but this
particular log was unusually large.
 
> Gzipping has two disadvantages: can not be read directly, one being
> that the attachment must be extracted to a separate file for reading
> outside the mail client.

The same is true of providing a link to a file stored elsewhere.
 
> Other downside is that a gzipped file must then be base64-encoded for
> email.  Base64 encoding multiplies the attachment size by 4/3
> (four-thirds), negating most of the reason for gzipping.

In the case of logfiles, you can often achieve 90% compression, so it is
one of the few cases where this does still save a lot of space. But the
real solution here would be to strip the escape codes first as they add a
lot of bloat and make the logs more difficult to read.

It's all about making the information as accessible as possible, if you
put barriers in the way of reading it, people won't bother, including
some that know the answer.


-- 
Neil Bothwick

What did the first man to discover you can get milk from cows think he
was doing? - anon.


pgp6MHedBrc3d.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Need coaching with emerge failure logs (Understanting the problem)

2017-02-26 Thread Thomas Mueller
> On Sat, 25 Feb 2017 21:58:05 +0100, Miroslav Rovis wrote:

> > On 170225-09:19-0500, Harry Putnam wrote:
> > > Setup: VBox vm running gentoo(amd64) guest on a win-10 (64bit) host
> > >  Hardware: HP xw8600 - 2x Xeon  CPU X5450 @ 3.00GHz - 32 GB ram

> >  [ some cca. 80k text cut here ]

> > Go for the guides, in which you will find that sending 5.5M log in an
> > email is plain wrong.

> On this list, it is preferred to attach logs rather than post them
> elsewhere with a link. That way all the information stays together.

> However, as Stroller mentioned, the escape codes make a bit of a mess.
> Logs this large could be gzipped before attaching.

> > Read e.g. how to post bugs on Bugzilla. shouldn't be hard to find.

> This wasn't a bug report but a request for help.


> Neil Bothwick

A 5.5M log is too much for most people, myself included, to read.

Gzipping has two disadvantages: can not be read directly, one being that the 
attachment must be extracted to a separate file for reading outside the mail 
client.

Other downside is that a gzipped file must then be base64-encoded for email.  
Base64 encoding multiplies the attachment size by 4/3 (four-thirds), negating 
most of the reason for gzipping.

Tom




Re: [gentoo-user] Need coaching with emerge failure logs (Understanting the problem)

2017-02-26 Thread Stroller

> On 26 Feb 2017, at 14:42, Harry Putnam  wrote:
> 
> My biggest trouble is that I just don't see anything looking like a
> clue that I recognize as such in those logs.

I always search for "error", and look around the first one.

I'd have assumed subsequent errors would be a result of the first one.

Early in the log you sent there are a couple of entries like this:

Checking for libvpx: 
  vpx not found at -lvpx  or vpx headers not found
  Check the file 
/var/tmp/portage/app-emulation/virtualbox-guest-additions-5.1.14/work/VirtualBox-5.1.14/configure.log
 for detailed error information.

But then the emerge continues for many hundreds of lines more, apparently 
unaffected.

I would google the "vpx not found…" line and see if I get any hints, but I 
don't feel that's important - I think it may just be a warning.

The string "error" comes up a couple of times in the context of -Werror 
compiler flags, but that's clearly not what we're looking for.


I would be looking primarily at the next point the word "error" comes up 
properly, which is here: 

from 
/var/tmp/portage/app-emulation/virtualbox-guest-additions-5.1.14/work/VirtualBox-5.1.14/src/VBox/Runtime/common/alloc/alloc.cpp:34:
/lib/modules/4.9.10-gentoo/build/arch/x86/include/asm/atomic.h: In function 
‘int atomic_read(const atomic_t*)’:
/lib/modules/4.9.10-gentoo/build/include/linux/compiler.h:305:42: error: 
uninitialized const member in ‘union atomic_read(const atomic_t*)::’
  union { typeof(x) __val; char __c[1]; } __u;   \


Interestingly, I see the mess of colour code brackets and numbers when I open 
the log you attached in TextEdit, vim or my Mac's Console.app logfile viewer.

If cat or sed them into the terminal (I noticed this adding the embedding 
spaces to the above) the colour codes are converted to colours and the text is 
displayed nicely.

In the above the filenames and the "‘union atomic_read(const 
atomic_t*)::’" are bold white, and the word "error:" is displayed in 
red.

Stroller.






Re: [gentoo-user] Need coaching with emerge failure logs (Understanting the problem)

2017-02-26 Thread Dale
Neil Bothwick wrote:
> On Sat, 25 Feb 2017 21:58:05 +0100, Miroslav Rovis wrote:
>
>> On 170225-09:19-0500, Harry Putnam wrote:
>>> Setup: VBox vm running gentoo(amd64) guest on a win-10 (64bit) host
>>>  Hardware: HP xw8600 - 2x Xeon  CPU X5450 @ 3.00GHz - 32 GB ram
>>>   
>>  [ some cca. 80k text cut here ]
>>
>> Go for the guides, in which you will find that sending 5.5M log in an
>> email is plain wrong.
> On this list, it is preferred to attach logs rather than post them
> elsewhere with a link. That way all the information stays together.
>
> However, as Stroller mentioned, the escape codes make a bit of a mess.
> Logs this large could be gzipped before attaching.
>
>

This is true.  I've ran into people doing that before elsewhere and the
place they put the logs would have deleted the files.  A lot of places
that allow you to post files, delete them after a while which means
anyone searching later can't even see what the problem was.  Given they
are usually free, who can blame them. 

Usually, I post the part at the end, making sure to get the "error 1"
part and a dozen or so prior lines.  If more is needed, then I can post
what is needed when asked. 

This list is different since we archive things pretty much forever. 
Heck, I even save my local storage of email for years here.  One never
knows what they may run into that searching the past helps. 

I wonder, why doesn't someone set up a wiki page that contains the way
Gentoo mailing lists work?  Maybe link to it from the page that lists
all the mailing lists and how to subscribe.  That would help people to
know how Gentoo does things, differently at least. 

Dale

:-)  :-) 



Re: [gentoo-user] Need coaching with emerge failure logs (Understanting the problem)

2017-02-26 Thread Neil Bothwick
On Sat, 25 Feb 2017 21:58:05 +0100, Miroslav Rovis wrote:

> On 170225-09:19-0500, Harry Putnam wrote:
> > Setup: VBox vm running gentoo(amd64) guest on a win-10 (64bit) host
> >  Hardware: HP xw8600 - 2x Xeon  CPU X5450 @ 3.00GHz - 32 GB ram
> >   
>  [ some cca. 80k text cut here ]
> 
> Go for the guides, in which you will find that sending 5.5M log in an
> email is plain wrong.

On this list, it is preferred to attach logs rather than post them
elsewhere with a link. That way all the information stays together.

However, as Stroller mentioned, the escape codes make a bit of a mess.
Logs this large could be gzipped before attaching.

> Read e.g. how to post bugs on Bugzilla. shouldn't be hard to find.

This wasn't a bug report but a request for help.


-- 
Neil Bothwick

Sarchasm : The gulf between the author of sarcastic wit and the person
who doesn't get it.


pgprfdaqGsn8x.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Need coaching with emerge failure logs (Understanting the problem)

2017-02-25 Thread Stroller

> On 25 Feb 2017, at 14:19, Harry Putnam  wrote:
> 
> I've attached a hefty log of some 4000 lines and hope someone will be
> patient enough to try to identify what is causing the problem. 

I took a look at this, but the broken colour codes throughout the log make it 
quite hard to read.

Example at the beginning:  [32;01m * 
Example from the end:   * 

Output to the terminal these would show the text in different colours, but the 
output was redirected to a textfile or mishandled in a copy-paste operation 
(not sure if screen or tmux does this?).

Running emerge with `--color n` would have made this log much more readable. 
Its size already makes it hard to search.

Stroller.


Re: [gentoo-user] Need coaching with emerge failure logs (Understanting the problem)

2017-02-25 Thread Miroslav Rovis
On 170225-09:19-0500, Harry Putnam wrote:
> Setup: VBox vm running gentoo(amd64) guest on a win-10 (64bit) host
>  Hardware: HP xw8600 - 2x Xeon  CPU X5450 @ 3.00GHz - 32 GB ram
> 
 [ some cca. 80k text cut here ]

Go for the guides, in which you will find that sending 5.5M log in an
email is plain wrong.

Read e.g. how to post bugs on Bugzilla. shouldn't be hard to find.

Regards!
-- 
Miroslav Rovis
Zagreb, Croatia
http://www.CroatiaFidelis.hr


signature.asc
Description: Digital signature