Re: "Repo Sync" FAILED: how to by-pass companies proxies ?

[Nikolay Dimitrov <picmaster@mail.bg>]

Hi Otavio,

On 04/03/2015 09:18 PM, Otavio Salvador wrote:
> Hello,
>
> On Fri, Apr 3, 2015 at 9:55 AM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>> On 04/03/2015 12:26 PM, 侯名 wrote:
>>>
>>> -----Original Message-----
>>> From: Nikolay Dimitrov [mailto:picmaster@mail.bg]
>>> Sent: Friday, April 03, 2015 11:41 AM
>>> To: Otavio Salvador; 侯名
>>> Cc: meta-freescale@yoctoproject.org
>>> Subject: Re: [meta-freescale] "Repo Sync" FAILED: how to by-pass companies
>>> proxies ?
>>>
>>> On 04/03/2015 06:08 AM, Otavio Salvador wrote:
>>>>
>>>> Hello Sir,
>>>>
>>>> On Thu, Apr 2, 2015 at 11:51 PM, 侯名 <houm@neusoft.com> wrote: ...
>>>>>
>>>>> My Company Proxy. Port 443/22. SSH is Blocked. So when I repo sync,
>>>>
>>>> ...
>>>>
>>>> Please take a look on following links, which might help:
>>>>
>>>> https://source.android.com/source/downloading.html#troubleshooting-net
>>>> work-issues
>>>>
>>>> http://elinux.org/Using_git_with_a_proxy
>>>>
>>>> It is a little tricky but should work.
>>>>
>>>> Best Wishes,
>>>
>>>
>>>> git config --global url."https://".insteadOf git://
>>>
>>>
>>>> Regards,
>>>> Nikolay
>>>
>>>
>>> [侯名] Thank you for your suggestion.
>>>                  I used your method, Configuring the proxy(user:password)
>>> and git(https instead of git).
>>>                  still does not work.
>>>                  And the error is the same as before.
>>
>>
>> Ahh, ok. I understood why it doesn't work. Here's a fixed manifest.xml,
>> which should work through your firewall:
>>
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <manifest>
>>
>>    <default sync-j="4" revision="master"/>
>>
>>    <remote fetch="https://git.yoctoproject.org/git" name="yocto"/>
>>    <remote fetch="https://github.com/Freescale" name="freescale"/>
>>    <remote fetch="https://github.com/openembedded" name="oe"/>
>>
>>    <project remote="yocto" revision="dizzy" name="poky" path="sources/poky"/>
>>    <project remote="yocto" revision="dizzy" name="meta-fsl-arm"
>> path="sources/meta-fsl-arm"/>
>>
>>    <project remote="oe" revision="dizzy" name="meta-openembedded"
>> path="sources/meta-openembedded"/>
>>
>>    <project remote="freescale" revision="dizzy" name="fsl-community-bsp-base"
>> path="sources/base">
>>          <copyfile dest="README" src="README"/>
>>          <copyfile dest="setup-environment" src="setup-environment"/>
>>    </project>
>>
>>    <project remote="freescale" revision="dizzy" name="meta-fsl-arm-extra"
>> path="sources/meta-fsl-arm-extra"/>
>>    <project remote="freescale" revision="dizzy" name="meta-fsl-demos"
>> path="sources/meta-fsl-demos"/>
>>    <project remote="freescale" revision="dizzy" name="Documentation"
>> path="sources/Documentation"/>
>>
>> </manifest>
>
> You could send a patch for dizzy and master changing to use https?
> this does not seem to offer any drawback AFAIK and would make
> community life eaiser ;)

The only drawback I see is the slightly increased initial repo sync
time (tested with dizzy):

git:  3m25.530s
http: 3m41.163s (+7.6%)

This seems like an acceptable trade-off. I'll send the patches.

Regards,
Nikolay