Git Mailing List Archive on lore.kernel.org
 help / color / Atom feed
* bug
@ 2020-06-26 21:11 Luke Knoble
  2020-06-29 18:08 ` [BUG] SSH permission error doing `git clone --recurse-submodules <SSH url>` (was: "bug") Philippe Blain
  0 siblings, 1 reply; 5+ messages in thread
From: Luke Knoble @ 2020-06-26 21:11 UTC (permalink / raw)
  To: git

Howdy,

I've found an issue in which I'm using this command:

git clone --recurse-submodules ssh://git@someurl:9999/someproject/repoX.git

git clones the repo successfully if I dont pass “git clone” any flags,
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

what gives git?

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [BUG] SSH permission error doing `git clone --recurse-submodules <SSH url>` (was: "bug")
  2020-06-26 21:11 bug Luke Knoble
@ 2020-06-29 18:08 ` Philippe Blain
  0 siblings, 0 replies; 5+ messages in thread
From: Philippe Blain @ 2020-06-29 18:08 UTC (permalink / raw)
  To: Luke Knoble; +Cc: git

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.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Bug
  2016-09-13 17:18 Bug Mike Hawes
  2016-09-13 17:26 ` Bug Santiago Torres
@ 2016-09-14 22:14 ` Dennis Kaarsemaker
  1 sibling, 0 replies; 5+ messages in thread
From: Dennis Kaarsemaker @ 2016-09-14 22:14 UTC (permalink / raw)
  To: Mike Hawes, git; +Cc: mh351681

On Tue, 2016-09-13 at 13:18 -0400, Mike Hawes wrote:
> To whom this may concern,
>
> I found a bug in git while trying to push my website.
> I redid the process and it happened again.
> I also tried it on another computer and it happened again.
> I was wondering how to claim a bug?

Hi Mike,

When you think git does not behave as you expect, please do not stop
your bug report with just "git does not work".  "I used git in this
way, but it did not work" is not much better, neither is "I used git
in this way, and X happend, which is broken".  It often is that git is
correct to cause X happen in such a case, and it is your expectation
that is broken. People would not know what other result Y you expected
to see instead of X, if you left it unsaid.

Please remember to always state

 - what you wanted to achieve;

 - what you did (the version of git and the command sequence to reproduce
   the behavior);

 - what you saw happen (X above);

 - what you expected to see (Y above); and

 - how the last two are different.

See http://www.chiark.greenend.org.uk/~sgtatham/bugs.html for further
hints.

(The above was shamelessly copied from the "A note from the maintainer" mails)

D.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: Bug
  2016-09-13 17:18 Bug Mike Hawes
@ 2016-09-13 17:26 ` Santiago Torres
  2016-09-14 22:14 ` Bug Dennis Kaarsemaker
  1 sibling, 0 replies; 5+ messages in thread
From: Santiago Torres @ 2016-09-13 17:26 UTC (permalink / raw)
  To: Mike Hawes; +Cc: git, mh351681

Hi, Michael.

It would be helpful to get more context on what triggered this bug. I'm
not a 'core' dev, so there may be a better way to send this. In general,
you want to state the following:

0) Information about your git installation, host system, etc.
1) Information about your repo (was it GitHub? local? self-hosted?)
2) What did you do? (git push origin master? git push?)
3) What happened instead of working? (the error message would be
   helpful.

Hope this helps.

Cheers!
-Santiago.

On Tue, Sep 13, 2016 at 01:18:52PM -0400, Mike Hawes wrote:
> To whom this may concern,
> 
> I found a bug in git while trying to push my website.
> 
> I redid the process and it happened again.
> 
> I also tried it on another computer and it happened again.
> 
> I was wondering how to claim a bug?
> 
> Thank you,
> 
> 
> Michael Hawes

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Bug
@ 2016-09-13 17:18 Mike Hawes
  2016-09-13 17:26 ` Bug Santiago Torres
  2016-09-14 22:14 ` Bug Dennis Kaarsemaker
  0 siblings, 2 replies; 5+ messages in thread
From: Mike Hawes @ 2016-09-13 17:18 UTC (permalink / raw)
  To: git; +Cc: mh351681

To whom this may concern,

I found a bug in git while trying to push my website.

I redid the process and it happened again.

I also tried it on another computer and it happened again.

I was wondering how to claim a bug?

Thank you,


Michael Hawes

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, back to index

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-26 21:11 bug Luke Knoble
2020-06-29 18:08 ` [BUG] SSH permission error doing `git clone --recurse-submodules <SSH url>` (was: "bug") Philippe Blain
  -- strict thread matches above, loose matches on Subject: below --
2016-09-13 17:18 Bug Mike Hawes
2016-09-13 17:26 ` Bug Santiago Torres
2016-09-14 22:14 ` Bug Dennis Kaarsemaker

Git Mailing List Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/git/0 git/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 git git/ https://lore.kernel.org/git \
		git@vger.kernel.org
	public-inbox-index git

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.git


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git