Closing, insufficient info

Ok, I was finally able to resolve it with some "voodoo". (The file file is quite
small - about 2 mb, it's a windows DLL) First I pulled into some other repo (on
yet another local machine) and then was able to pull into my original target
from that intermediate one. I don't know why it worked this way. I checked
everything with "hg verify" and no problems were reported. After that
"operation" everything works fine.

Anyway, thanks for the info.

Regards,
Vlad

First off, Mercurial internally treats -everything- as binary. It only makes a
text/binary distinction when asked to diff files or display them in hgweb. So
whatever the problem is, it's not that.

A much more likely situation is that it's simply taking a long time to calculate
or send the delta ("binary" is often synonymous with "huge"). How big is the
file in question? On the Linux side you can use tcpdump or 'watch ifconfig
<interface>' or 'strace -p `pidof hg`' to see if it's still receiving data.

Hi guys,

I have problem pulling (hg pull/clone) binary files from a windows vista machine
into a linux (ubuntu) box. On the windows side I do "hg serve" and on the linux
side I do "hg --debug pull/clone http://windows-box-ip:8000/repo-name". Pull
info the same windows machine *via http* (i.e. with the above command) works
fine. Hg just starts the "adding changed files" phase and hangs on the first
binary met. I met the same problem with both 0.9.4 and 1.0 (both sides). It's
interesting that it worked when I previously pulled into windows box. In the web
browser I can see that hg correctly recognized he binary as such
(app/octet-stream). It's a OSS project repo, so if you need it I can provide
[parts of] it.

Regards,
Vlad