> Out of curiosity: is there a proxy between them? A caching proxy > server "might" explain this behaviour (in which case i think there's > a workaround).
No proxy involved. The three machines are sitting on my desk. As a side note, the server is a raspberry PI and it does a great job at hosting fossil repo ! > I have seen this issue a few times and this was with using file:// for > the transport to the "server". I've fixed it by doing a checkout to > another branch and back. If I recall correctly a checkout to the current > branch was not enough but I'm not sure. I'm using https transport layer (lighty web server handles the SSL part, the fossil CGI interface is used). The three machines are clock sync with NTP. The only clue for you I have is that a rebuild on the server did the trick. I'm no sure what "fossil rebuild" does though... _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
