| Summary: | dev-lang/python-2.7.5-r2: error message not caught | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
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. (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. I'm pretty sure it was something in that shell that had nothing to do with what emerge was doing at the time. |
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 ?)