From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Recipes with fetch failures:
Date: Sun, 23 Jan 2011 08:36:43 -0700 [thread overview]
Message-ID: <4D3C4B0B.3080108@mentor.com> (raw)
In-Reply-To: <AANLkTimOGhiwA+szLoWVzAUP2AUX1YVBcOnMLg3YSWdM@mail.gmail.com>
On 01/22/2011 01:17 PM, Khem Raj wrote:
> On Sat, Jan 22, 2011 at 12:07 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> On Sat, Jan 22, 2011 at 17:46, Khem Raj<raj.khem@gmail.com> wrote:
>>> On Sat, Jan 22, 2011 at 10:06 AM, Otavio Salvador
>>>> cvs://anoncvs:anoncvs@anoncvs.handhelds.org/cvs;module=ipkg-utils
>>>>
>>>
>>> yeah hh.org is gone. So you need to rely on mirrors to get the tarballs
>>> add
>>>
>>> SOURCE_MIRROR_URL ?= "http://sources.openembedded.org/"
>>>
>>> to your local.conf and probably you also need to inherit own_mirrors
>>
>> I think the recipe should be change to use this in this case. I know I
>> can use mirrors but the recipe ought to use a fetchable reference IMO.
>>
>
> we are still hopeful of getting the cvs repos. But yes it wont hurt if
> the SRC_URIs pointed
> to source mirrors for now
If a rather critical part of how we do things was apparently dead
software and just went away, perhaps we really really need to
investigate using something else or taking up the project and hosting it
$wherever ?
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-01-23 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 18:06 Recipes with fetch failures: Otavio Salvador
2011-01-22 19:46 ` Khem Raj
2011-01-22 20:07 ` Otavio Salvador
2011-01-22 20:17 ` Khem Raj
2011-01-23 15:36 ` Tom Rini [this message]
2011-01-23 18:49 ` Bernhard Reutner-Fischer
2011-01-24 10:42 ` Marcin Juszkiewicz
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=4D3C4B0B.3080108@mentor.com \
--to=tom_rini@mentor.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 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.