Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: David Thomas <david.thomas@microbee-systems.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: SRC_URI = "svn://svn.o-hand.com/repos/matchbox/trunk
Date: Fri, 11 Nov 2011 15:53:29 +0000	[thread overview]
Message-ID: <45554938.bbIM0h9DI3@helios> (raw)
In-Reply-To: <CALJpqJw_QkVCyD918ymd6=11VaFC1uj6kGy_XVkaL+-WJQ8jgw@mail.gmail.com>

On Friday 11 November 2011 09:20:18 you wrote:
> Sorry, new to this system. We mostly design hardware and I go in and
> out of Linux development periodically and it is difficult to keep
> current for this reason.

No problem. I know you've been very patient with the frustrations you have, if 
you'll just bear with us I'm sure we can sort it out.

> DISTRO = "angstrom-2008.1"

OK. So it ought to have the approprate file in the mirror. What version of 
bitbake are you using? Also, could you run the following:

bitbake -e matchbox-native | grep ^PREMIRRORS

> Will I need to search any bb files using the dead SRC_URI and replace
> them with yoctoproject.org?

That's one way of fixing it, yes.

BTW I would suggest if you are starting a new project and you expect to keep 
it around for a while you should consider using something based on top of 
OpenEmbedded-Core, such as the Yocto Project or a newer version of Angstrom. 
That way issues like these (broken downloads) get taken care of, since OE-core 
is maintained.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  parent reply	other threads:[~2011-11-11 15:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 22:32 SRC_URI = "svn://svn.o-hand.com/repos/matchbox/trunk David Thomas
2011-11-10  9:58 ` Paul Eggleton
2011-11-10 12:35   ` David Thomas
2011-11-10 22:11     ` David Thomas
2011-11-10 23:04       ` Paul Menzel
2011-11-11  3:17         ` David Thomas
2011-11-11  7:30           ` Paul Menzel
2011-11-11 11:55             ` Dave Thomas
2011-11-11 12:11             ` David Thomas
2011-11-11 13:05               ` Paul Eggleton
2011-11-11 14:51                 ` David Thomas
2011-11-11 15:14                   ` Paul Eggleton
     [not found]                     ` <CALJpqJw_QkVCyD918ymd6=11VaFC1uj6kGy_XVkaL+-WJQ8jgw@mail.gmail.com>
2011-11-11 15:53                       ` Paul Eggleton [this message]
     [not found]                         ` <CALJpqJwC460+sy7PBVt+q6uVqYKs+XpgqfNombbSZaH8U9SCfw@mail.gmail.com>
2011-11-11 16:14                           ` Paul Eggleton
     [not found]                             ` <CALJpqJw26yq0H4JEMDBaNamxN+_beJHu7sHLkEAWmAD_jKGXVg@mail.gmail.com>
2011-11-11 16:30                               ` Paul Eggleton
     [not found]                                 ` <CALJpqJwNOLdF+3UGoYmeMPLbYBm9dvmit-hOjzF2YHHebF385Q@mail.gmail.com>
2011-11-11 16:53                                   ` Paul Eggleton
     [not found]                                     ` <CALJpqJw6MvmkxxDhJ_amJRFep3yYoTjRogPD4GQ1HG2RpQmvQQ@mail.gmail.com>
2011-11-11 17:28                                       ` Paul Eggleton
2011-11-12 15:22                                         ` David Thomas
2011-11-11 15:52                 ` David Thomas
2011-11-11 16:03                   ` Martin Jansa
2011-11-11 16:08                     ` David Thomas

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=45554938.bbIM0h9DI3@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=david.thomas@microbee-systems.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