[oe] meta-browser

Paul Eggleton paul.eggleton at linux.intel.com
Thu May 17 15:04:15 UTC 2012


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

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre




More information about the Openembedded-devel mailing list