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 13:05:30 +0000 [thread overview]
Message-ID: <6416131.BOns2L3oYb@helios> (raw)
In-Reply-To: <833EEBB2-42FF-438F-A5F3-8B24DDD3964D@microbee-systems.com>
On Friday 11 November 2011 06:11:14 David Thomas wrote:
> Well I checked this and the files where in this location... Still no dice.
> The manual states it first searches to see if they exist then downloads. I
> see the opposite, it fails to contact the server and then fails.
I don't think this is to do with those files (they are in the files subdir as
you point out, and they will be found there via FILESPATH; this is automatic).
If it's contacting the server and failing, it's the URI pointing to that
server or some other problem relating to that operation. You're not behind
some kind of firewall that blocks the git protocol are you?
Also, from one of your earlier emails:
> SRC_URI = "git:///home/twoods/local;protocol=file;branch=master"
I don't think this is what you want. Just use file://<full path> if you want to
point it to a local location. But I'm not sure that's what you really want
here either.
> git://git.yoctoproject.org/matchbox-keyboard;protocol=git;file://smallscreen
> -fontsize.patch;patch=1
That won't work - you have no space between the first URI and the next. Fix
that, and assuming your network allows access to remote git repos, that should
work.
You can double check what SRC_URI bitbake is going to use by running this:
bitbake -e matchbox-keyboard | grep ^SRC_URI
Could you also remind me what DISTRO you are using?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-11-11 13:11 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 [this message]
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
[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=6416131.BOns2L3oYb@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 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.