Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Jacek Cała
As stated in the original question 'ssh SERVERNAME' works fine, which means 'ping SERVERNAME' can also resolve the name ok. 2015-06-17 13:44 GMT+01:00 Stephan Beal sgb...@googlemail.com: On Tue, Jun 16, 2015 at 5:44 PM, Jacek Cała jacek.c...@gmail.com wrote: works perfectly fine. It's not

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Stephan Beal
On Tue, Jun 16, 2015 at 5:44 PM, Jacek Cała jacek.c...@gmail.com wrote: works perfectly fine. It's not urgent for me because I can work using IP but I'd appreciate any hints how it may be solved. Try: ping SERVERNAME If that results in the same error then the problem is your DNS config or

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread bch
You're ignoring that ssh has extensive configuration options and could be configured to use an alias. Stephan is probably trying to get a more definitive test to help. On Jun 17, 2015 6:06 AM, Jacek Cała jacek.c...@gmail.com wrote: As stated in the original question 'ssh SERVERNAME' works fine,

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread jungle Boogie
On 17 June 2015 at 06:06, Jacek Cała jacek.c...@gmail.com wrote: As stated in the original question 'ssh SERVERNAME' works fine, which means 'ping SERVERNAME' can also resolve the name ok. Paste your /etc/resolve.conf file Are ssh servername and clone server name the same? -- --- inum:

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Stephan Beal
On Wed, Jun 17, 2015 at 3:15 PM, bch brad.har...@gmail.com wrote: You're ignoring that ssh has extensive configuration options and could be configured to use an alias. Stephan is probably trying to get a more definitive test to help. LOL! Yeah, what Brad said ;). Plus... i did skip over the

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Jan Nijtmans
2015-06-17 15:56 GMT+02:00 Jacek Cała jacek.c...@gmail.com: Hi, Please find below some details about the software running in my container: - fossil version -v says: This is fossil version 1.33 [9c65b5432e] 2015-05-23 11:11:31 UTC Compiled on Jun 10 2015 22:28:08 using gcc-4.6.3 (32-bit)

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Jacek Cała
Hi, Please find below some details about the software running in my container: - fossil version -v says: This is fossil version 1.33 [9c65b5432e] 2015-05-23 11:11:31 UTC Compiled on Jun 10 2015 22:28:08 using gcc-4.6.3 (32-bit) SQLite 3.8.10.2 2015-05-20 18:17:19 2ef4f3a5b1 Schema version

Re: [fossil-users] Issue with cloning a repo

2015-06-17 Thread Jacek Cała
Thank you Jan for clarifying the problem. BTW, perhaps that's a reason why on the download page there could also be a linux-x64 version available. Cheers, Jacek 2015-06-17 15:17 GMT+01:00 Jan Nijtmans jan.nijtm...@gmail.com: 2015-06-17 15:56 GMT+02:00 Jacek Cała jacek.c...@gmail.com:

[fossil-users] Issue with cloning a repo

2015-06-16 Thread Jacek Cała
Hi, I'm running fossil 1.33 in a docker container and found an issue when cloning my repo. If I run it like: $ fossil clone http://USERNAME@SERVERNAME/REPONAME repo.fossil it fails reporting: getaddrinfo() fails: Name or service not known Clone done, sent: 0 received: 0 ip: server returned

Re: [fossil-users] Issue with cloning a repo

2015-06-16 Thread Andy Bradford
Thus said =?UTF-8?Q?Jacek_Ca=C5=82a?= on Tue, 16 Jun 2015 16:44:42 +0100: $ fossil clone http://USERNAME@SERVERNAME/REPONAME repo.fossil it fails reporting: getaddrinfo() fails: Name or service not known Mind sharing the actual hostname for SERVERNAME? It's possible there's some kind