On Thu, 17 Oct 2013 06:01:51 +0200, Andy Bradford
<[email protected]> wrote:
Thus said Stephan Beal on Tue, 15 Oct 2013 19:08:30 +0200:
[stephan@host:~/cvs/fossil/fossil/src]$ grep 'server does not respond'
*.*
The actual error is:
Accept certificate for host fossil (a=always/y/N)? y
server did not reply
$ grep 'server did not reply' *.*
http.c: fossil_fatal("server did not reply");
To cause this error message I just killed the remote fossil process that
was running before answering y.
I suspect that something like a dropped connection may have been the
cause of this, but it's hard to say without more details (and
reproducibility).
I'm sorry, I don't have any of these details right now. I propose to ask
my colleague to try to reproduce the error. I might take a bit of time,
though. is this of interest?
for the record, what I do now is:
-- the problem occurred during the initial clone attempt of an essentially
empty new repo (might have been 100kB)
-- if this makes a difference: it was a "cgi-served" repo and https
-- yes, there is a firewall involved
I've thought about a possible time-out problem but I would presume he (the
colleague in the US) did just follow the provided recipe (he has no
previous experience with fossil) step by step ("type fossil clone
https:username@server repo.fossil and provide password"...) and it seems
quite unlikely that he walked away for coffee at that point w/o answering
the question).
Andy
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
