Re: git 2.3.4, ssh: Could not resolve hostname

From: Reid Woodbury Jr. <reidw@rawsound.com>
Date: Apr 2, 2015, 18:58 UTC
Message-ID: <201C57EF-FC96-4FFB-81D2-90F94428A6CA@rawsound.com>
In-Reply-To: <20150402180914.GA19081@peff.net>

Peff The colons were part of the output. The 'xxxx' replaces the domain in the response. The domain is an internal one that my client would rather keep private. But this got me to think that this might be an important detail: I am using GIT from a remote node on a Cisco AnyConnect VPN with DNS served by ActiveDirectory. Reid

Show 21 quoted lines

> On Apr 2, 2015, at 11:09 AM, Jeff King <peff@peff.net> wrote:
> 
> On Thu, Apr 02, 2015 at 10:18:33AM -0700, Reid Woodbury Jr. wrote:
> 
>> After upgrading from GIT 2.3.3 to 2.3.4 (on Mac OS X 10.10.2,
>> installed with MacPorts) I received this error message when doing a
>> push:
>> 
>> $ git push
>> ssh: Could not resolve hostname xxxx:: nodename nor servname provided, or not known
>> fatal: Could not read from remote repository.
> 
> It is hard to tell from the obfuscated output, but perhaps the problem
> is the two colons (i.e., git is feeding a hostname like "foo:" when it
> should be just "foo"). There were some changes in v2.3.4 related to
> parsing ssh URLs. +cc Torsten, who worked on that code.
> 
> Can you show us your git config (presumably the host is defined in
> remote.origin.url in .git/config of the repository)?
> 
> -Peff