[oe] meta-browser

[Eric Bénard]

Hi Gary,

Le Thu, 17 May 2012 09:19:48 -0600,
Gary Thomas <gary at mlbassoc.com> a écrit :

> It does look like there's a lot of redirecting going on which is causing the
> wget behaviour:
> 
> $ wget http://commondatastorage.googleapis.com/chromium-browser-official/chromium-19.0.1049.3.tar.bz2
> --2012-05-17 09:16:00--  http://commondatastorage.googleapis.com/chromium-browser-official/chromium-19.0.1049.3.tar.bz2
> Resolving commondatastorage.googleapis.com... 74.125.225.76, 74.125.225.74, 74.125.225.75
> Connecting to commondatastorage.googleapis.com|74.125.225.76|:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: http://redirector-bigcache.googleapis.com/chromium-browser-official/chromium-19.0.1049.3.tar.bz2 [following]
> --2012-05-17 09:16:01--  http://redirector-bigcache.googleapis.com/chromium-browser-official/chromium-19.0.1049.3.tar.bz2
> Resolving redirector-bigcache.googleapis.com... 209.85.225.95
> Connecting to redirector-bigcache.googleapis.com|209.85.225.95|:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: http://o-o.preferred.atl14s01.v2.lscache4.c.bigcache.googleapis.com/chromium-browser-official/chromium-19.0.1049.3.tar.bz2?cms_redirect=yes [following]
> --2012-05-17 09:16:02--  http://o-o.preferred.atl14s01.v2.lscache4.c.bigcache.googleapis.com/chromium-browser-official/chromium-19.0.1049.3.tar.bz2?cms_redirect=yes
> Resolving o-o.preferred.atl14s01.v2.lscache4.c.bigcache.googleapis.com... 173.194.11.234
> Connecting to o-o.preferred.atl14s01.v2.lscache4.c.bigcache.googleapis.com|173.194.11.234|:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: http://v2.cache2.c.bigcache.googleapis.com/chromium-browser-official/chromium-19.0.1049.3.tar.bz2?cms_redirect=yes&redirect_counter=1 [following]
> --2012-05-17 09:16:03--  http://v2.cache2.c.bigcache.googleapis.com/chromium-browser-official/chromium-19.0.1049.3.tar.bz2?cms_redirect=yes&redirect_counter=1
> Resolving v2.cache2.c.bigcache.googleapis.com... 74.125.212.49
> Connecting to v2.cache2.c.bigcache.googleapis.com|74.125.212.49|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 176721817 (169M) [application/x-bzip2]
> Saving to: “chromium-19.0.1049.3.tar.bz2?cms_redirect=yes&redirect_counter=1”
>     ...
> 
> I wonder if wget should be using the -O option to force the resulting filename?
> 
something seems to have changed on their hosting infrastructure.
We will try to find a workaround but there are not many places with
chromium sources tarball and this saves a lot of time vs fetching
from SCM.

Eric