• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 375 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM3517: Git clone failing when using git://

Jeroen van Emden
Prodigy 10 points
Part Number: AM3517


Tool/software:

Unable to clone via git://. Cloning via https is working. Is something blocking it at the TI side?

13:03 $ git clone git://git.ti.com/ti-u-boot/ti-u-boot.git
Cloning into 'ti-u-boot'...
fatal: unable to connect to git.ti.com:
git.ti.com[0: 198.47.28.208]: errno=Connection refused

The following is working:

13:14 $ git clone https://git.ti.com/git/ti-u-boot/ti-u-boot.git
Cloning into 'ti-u-boot'...
remote: Enumerating objects: 1115504, done.
remote: Counting objects: 100% (1537/1537), done.
remote: Compressing objects: 100% (744/744), done.


But we cannot change to it as it comes with the Yocto build in the meta-ti package.

  • 0
    TI__Guru 70272 points
    Jeroen van Emden said:
    Unable to clone via git://. Cloning via https is working. Is something blocking it at the TI side?

    Many internet servers including the TI git server have stopped supporting the "Git Transport" protocol a year or two ago, so the errors you are seeing building some older Yocto recipes are expected and nothing unique to TI. The solution is to start using the "HTTPS Transport" for Git instead, just like you have already figured out how to do it manually. As for Yocto, you need to update the respective Bitbake recipes with the new URL/transport for this to work, there's no way around that. Look at newer recipes in `meta-ti` if you need inspiration what exact URL/syntax to use. There's also numerous E2E threads on this topic here you can try searching for.

    Regards, Andreas