Bug: [hostname:port]:repo.git notation no longer works (for ssh)

I've just upgraded to Debian testing (jessie), and with that I got a
brand new (for me) git version:

    $ git --version
    git version 1.8.4.rc3

Some of my repos I use an ssh tunnel to reach, so when I want to reach a
repo forwarded to local port 2223, using the ssh protocol, the following
used to work (.git/config) in older git versions:

    [remote "exp"]
            url = [localhost:2223]:blink.git
            fetch = +refs/heads/*:refs/remotes/exp/*

However, now I get this message:

    $ git fetch exp
    fatal: ':blink.git' does not appear to be a git repository
    fatal: Could not read from remote repository.

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

If I don't go via the ssh tunnel (I finally have some VPN stuff these
days, so I don't really need the tunnel thing anymore, but that's going
to be a lot of remotes to update, so I'd prefer it just worked like it
used to):

-            url = [localhost:2223]:blink.git
+            url = git:blink.git

... it works fine.

-- 
---- Morten Stenshorne, developer, Opera Software ASA ----
------------------ http://www.opera.com/ -----------------

On Fri, Sep 27, 2013 at 3:07 PM, Morten Stenshorne [off-list ref] wrote:

I've just upgraded to Debian testing (jessie), and with that I got a
brand new (for me) git version:

    $ git --version
    git version 1.8.4.rc3

Some of my repos I use an ssh tunnel to reach, so when I want to reach a
repo forwarded to local port 2223, using the ssh protocol, the following
used to work (.git/config) in older git versions:

    [remote "exp"]
            url = [localhost:2223]:blink.git
            fetch = +refs/heads/*:refs/remotes/exp/*

However, now I get this message:

    $ git fetch exp
    fatal: ':blink.git' does not appear to be a git repository
    fatal: Could not read from remote repository.

Ugh.. bisect pointed to my commit 6000334 (clone: allow cloning local
paths with colons in them - 2013-05-04). Will have a closer look
tonight.
-- 
Duy

Am 27.09.2013 10:07, schrieb Morten Stenshorne:

I've just upgraded to Debian testing (jessie), and with that I got a
brand new (for me) git version:

    $ git --version
    git version 1.8.4.rc3

Some of my repos I use an ssh tunnel to reach, so when I want to reach a
repo forwarded to local port 2223, using the ssh protocol, the following
used to work (.git/config) in older git versions:

    [remote "exp"]
            url = [localhost:2223]:blink.git
            fetch = +refs/heads/*:refs/remotes/exp/*

However, now I get this message:

    $ git fetch exp
    fatal: ':blink.git' does not appear to be a git repository
    fatal: Could not read from remote repository.

I wonder why that worked (especially the "[...]") at all ?
I thought specifying a port for a SSH connection was always only
possible when using

       ssh://user@host:port/path/to/repo.git
- or -
       ssh://user@host:port/~user/path/to/repo.git

At least that's what I always read out of the git-clone man page.

Stefan
-- 
----------------------------------------------------------------
/dev/random says: Don't ask me, I have random access memory.
python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"

On Fri, Sep 27, 2013 at 3:55 PM, Stefan Näwe
[off-list ref] wrote:

quoted

    [remote "exp"]
            url = [localhost:2223]:blink.git
            fetch = +refs/heads/*:refs/remotes/exp/*

However, now I get this message:

    $ git fetch exp
    fatal: ':blink.git' does not appear to be a git repository
    fatal: Could not read from remote repository.

I wonder why that worked (especially the "[...]") at all ?
I thought specifying a port for a SSH connection was always only
possible when using

       ssh://user@host:port/path/to/repo.git
- or -
       ssh://user@host:port/~user/path/to/repo.git

At least that's what I always read out of the git-clone man page.

[] is used to wrap ipv6 and because we don't know if it's actually
ipv6 or v4, we accept it in both cases, so [abc] can be used in place
"host" above. No [host:port]:path won't work because "host:port" is
considered host name. But [host or ip]:path may work (that is after I
fix my bug).
-- 
Duy

On Fri, Sep 27, 2013 at 4:07 AM, Morten Stenshorne [off-list ref] wrote:

If I don't go via the ssh tunnel (I finally have some VPN stuff these
days, so I don't really need the tunnel thing anymore, but that's going
to be a lot of remotes to update, so I'd prefer it just worked like it
used to):

-            url = [localhost:2223]:blink.git
+            url = git:blink.git

... it works fine.

Until you get a proper fix, I wonder if this will help:

  git config --global --add url."git:".insteadOf  "[localhost:2223]:"

See "git help config" for details on the insteadOf config setting.

Phil