On 2012-05-17 09:04, Paul Eggleton wrote:
On Thursday 17 May 2012 08:46:08 you wrote:
On 2012-05-17 08:37, Paul Eggleton wrote:
On Thursday 17 May 2012 08:18:47 Gary Thomas wrote:
Trying the new layer, when I ran 'bitbake chromium -c fetch', I got this
error: Fetcher failure for URL:
'http://commondatastorage.googleapis.com/chromium-browser-official/chromi
um
-19.0.1049.3.tar.bz2'. The fetch command returned success for url
http://commondatastorage.googleapis.com/chromium-browser-official/chromiu
m-
19.0.1049.3.tar.bz2 but
/local/p60_poky/downloads/chromium-19.0.1049.3.tar.bz2 doesn't exist?!
Looking at my tree, I found this:
downloads/chromium-19.0.1049.3.tar.bz2?cms_redirect=yes&redirect_counter=
1
which has MD5SUM that matches the recipe.
Any ideas what might have gone wrong?
If it really has "?cms_redirect=yes&redirect_counter=1" at the end of the
filename that might have something to do with it...
Of course, but that's a result of the fetcher code - the recipe does not
have such:
SRC_URI =
"http://commondatastorage.googleapis.com/chromium-browser-official/${P}.tar
.bz2"
The fetch log is at http://www.mlbassoc.com/misc/chromium_fetch.log
My build host is Fedora 16 (i686)
My oe-core (poky/master) is rev 38da655788
Out of curiosity I tried to download the file manually and got a 404, so I
think there is a bigger issue with this recipe than fetcher behaviour...
Interesting because the fetcher did get the file for me, albeit with those
decorations, that has the correct MD5SUM
-rw-rw-r-- 1 gthomas gthomas 176721817 Feb 23 14:57
downloads/chromium-19.0.1049.3.tar.bz2
(I stripped the decorations manually)
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?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
