From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] update-rc.d: Switch from a tag to a sepcific revision
Date: Mon, 11 Jul 2011 09:59:41 -0700 [thread overview]
Message-ID: <1310403581.2188.3.camel@vorpal.jf.intel.com> (raw)
In-Reply-To: <1310399257.20015.968.camel@rex>
On Mon, 2011-07-11 at 16:47 +0100, Richard Purdie wrote:
> Unfortunately the git fetcher cannot resolve a named tag into a revision
> without network access. Since its desireable for OE-Core to function
> in a networkless environment, we need to specify the revision in the
> recipe which corresponds to the 0.7 tag.
>
> [YOCTO #1140]
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Acked-by: Joshua Lock <josh@linux.intel.com>
> ---
> meta/recipes-core/update-rc.d/update-rc.d_0.7.bb | 5 ++++-
> 1 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb b/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
> index 5bd88cb..8bc3dbf 100644
> --- a/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
> +++ b/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb
> @@ -7,7 +7,10 @@ LIC_FILES_CHKSUM = "file://update-rc.d;beginline=5;endline=15;md5=148a48321b10eb
>
> PR = "r4"
>
> -SRC_URI = "git://github.com/philb/update-rc.d.git;tag=update-rc.d_${PV};protocol=git \
> +# Revision corresponding to tag update-rc.d_0.7
> +SRCREV = "eca680ddf28d024954895f59a241a622dd575c11"
> +
> +SRC_URI = "git://github.com/philb/update-rc.d.git;protocol=git \
> file://add-verbose.patch;striplevel=1"
>
> S = "${WORKDIR}/git"
--
Joshua Lock
Yocto Project "Johannes Factotum"
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-07-11 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 15:47 [PATCH] update-rc.d: Switch from a tag to a sepcific revision Richard Purdie
2011-07-11 16:59 ` Joshua Lock [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=1310403581.2188.3.camel@vorpal.jf.intel.com \
--to=josh@linux.intel.com \
--cc=openembedded-core@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