On 18 June 2013 11:06, Michai Ramakers <[email protected]> wrote: > > For the time being I will park the faulty/suspect repo somewhere, and > create a new repo to work on.
Ok, did that - created new repo from scratch and added files, then tried cloning with new fossil-version on both server- and client-side. Oddly enough I see the similar behaviour as the original issue. I tried to isolate it a bit; there seem to be 2 files (a .zip and an .exe) that, when added to a clean repo, each cause cloning of that repo to fail; only when both are omitted does cloning on my win32 box succeed. A clean archive with either one of these files (in their original dir-structure, but omitting all other files) would cause failure. A repo with both files is available at http://83.117.36.67 SHA1/size of both: michai@lime:/tmp/binsearch/f$ sha1 * SHA1 (JN-AN-1110_JenNet-IP-Border-Router-BR_1v6v1.zip) = 2cec006763915be86cc3730481e1b703c0553526 SHA1 (JN-SW-4041-SDK-Toolchain-v1.1.exe) = 93979b198b794a26456ad8069404b8cfe8949bb6 michai@lime:/tmp/binsearch/f$ ls -l * -rw-r--r-- 1 michai wheel 102068822 Jun 12 10:51 JN-AN-1110_JenNet-IP-Border-Router-BR_1v6v1.zip -rw-r--r-- 1 michai wheel 156939992 Jun 11 22:40 JN-SW-4041-SDK-Toolchain-v1.1.exe (I am running 'f server' from within the source tree - running a server like this or with repo-file as argument doesn't seem to matter.) Hope this helps (and reproduces at all) in debugging. Michai _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
