git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris <chrisb.duck@gmail.com>
To: git@vger.kernel.org
Subject: bug report : 2.3.5  ssh repo not found
Date: Sat, 25 Apr 2015 06:57:28 +0100	[thread overview]
Message-ID: <553B2CC8.9020204@gmail.com> (raw)

Hello,

Using git version 2.3.5 with kernel 3.19.3-3-ARCH #1 SMP PREEMPT x86_64 
I see the following error message when pulling or cloning a repo over ssh:

"""
git clone ssh://user@mydomain:/home/user/path/to/project.git
Cloning into 'project'...
ssh: Could not resolve hostname mydomain:: Name or service not known
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
"""

Obviously I changed the url to hide credential info

After ensuring DNS was OK and being able to ssh to that instance 
directly I tried downgrading git to my distro's last installed version 
of git version 2.2.2 and now I can clone / pull / push to/from that repo 
without issue.

Is this a bug?

Best,
Chris

             reply	other threads:[~2015-04-25  5:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-25  5:57 Chris [this message]
2015-04-25  6:04 ` bug report : 2.3.5 ssh repo not found Bryan Turner
2015-04-25 21:34 ` 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=553B2CC8.9020204@gmail.com \
    --to=chrisb.duck@gmail.com \
    --cc=git@vger.kernel.org \
    /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).