My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 546: repo doesn't consider port in ~/.ssh/config
1 person starred this issue and may be notified of changes. Back to list
Status:  Invalid
Owner:  ----
Closed:  Apr 2010


Sign in to add a comment
 
Project Member Reported by fredrik....@sonyericsson.com, Apr 26, 2010
Affected Version: 1.6.8, at least.

What steps will reproduce the problem?
1. Enter an alias into ~/.ssh/config that configures the port to the 
gerrit ssh port, 29418
2. according to https://review.source.android.com/#change,9655 , unless a 
port is specified in the immediate URL, the port is set to port 22. This 
collides with the ssh/config setting, and seem to override it.
3. Run any repo command, repo init, repo sync and you will get a lot of 
password questions that go by in your output. You don't have to enter a 
password, it seems repo won't specify the port in every call. It is 
however annoying and confusing to see the password prompt during the sync 
operation.

> What is the expected output? What do you see instead?
I expect no password prompt like when the port is in the URL. :-)

> Please provide any additional information below.
Well, a new way to avoid the original python error when the port is empty 
needs to be figured out. But I haven't given that any thoughts at all.

This is obviosuly not very high prio either, it is not a fatal problem. 
But I do nkow of several users who have reported this problem.
Apr 26, 2010
Project Member #1 fredrik....@sonyericsson.com
Actually, this is probably true for any ssh config, even if it's system global. So, 
not only your personal config, but any others in your path too.
Apr 26, 2010
#2 sop@google.com
Wrong project.  repo bugs should go into its own issue
tracker at https://code.google.com/p/git-repo/

Please move the issue there.  Sorry, you have to do it
by copy-and-paste.  :-(
Status: Invalid
Apr 26, 2010
Project Member #3 fredrik....@sonyericsson.com
No worries, I took a chance and looked for https://code.google.com/p/repo/ However, I 
didn't have any luck with that, so I took a chance, hehe.

It's now reported on the correct project-URL!

https://code.google.com/p/git-repo/issues/detail?id=64
Sign in to add a comment

Powered by Google Project Hosting