[meta-freescale] Initial repo sync fails with "Unable to find..."

[Spriggs, Jim]

Hi again Guys,

I'm still not getting it, unfortunately.

Here's what I tried so far:

1) rm -rf .repo

2) repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b daisy
This succeeds without errors.

3) The network policy here disallows git-protocol, so I then fix up manifest.xml as recommended...

  <remote fetch="http://git.yoctoproject.org/git" name="yocto"/>
  <remote fetch="http://github.com/Freescale" name="freescale"/>
  <remote fetch="http://git.openembedded.org" name="oe"/>


4) repo --trace sync
This produced...

<snip - everything is good up to this point>

: export GIT_DIR=/home/jim/Projects/fsl-community-bsp/.repo/projects/sources/poky.git
: git pack-refs --all --prune 1>| 2>|
: scan refs /home/jim/Projects/fsl-community-bsp/.repo/projects/sources/poky.git
: load refs /home/jim/Projects/fsl-community-bsp/.repo/projects/sources/poky.git
: git symbolic-ref -m manifest set to daisy refs/remotes/m/daisy refs/remotes/yocto/daisy 1>| 2>|
error: Failed connect to git.openembedded.org:80; Connection timed out (curl_result = 7, http_code = 0, sha1 = 9691dfbb74adfbffe409e655d8ec25f0a874aa34)
error: Unable to find 1b6f02a6ee8a6608f8c4d57eafc8be72e4a83187 under http://git.openembedded.org/meta-openembedded
Cannot obtain needed blob 1b6f02a6ee8a6608f8c4d57eafc8be72e4a83187
while processing commit c734b14e2b900fe5172cc80185f0cf8b7734d0e8.
error: Fetch failed.

: export GIT_DIR=/home/jim/Projects/fsl-community-bsp/.repo/projects/sources/meta-openembedded.git
: git fetch oe --tags +refs/heads/*:refs/remotes/oe/*
error: Unable to find 39eb975b87333845f7a90802c299b4923d6f78ae under http://git.openembedded.org/meta-openembedded
Cannot obtain needed tree 39eb975b87333845f7a90802c299b4923d6f78ae
while processing commit 9be6cf51519158caa5d63ec1538e5c6946ca86c5.
error: Fetch failed.
: load refs /home/jim/Projects/fsl-community-bsp/.repo/projects/sources/meta-openembedded.git
: git pack-refs --all --prune 1>| 2>|
error: Cannot fetch meta-openembedded

error: Exited sync due to fetch errors

--------------------------

So I guess the problem is actually the "Connection timed out", of which the "Unable to find" is merely a further symptom.
Given that I can, apparently, access the other servers just fine, what's so special about the git.openembedded.org server?

Thanks for any other clues!

--
jim


-----Ursprüngliche Nachricht-----
Von: otavio.salvador at gmail.com [mailto:otavio.salvador at gmail.com] Im Auftrag von Otavio Salvador
Gesendet: Samstag, 11. Oktober 2014 20:13
An: Philip Balister
Cc: Spriggs, Jim; meta-freescale at yoctoproject.org
Betreff: Re: [meta-freescale] Initial repo sync fails with "Unable to find..."

On Sat, Oct 11, 2014 at 2:14 PM, Philip Balister <philip at balister.org> wrote:
> I jsut updated a git checkout with that remote for meta-openmebedded
> and can see that hash.

I also confirmed it worked fine.

Jim, is it possible to test it again?

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

________________________________

RAYLASE AG
Argelsrieder Feld 2+4
82234 Wessling
Germany
Tel.: +49-(0)8153/88 98-0
Fax: +49-(0)8153/88 98-10
http://www.raylase.de

District Court Munich, HRB 131450

Board: Peter von Jan (CEO)

Supervisory Board: Dr. Ulrich Lohmann (Chairman)


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.