On Fri, Sep 28, 2007 at 11:32:34PM -0700, Zack Weinberg wrote:
So - monotone isn't actually doing anything wrong, this is a bug in
netxx. Is there any hope of getting it fixed upstream? I do not
relish the thought of auditing the two-dozen or so places where netxx
throws exceptions and
On 9/28/07, Zack Weinberg [EMAIL PROTECTED] wrote:
I don't speak German, but I suspected that Die Wartezeit für die
Verbindung ist abgelaufen was a kernel failure message, so I looked
it up in glibc's message translations, and indeed: it means
Connection timed out in English. This is a normal
Zack Weinberg [EMAIL PROTECTED] writes:
Tangentially, the chain of foo error: strings that get tacked on the
beginning of the actual error message is getting kind of absurd here,
doncha think? --
mtn: Fataler Fehler: std::runtime_error: Netzwerk-Fehler: recv failure:
(with precisely half
Here a bug message
- Pull org.openembedded.dev (over night)
- console output (morning)
finde Elemente zum Synchronisieren:
mtn: Bytes rein | Bytes raus | Zertifikate rein | Revisionen rein
mtn:105,1 M |505 |72.601/72.601 | 18.140/18.140
mtn: Fataler Fehler: std::runtime_error:
On 9/28/07, Werner Schulte [EMAIL PROTECTED] wrote:
- Pull org.openembedded.dev (over night)
- console output (morning)
finde Elemente zum Synchronisieren:
mtn: Bytes rein | Bytes raus | Zertifikate rein | Revisionen rein
mtn:105,1 M |505 |72.601/72.601 | 18.140/18.140
