From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id A707DE0095D; Fri, 3 Apr 2015 23:37:51 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-HAM-Report: * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (picmaster[at]mail.bg) * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [193.201.172.118 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's * domain * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature Received: from mx2.mail.bg (mx2.mail.bg [193.201.172.118]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E31FDE00957 for ; Fri, 3 Apr 2015 23:37:46 -0700 (PDT) Received: from [192.168.0.62] (unknown [93.152.143.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx2.mail.bg (Postfix) with ESMTPSA id 411A16002AD3; Sat, 4 Apr 2015 09:37:44 +0300 (EEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mail.bg; s=default; t=1428129464; bh=XAMHtUqyJt10UXyxJNqJvPHwXE7kDPFuQ9VJRB5+Uhw=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=g0hTIj/1OpiOJxU6X0aGEqPW1uc+QSjVqJGfQWsGWXyVmumkcwnjrsWoNBGwf5whI 1kPomzarrzX1H3AbPSpSZCvd0vy8rrKHvH9IFJHuSi2nKzVLZHOgpoVUFOBXfJJp5W 9SSotPME8JIFlm4mpGAJGDpGWIHjgsQbZguBp8kw= Message-ID: <551F86B7.2040500@mail.bg> Date: Sat, 04 Apr 2015 09:37:43 +0300 From: Nikolay Dimitrov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: Otavio Salvador References: <000b01d06db9$16b45a00$441d0e00$@neusoft.com> <551E0BE4.2080305@mail.bg> <001b01d06df0$38509c50$a8f1d4f0$@neusoft.com> <551E8DD1.4050009@mail.bg> In-Reply-To: Cc: =?UTF-8?B?5L6v5ZCN?= , "meta-freescale@yoctoproject.org" Subject: Re: "Repo Sync" FAILED: how to by-pass companies proxies ? X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Apr 2015 06:37:51 -0000 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi Otavio, On 04/03/2015 09:18 PM, Otavio Salvador wrote: > Hello, > > On Fri, Apr 3, 2015 at 9:55 AM, Nikolay Dimitrov 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, 侯名 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: >> >> >> >> >> >> >> >> >> >> >> >> >> > path="sources/meta-fsl-arm"/> >> >> > path="sources/meta-openembedded"/> >> >> > path="sources/base"> >> >> >> >> >> > path="sources/meta-fsl-arm-extra"/> >> > path="sources/meta-fsl-demos"/> >> > path="sources/Documentation"/> >> >> > > 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