From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: meta-browser
Date: Thu, 17 May 2012 17:30:59 +0200 [thread overview]
Message-ID: <20120517173059.5a18d533@eb-e6520> (raw)
In-Reply-To: <4FB51714.8030201@mlbassoc.com>
Hi Gary,
Le Thu, 17 May 2012 09:19:48 -0600,
Gary Thomas <gary@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
next prev parent reply other threads:[~2012-05-17 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 14:18 meta-browser Gary Thomas
2012-05-17 14:37 ` meta-browser Paul Eggleton
2012-05-17 14:46 ` meta-browser Gary Thomas
2012-05-17 15:04 ` meta-browser Paul Eggleton
2012-05-17 15:19 ` meta-browser Gary Thomas
2012-05-17 15:30 ` Eric Bénard [this message]
2012-05-17 15:52 ` meta-browser Eric Bénard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120517173059.5a18d533@eb-e6520 \
--to=eric@eukrea.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox