git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Reid Woodbury Jr." <reidw@rawsound.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>, git@vger.kernel.org
Subject: Re: git 2.3.4, ssh: Could not resolve hostname
Date: Thu, 2 Apr 2015 14:09:15 -0400	[thread overview]
Message-ID: <20150402180914.GA19081@peff.net> (raw)
In-Reply-To: <56B33978-76A0-4EE0-BCC0-EF030FD52E41@rawsound.com>

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

  reply	other threads:[~2015-04-02 18:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 17:18 git 2.3.4, ssh: Could not resolve hostname Reid Woodbury Jr.
2015-04-02 18:09 ` Jeff King [this message]
2015-04-02 18:58   ` Reid Woodbury Jr.
2015-04-02 19:14     ` Jeff King
2015-04-02 19:24       ` Junio C Hamano
2015-04-02 19:31         ` Reid Woodbury Jr.
2015-04-02 19:35           ` Jeff King
2015-04-02 20:06             ` Reid Woodbury Jr.
2015-04-02 20:15               ` Thomas Schneider
2015-04-03  0:02             ` Torsten Bögershausen
2015-04-03  1:30               ` brian m. carlson
2015-04-03 21:01               ` Junio C Hamano
2015-04-03 21:05                 ` Jeff King
2015-04-03 21:32               ` Kyle J. McKay
2015-04-04  0:19                 ` Reid Woodbury Jr.
2015-04-04  7:21                   ` Torsten Bögershausen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150402180914.GA19081@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=reidw@rawsound.com \
    --cc=tboegi@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).