Bug 485784 – dev-lang/python-2.7.5-r2: error message not caught

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Toralf Förster 2013-09-23 20:40:57 UTC]

WHile upgrading a x86 within a chrooted env I got :

>>> Emerging (19 of 29) dev-lang/python-2.7.5-r2
>>> Jobs: 18 of 29 complete, 1 running              Load avg: 6.68, 6.62, 6.37ssh_exchange_identification: read: Connection timed out

during test phase.
I think even that error msg should be catched by emerge ?

(so probably rather a sandbox/emerge issue than pythin related ?)

[Comment 1 Jeroen Roovers (RETIRED) 2013-09-25 15:07:41 UTC]

ssh_exchange_identification: read: Connection timed out

Why would an ebuild be calling that? It might as well be something else backgrounded in that shell.

[Comment 2 Toralf Förster 2013-09-25 18:07:16 UTC]

(In reply to Jeroen Roovers from comment #1)
> ssh_exchange_identification: read: Connection timed out
> 
> Why would an ebuild be calling that? It might as well be something else
> backgrounded in that shell.

Hhm - I chrooted into that x86 UML image - I did not started the user mode linux image and logged in via ssh to upgrade it (which would be a night mare due to the big overhead). So /me wonders which other process should send that message.

[Comment 3 Jeroen Roovers (RETIRED) 2013-09-27 16:23:46 UTC]

I'm pretty sure it was something in that shell that had nothing to do with what emerge was doing at the time.