From: Martyn Welch <martyn.welch@ge.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: SRC_URI fetching problem
Date: Mon, 15 Mar 2010 10:42:50 +0000 [thread overview]
Message-ID: <4B9E0F2A.4000503@ge.com> (raw)
In-Reply-To: <4B9E0A1B.3070606@dresearch.de>
Steffen Sledz wrote:
> Martyn Welch wrote:
>
>> Steffen Sledz wrote:
>>
>>> I work at a recipe for rsyslog (http://www.rsyslog.com) and hit a
>>> problem with the wget fetcher.
>>>
>>> The download uri for rsyslog-5.4.0.tar.gz does not contain the archive
>>> name itself but is http://www.rsyslog.com/Downloads-req-getit-lid-197.phtml.
>>>
>>> If i set
>>>
>>> SRC_URI = "http://www.rsyslog.com/Downloads-req-getit-lid-197.phtml"
>>> SRC_URI[archive.md5sum] = "291882229d50496f42bd63174076dd37"
>>> SRC_URI[archive.sha256sum] = "d9cd21d2fcd45fcae65eb0a51927c40315cca02afdc62478abd950febfcf7228"
>>>
>> At a guess you need to add ";name=archive" to the end of your SRC_URI.
>>
>
> Nope, same behaviour. :(
>
> BTW: The ";name=" option is not documented in the user manual at
> <http://docs.openembedded.org/usermanual/usermanual.html>.
>
Neither is the relatively new mechanism for incuding the md5sum and
sha256sum in the recipe. Unless you add the "name" parameter (or the
md5sum and sha256sum for that SRC_URI happens to already be in
checksum.ini) you will probably see another failure when it attempts to
validate the archive it has been downloaded. Either way, I think Thomas'
suggestion may be right.
Martyn
--
Martyn Welch (Principal Software Engineer) | Registered in England and
GE Intelligent Platforms | Wales (3828642) at 100
T +44(0)127322748 | Barbirolli Square, Manchester,
E martyn.welch@ge.com | M2 3AB VAT:GB 927559189
prev parent reply other threads:[~2010-03-15 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 10:13 SRC_URI fetching problem Steffen Sledz
2010-03-15 10:19 ` Martyn Welch
2010-03-15 10:21 ` Steffen Sledz
2010-03-15 10:31 ` Thomas Zimmermann
2010-03-15 10:37 ` Steffen Sledz
2010-03-15 10:42 ` Martyn Welch [this message]
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=4B9E0F2A.4000503@ge.com \
--to=martyn.welch@ge.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