Re: [eclipsedarcs-develop] darcs get failure from eclipsedarcs repo
Status: Alpha
Brought to you by:
radoslawg
|
From: Kauker, H. <Hub...@tr...> - 2007-03-16 08:21:06
|
Leif, for the record only: when that 404 message came, nothing was killed or interrupted. And indeed, I am on Windows. Must be one of those "rough" edges. Just an idea: --exact-version might produce a readable OS identifier, too? Hubert Also simple "darcs get" went past patch 37 this morning. Killed it myself at patch 100 or so, since my patience was up. Anyway, a rather strange message: libcurl: HTTP error (404?). What puzzles me is the question mark. Obviously libcurl or some other module higher up was doing some guesswork. Under normal conditions a 404 error and a timeout, say, should be easy to tell apart. Right? Indeed. I'd have to speculate what happens here. I would guess, from the message, that it comes from libcurl. But as you said, libcurl should be able to be more specific. So either the message comes actually from the code that calls it (called it, was interrupted by the kill, didn't know what the problem was, and wrote that message as if on behalf of libcurl), or (assuming you're on Windows) this has to do with the version of libcurl that was linked in (cygwin?, ...). Generally, Darcs seems to have a few rough edges on Windows, there are several things that don't really run smoothly. |