From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail5.wrs.com (mail5.windriver.com [192.103.53.11]) by mail.openembedded.org (Postfix) with ESMTP id AED027C6AF for ; Fri, 22 Feb 2019 08:19:15 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail5.wrs.com (8.15.2/8.15.2) with ESMTPS id x1M8ISLH029393 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Feb 2019 00:18:49 -0800 Received: from localhost.localdomain (128.224.162.215) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.3.435.0; Fri, 22 Feb 2019 00:18:30 -0800 To: Richard Purdie , References: <1550815380-192596-1-git-send-email-haitao.liu@windriver.com> <939bc06d030a91fc7f2376171997fdd010124b5d.camel@linuxfoundation.org> From: Haitaoliu Message-ID: Date: Fri, 22 Feb 2019 16:15:54 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: <939bc06d030a91fc7f2376171997fdd010124b5d.camel@linuxfoundation.org> X-Originating-IP: [128.224.162.215] Subject: Re: [PATCH] bitbake.conf:update FETCHCMD_wget with --no-passive-ftp X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2019 08:19:15 -0000 Content-Type: multipart/alternative; boundary="------------F44D801B8FA93C1E83C75A35" Content-Language: en-US --------------F44D801B8FA93C1E83C75A35 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit On 2019/2/22 下午3:17, Richard Purdie wrote: > On Fri, 2019-02-22 at 14:03 +0800, Liu Haitao wrote: >> When fetching the source of alsa it would trigger the following >> WARNING: >> >>> WARNING: alsa-lib-1.1.6-r0 do_fetch: Failed to fetch URL >>> ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.1.6.tar.bz2, >>> attempting MIRRORS if >>> available >> Bitbake would use wget with "--no-passive" to fetch the source. >> Behind most firewall and NAT >> configurations it could work well.However, in some rare firewall >> configurations, >> active FTP actually works when passive FTP doesn't. >> >> So disable the use of the passive FTP transfer mode for wget. > As you say, its much more likely that passive ftp would work than > active ftp, so this change would make things worse for more people? > This change maybe make some trouble for others. But I have not found any errors  since  applying the change into the latest yocto. Each of two mode(active and passive) has its own advantages and disadvantages.  Now most servers and firewalls support passive ftp,  while the ALSA is an exception that does not support it. > We're trying to get away from having ftp urls in oe-core at all so > hopefully this isn't a big deal. Thanks for your reminding, I could  try to use https url instead of ftp url in alsa-lib_1.1.6.bb.  The alsa also provides the HTTP server for downing the packages. "https://www.alsa-project.org/files/pub/lib/alsa-lib-1.1.6.tar.bz2" thanks, haitao > Cheers, > > Richard > > --------------F44D801B8FA93C1E83C75A35 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 8bit


On 2019/2/22 下午3:17, Richard Purdie wrote:
On Fri, 2019-02-22 at 14:03 +0800, Liu Haitao wrote:

When fetching the source of alsa it would trigger the following
WARNING:


WARNING: alsa-lib-1.1.6-r0 do_fetch: Failed to fetch URL
ftp://ftp.alsa-project.org/pub/lib/alsa-lib-1.1.6.tar.bz2,
attempting MIRRORS if
available

Bitbake would use wget with "--no-passive" to fetch the source.
Behind most firewall and NAT
configurations it could work well.However, in some rare firewall
configurations,
active FTP actually works when passive FTP doesn't.

So disable the use of the passive FTP transfer mode for wget.

As you say, its much more likely that passive ftp would work than
active ftp, so this change would make things worse for more people?

This change maybe make some trouble for others. But I have not found any errors  since  applying the change into the latest yocto.

 Each of two mode(active and passive) has its own advantages and disadvantages.  Now most servers and firewalls support passive ftp,

 while the ALSA is an exception that does not support it. 

We're trying to get away from having ftp urls in oe-core at all so
hopefully this isn't a big deal.

Thanks for your reminding, I could  try to use https url instead of ftp url in alsa-lib_1.1.6.bb.  The alsa also provides the HTTP server for downing the packages.  "https://www.alsa-project.org/files/pub/lib/alsa-lib-1.1.6.tar.bz2"

thanks,

haitao

Cheers,

Richard
--------------F44D801B8FA93C1E83C75A35--