Andy Bradford: > This error would seem to indicate that your client sync code > doesn't actually know what the uvigot card is
Indeed, if I get it right from following the code paths, there are separate functions to handle synchronization for the client: http://www.fossil-scm.org/index.html/artifact/0d5ab26abb?txt=1&ln=1681-1689 and for the server: http://www.fossil-scm.org/index.html/artifact/0d5ab26abb?txt=1&ln=1127-1140 The client code is processing the "uvigot" card: http://www.fossil-scm.org/index.html/artifact/0d5ab26abb?txt=1&ln=2113-2183 The counterpart for the server handler is missing (that's where the "server says: bad command" message comes from), but that's probably intentional, as inferred from this comment: http://www.fossil-scm.org/index.html/artifact/0d5ab26abb?txt=1&ln=682-685 The `send_unversioned_file()' function should only generate "uvigot" cards on the server (that is, for the client), but the function is also called from the client sync code (generating "uvigot" cards for the server), without discrimination of client or server mode. I have rebuilt the Fossil client binary with an extra flag passed to this function to indicate whether "uvigot" cards are desired or not. The error message is gone, but unversioned files are not synchronized at all, that way. So I feel that the server should handle "uvigot" cards as well, and indicate the unversioned files that the client should transfer. Let's see if I dare diving any deeper ... ;-) --Florian _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
