From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Luke Knoble <lupeknoble@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [BUG] SSH permission error doing `git clone --recurse-submodules <SSH url>` (was: "bug")
Date: Mon, 29 Jun 2020 14:08:37 -0400 [thread overview]
Message-ID: <114B6FFA-134F-4024-BB66-797B4367C5E4@gmail.com> (raw)
In-Reply-To: <CA+m5axz6QG5+AH5dB-J1dcD26z8z8uOUYUOgypu9kqoX49z0xA@mail.gmail.com>
Hi Luke,
> Le 26 juin 2020 à 17:11, Luke Knoble <lupeknoble@gmail.com> a écrit :
>
> Howdy,
>
> I've found an issue in which I'm using this command:
>
> git clone --recurse-submodules ssh://git@someurl:9999/someproject/repoX.git
Which version of Git ?
>
> git clones the repo successfully if I dont pass “git clone” any flags,
Does `git submodules update --init` then works ?
Can you share `.gitmodules` ? (is the submodules recorded with an HTTP
or SSH url in `.gitmodules` ?)
> but gives me this error when I use “--recurse-submodules” and git
> attempts to clone a single submodule:
>
> git@someurl: Permission denied (publickey).
> fatal: Could not read from remote repository.
> Please make sure you have the correct access rights
> and the repository exists.
> fatal: clone of
> 'ssh://git@someurl:9999/someproject/submodule_repo.git' into submodule
> path 'C:/someproject/submodule_repo' failed
>
> The obvious answer is that my permissions are bad, but I can clone the
> submodule repo directly without issue.. This command succeeds:
>
> git clone --recurse-submodules
> ssh://git@someurl:9999/someproject/submodule_repo.git
Interesting. Could you retry your commands, prefixing them with `GIT_TRACE2=1 GIT_SSH_COMMAND="ssh -vvv"` ?
Philippe.
prev parent reply other threads:[~2020-06-29 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 21:11 bug Luke Knoble
2020-06-29 18:08 ` Philippe Blain [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=114B6FFA-134F-4024-BB66-797B4367C5E4@gmail.com \
--to=levraiphilippeblain@gmail.com \
--cc=git@vger.kernel.org \
--cc=lupeknoble@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).