All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org, "Viguera,
	Javier" <Javier.Viguera@digi.com>
Subject: Re: [meta-networking] crda-1.1.3 broken in dylan, dora, daisy and dizzy
Date: Thu, 5 Feb 2015 11:54:31 -0500	[thread overview]
Message-ID: <20150205165430.GH5273@mentor.com> (raw)
In-Reply-To: <3700387.1Q9y16bqhG@peggleto-mobl5.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]

[Re: [oe] [meta-networking] crda-1.1.3 broken in dylan, dora, daisy and dizzy] On 15.02.05 (Thu 16:49) Paul Eggleton wrote:

> On Tuesday 03 February 2015 09:05:54 Viguera, Javier wrote:
> > > -----Original Message-----
> > > From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
> > > 
> > > I agree, #2 is the best option to take care of the older branches.
> > > 
> > > Tom, can you please fetch the following files and add them to the OE
> > > source
> > > 
> > > mirror:
> > >   http://distfiles.lesslinux.org/crda-1.1.3.tar.bz2
> > >   http://distfiles.lesslinux.org/2013.01.11-regulatory.bin
> > > 
> > > I've verified the md5sums match the recipe:
> > >   29579185e06a75675507527243d28e5c  crda-1.1.3.tar.bz2
> > >   e0c8a5ca63fb8bf803213f9a0c90b50b  2013.01.11-regulatory.bin
> > 
> > Good to know we agree on the best option.
> > 
> > Could I make a humble request to speed up the copy of the packages to OE
> > source mirror?
> > 
> > We have a BSP layer that depends on this and currently our build is broken
> > fetching crda.
> 
> I've been thinking about this, and this is getting ridiculous. Instead of 
> manually adding files to the OE source mirror, I think it's time we simply had 
> a populated fallback source mirror that has all the sources for at least the 
> recipes in layers hosted on openembedded.org (if not other commonly used 
> layers) aside from OE-Core which is already handled by the yoctoproject.org 
> mirrors. This issue keeps coming up far too often.
> 
> Is there a possibility we can set this up?

That would be hugely helpful.

-J.

> 
> Cheers,
> Paul
> 
> -- 
> 
> Paul Eggleton
> Intel Open Source Technology Centre
-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 501 bytes --]

  reply	other threads:[~2015-02-05 16:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 16:51 [meta-networking] crda-1.1.3 broken in dylan, dora, daisy and dizzy Viguera, Javier
2015-01-30 17:23 ` Paul Eggleton
2015-02-03  9:05   ` Viguera, Javier
2015-02-05 16:49     ` Paul Eggleton
2015-02-05 16:54       ` Joe MacDonald [this message]
2015-02-05 17:45       ` Hugo Vasconcelos Saldanha
2015-02-05 17:52       ` Khem Raj
2015-02-05 18:04         ` Tom King
2015-02-05 18:49           ` Ash Charles
2015-02-05 19:03             ` Tom King
2015-02-05 19:21               ` Ash Charles
2015-02-06 16:05                 ` Ash Charles
2015-02-05 19:06             ` Martin Jansa
2015-02-16 13:24   ` Paul Eggleton
2015-02-20  9:43     ` Paul Eggleton

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=20150205165430.GH5273@mentor.com \
    --to=joe_macdonald@mentor.com \
    --cc=Javier.Viguera@digi.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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.