Re: [PATCH] bitbake.conf:update FETCHCMD_wget with --no-passive-ftp

[Haitaoliu <Haitao.Liu@windriver.com>]

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]


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
>
>

[-- Attachment #2: Type: text/html, Size: 3265 bytes --]