From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
Rick Bianchi <bianchirickkutta@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: WARNING: Failed to fetch URL http://downloads.sourceforge.net/openjade/openjade-0.6.14.tar.gz, attempting MIRRORS if available
Date: Mon, 03 Mar 2014 16:29:30 +0000 [thread overview]
Message-ID: <5314ADEA.6040206@dynamicdevices.co.uk> (raw)
In-Reply-To: <2231928.eQF8dO1LsD@peggleto-mobl5.ger.corp.intel.com>
On 03/03/2014 16:27, Paul Eggleton wrote:
> On Monday 03 March 2014 14:53:26 Alex J Lennon wrote:
>> On 03/03/2014 14:36, Rick Bianchi wrote:
>>> Does anyone know how I can get around this error? There is no such
>>> package on sourceforge "Fetcher failure for URL:
>>> 'http://downloads.sourceforge.net/openjade/openjade-0.6.14.tar.gz'.
>>> Unable to fetch URL from any source."
>> Rick, as Paul mentioned there seems to be something really strange going on.
>>
>> If you look in the docbook-utils-native recipe (which is at r3 for me in
>> master:d6596f5e0446b6aa3ae845389965bb2852f17b65) it is 0.6.14
>>
>> That recipe doesn't use the openjade tarball although it has a
>> dependency on openjade-native
>>
>> If you look at the openjade-native recipe it is at version 1.3.2
>>
>> So, you'd expect docbook-utils-native to be pulling down a 0.6.14
>> docbook tarball, or if you were building openjade-native you'd expect
>> the openjade 1.3.2 tarball to be pulled down (I believe)
>>
>> So it looks as though somehow there's some kind of corruption that is
>> mixing up openjade with the 0.6.14 of docbook for some reason.
>>
>> i.e. I don't believe you're going to find a tarball of an
>> openjade-0.6.14 release.
> This is my assessment of what's happening also. I can't understand how this
> could ever happen, but it looks like SRC_URI is being mixed up between the two
> recipes, and this is on the dylan (old stable) branch as well.
>
>> It might be better to try checkout out your layers again and doing a
>> rebuild from scratch ?
> Before doing this, Rick could you run the following and post the output:
>
> bitbake -e docbook-utils-native | grep ^SRC_URI=
The other thought that came to mind is that you might disable all the
other layers in your bblayers configuration file, and try building
docbook-utils-native
That at least would isolate whether there's some odd layer interaction
going on.
Cheers, Alex
> Thanks,
> Paul
>
next prev parent reply other threads:[~2014-03-03 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 14:36 WARNING: Failed to fetch URL http://downloads.sourceforge.net/openjade/openjade-0.6.14.tar.gz, attempting MIRRORS if available Rick Bianchi
2014-03-03 14:53 ` Alex J Lennon
2014-03-03 16:27 ` Paul Eggleton
2014-03-03 16:29 ` Alex J Lennon [this message]
2014-03-03 16:40 ` Rick Bianchi
2014-03-03 16:43 ` Paul Eggleton
2014-03-03 16:47 ` Rick Bianchi
2014-03-03 16:48 ` Alex J Lennon
2014-03-03 16:49 ` Paul Eggleton
2014-03-03 16:55 ` Rick Bianchi
2014-03-03 16:56 ` Rick Bianchi
2014-03-03 17:13 ` Paul Eggleton
2014-03-03 17:25 ` Paul Eggleton
2014-03-03 17:38 ` Rick Bianchi
2014-03-03 16:44 ` Rick Bianchi
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=5314ADEA.6040206@dynamicdevices.co.uk \
--to=ajlennon@dynamicdevices.co.uk \
--cc=bianchirickkutta@gmail.com \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.