{"thread":{"id":"39157","subject":"bug report : 2.3.5 ssh repo not found","startedAt":"2015-04-25T05:57:28Z","lastAt":"2015-04-25T21:34:45Z","messageCount":3,"participants":["Chris","Bryan Turner","Torsten Bögershausen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"259982","messageId":"553B2CC8.9020204@gmail.com","threadId":"39157","inReplyTo":null,"subject":"bug report : 2.3.5 ssh repo not found","fromName":"Chris","fromEmail":"chrisb.duck@gmail.com","sentAt":"2015-04-25T05:57:28Z","receivedAt":"2015-04-25T05:57:28Z","isPatch":false,"sender":{"key":"chrisb.duck@gmail.com","avatar":null},"body":"Hello,\n\nUsing git version 2.3.5 with kernel 3.19.3-3-ARCH #1 SMP PREEMPT x86_64 \nI see the following error message when pulling or cloning a repo over ssh:\n\n\"\"\"\ngit clone ssh://user@mydomain:/home/user/path/to/project.git\nCloning into 'project'...\nssh: Could not resolve hostname mydomain:: Name or service not known\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n\"\"\"\n\nObviously I changed the url to hide credential info\n\nAfter ensuring DNS was OK and being able to ssh to that instance \ndirectly I tried downgrading git to my distro's last installed version \nof git version 2.2.2 and now I can clone / pull / push to/from that repo \nwithout issue.\n\nIs this a bug?\n\nBest,\nChris\n"},{"id":"259983","messageId":"CAGyf7-FVf4Pf90eaRnfNwC1JJV7ANkSGLONJZaF=eKRadnhqQA@mail.gmail.com","threadId":"39157","inReplyTo":"553B2CC8.9020204@gmail.com","subject":"Re: bug report : 2.3.5 ssh repo not found","fromName":"Bryan Turner","fromEmail":"bturner@atlassian.com","sentAt":"2015-04-25T06:04:34Z","receivedAt":"2015-04-25T06:04:34Z","isPatch":false,"sender":{"key":"bturner@atlassian.com","avatar":"https://gravatar.com/avatar/16bcf3167981c1ef7c804e502642366d888a35b0d0b0a4ca01fdc442aa1acb1e?d=mp&s=160"},"body":"On Sat, Apr 25, 2015 at 3:57 PM, Chris <chrisb.duck@gmail.com> wrote:\n> Hello,\n>\n> Using git version 2.3.5 with kernel 3.19.3-3-ARCH #1 SMP PREEMPT x86_64 I\n> see the following error message when pulling or cloning a repo over ssh:\n>\n> \"\"\"\n> git clone ssh://user@mydomain:/home/user/path/to/project.git\n> Cloning into 'project'...\n> ssh: Could not resolve hostname mydomain:: Name or service not known\n> fatal: Could not read from remote repository.\n>\n> Please make sure you have the correct access rights\n> and the repository exists.\n> \"\"\"\n\nI believe that's [1]\n\nRemove the : between the domain and the path and it should work, per\nJeff King [2]\n\n[1] http://thread.gmane.org/gmane.comp.version-control.git/266649\n[2] http://article.gmane.org/gmane.comp.version-control.git/266659\n\n>\n> Obviously I changed the url to hide credential info\n>\n> After ensuring DNS was OK and being able to ssh to that instance directly I\n> tried downgrading git to my distro's last installed version of git version\n> 2.2.2 and now I can clone / pull / push to/from that repo without issue.\n>\n> Is this a bug?\n>\n> Best,\n> Chris\n>\n>\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n"},{"id":"260006","messageId":"553C0875.3090706@web.de","threadId":"39157","inReplyTo":"553B2CC8.9020204@gmail.com","subject":"Re: bug report : 2.3.5 ssh repo not found","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2015-04-25T21:34:45Z","receivedAt":"2015-04-25T21:34:45Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On 2015-04-25 07.57, Chris wrote:\n> Hello,\n> \n> 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:\n> \n> \"\"\"\n> git clone ssh://user@mydomain:/home/user/path/to/project.git\n> Cloning into 'project'...\n> ssh: Could not resolve hostname mydomain:: Name or service not known\n> fatal: Could not read from remote repository.\n> \n> Please make sure you have the correct access rights\n> and the repository exists.\n> \"\"\"\n> \n> Obviously I changed the url to hide credential info\n> \n> 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.\n> \n> Is this a bug?\n> \n> Best,\n> Chris\n\nIt's a know issue/bug, sorry for the inconvenience.\n\nThere are 2 options:\nEither:\n\nchange the URL\ngit clone ssh://user@mydomain:/home/user/path/to/project.git\ninto\ngit clone ssh://user@mydomain/home/user/path/to/project.git\n\n(In other words, remove the ':' after the hostname)\n\n\nOr\nCompile Git yourself from the latest git.git/master, which has this fix:\n\ncommit 9718c7c0c2a92585729d0f2e05ebf2c44b0cc56a\nMerge: a59ac46 6b6c5f7\nAuthor: Junio C Hamano <gitster@pobox.com>\nDate:   Mon Apr 20 15:28:33 2015 -0700\n\n    Merge branch 'tb/connect-ipv6-parse-fix'\n    \n    An earlier update to the parser that disects an address broke an\n    address, followed by a colon, followed by an empty string (instead\n    of the port number).\n    \n    * tb/connect-ipv6-parse-fix:\n      connect.c: ignore extra colon after hostname\n"}]}