On Mon, Jul 23, 2012 at 2:02 PM, Tamas Selmeci <tselm...@open-st.eu> wrote:
> Hello all! > > First of all, congratulations for Fossil, this small version control > system has really amazed me. > > I've created a fossil repo (from one of my git repos) on my server and > wanted to clone it on my linux machine. The command > > fossil clone ssh://user@server://home/**fossil/repo.fossil repo.fossil > > doesn't do anything, but enters an endless wait state and produces a > barely ~56 KB file on the host machine. > > I observed that this command is running on the server: > > fossil test-http /home/fossil/repo.fossil > > A search in the mailing list arhive indicated to me that the problem may > rely somewhere in the SSH connection; I've also found a patch which > replaces 'test-http' with 'ssh-sync', but that also didn't solve my problem > (ssh-sync wasn't found on my computer). > > I'm running dropbear-2012.55 on the server, which is an ARM. Apart from > this, dropbear seems to work perfectly. > > How shall I go on? Does anybody have any suggestion? Switching to OpenSSH > is not necessarily an option, but I may give it a try. > > I got problem like this when my server was Linux (Debian Squeeze). By default it have some text in /etc/motd file. This contain a kind of welcome message at login and it seems to be used even on non-interactive session. I've just rename it and everything start to work. May be you have the same problem ? -- Martin G.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
