Hi ,

Thanks for your prompt reply.

Actually I am able to create my own SRC_URI on your guided lines as
#SRC_URI = 
"git://ep-code.xyz.com/sysconfig;branch=xxx-ep-20130823-3.0-alpha;protocol=ssh"
But when do_fetch task starts executing it prompts me to input the passphrase 
for the same server when I am not able to pass . Please suggest me is the way I 
mentioned the path is need to be modified or

There is something that enable me to pass password for git server ie username 
and password are possible to be passed as argument to git path or some other 
way exist to give input to bitbake do_fetch task as runtime I don't think we 
can pass any input.

Please suggest me the way.

Regards,
Rohit Jindal

From: Nicolas Dechesne [mailto:[email protected]]
Sent: Monday, September 09, 2013 6:15 PM
To: Rohit2 Jindal
Cc: [email protected]
Subject: Re: [yocto] yocto query on SR_URI creation


On Mon, Sep 9, 2013 at 9:47 AM, Rohit2 Jindal 
<[email protected]<mailto:[email protected]>> wrote:
Actually I want to access external git server of our client using yocto 
SRC_URI. But I am not able to create path to git server .


I just have following info of external server with me

1)~/.ssh/config file

host xyz
user epuser
hostname ep-code.xyz.com<http://ep-code.xyz.com>
port 22
identityfile ~/.ssh/abc_r.j


2)abc_r.j.pub file
3)abc_r.j file

I am not able to understand which URI protocols will work for me to set path in 
SRC_URI of .bb file


Same thing on linux prompt works like this
$git clone xyz:sysconfig



$buildroot>make git-checkout
Available tag used is xxx-ep-20130823-3.0-alpha
Available server [email protected]:/<mailto:[email protected]:/>


The following should work:

SRC_URI = 
"git://foo.xyz.com/folder/project.git;protocol=ssh<http://foo.xyz.com/folder/project.git;protocol=ssh>"

And in ~/.ssh/config

Host foo.xyz.com<http://foo.xyz.com>
  User <your username>
  IdentityFile ~/.ssh/abc_r.j

You would need to ssh once to that server outside of OE so that i records the 
server in ~/.ssh/known_hosts first.





===============================================================================
Please refer to http://www.aricent.com/legal/email_disclaimer.html
for important disclosures regarding this electronic communication.
===============================================================================
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to