On Wed, Mar 25, 2015 at 12:47:30PM +0100, Christian Hesse wrote: > Magnus Therning <mag...@therning.org> on Wed, 2015/03/25 12:36: > > I thought I'd ask here before raising a ticket. > > > > Is anyone else seeing this behaviour with git 2.3.4-1: > > > > ~~~ > > [I] % git fetch > > ssh: Could not resolve hostname build01:: 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. > > ~~~ > > > > Downgrading to 2.3.3-1 "solves" it. > > What does the URL look like? You can get it for origin with: > > % git remote show origin > > I suppose you use a non-standard ssh port (or specified it nevertheless) with > host:port, no? man git-clone tells us to use something like: > > ssh://[user@]host.xz[:port]/path/to/repo.git/
It looks like this:
ssh://build01.evidente.local:/home/husqvarna/git/evi-cst.git
Nothing non-standard about that and it has worked fine with every
version of git I've used the last 6 months or so, until the upgrade to
2.3.4... I really don't expect the format of remotes to change when
going from 2.3.3 to 2.3.4!
/M
--
Magnus Therning OpenPGP: 0xAB4DFBA4
email: mag...@therning.org jabber: mag...@therning.org
twitter: magthe http://therning.org/magnus
There's a big difference between making something easy to use and
making it productive.
-- Adam Bosworth
pgpEyo8ZKzwT3.pgp
Description: PGP signature
