From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/2] efivar: 0.7 -> 0.21
Date: Wed, 23 Sep 2015 16:08:29 +0200 [thread overview]
Message-ID: <20150923140829.GE2384@jama> (raw)
In-Reply-To: <1441704708-22940-2-git-send-email-kai.kang@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]
On Tue, Sep 08, 2015 at 05:31:47PM +0800, kai.kang@windriver.com wrote:
> From: Kai Kang <kai.kang@windriver.com>
>
> Upgrade efivar from 0.7 to 0.21.
>
> * update HOMEPAGE
Fails to build in world http://errors.yoctoproject.org/Errors/Details/18426/
>
> Signed-off-by: Kai Kang <kai.kang@windriver.com>
> ---
> meta-oe/recipes-extended/efivar/efivar_git.bb | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/meta-oe/recipes-extended/efivar/efivar_git.bb b/meta-oe/recipes-extended/efivar/efivar_git.bb
> index 18446a0..bf2e6d2 100644
> --- a/meta-oe/recipes-extended/efivar/efivar_git.bb
> +++ b/meta-oe/recipes-extended/efivar/efivar_git.bb
> @@ -1,14 +1,14 @@
> SUMMARY = "Tools to manipulate UEFI variables"
> DESCRIPTION = "efivar provides a simple command line interface to the UEFI variable facility"
> -HOMEPAGE = "https://github.com/vathpela/efivar"
> +HOMEPAGE = "https://github.com/rhinstaller/efivar"
>
> LICENSE = "LGPLv2.1"
> -LIC_FILES_CHKSUM = "file://COPYING;md5=a6f89e2100d9b6cdffcea4f398e37343"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=6626bb1e20189cfa95f2c508ba286393"
>
> DEPENDS = "popt"
>
> -SRCREV = "c9e1f24a81b5374408bca5616402276e47171cf7"
> -PV = "0.7+git${SRCPV}"
> +SRCREV = "aab6c2a64d90b6e5a63661fb5bd6be8d878b0784"
> +PV = "0.21+git${SRCPV}"
> SRC_URI = "git://github.com/vathpela/efivar.git"
>
> S = "${WORKDIR}/git"
> --
> 1.9.1
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-09-23 14:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 9:31 [meta-oe][PATCH 0/2] Upgrade efivar and efibootmgr kai.kang
2015-09-08 9:31 ` [PATCH 1/2] efivar: 0.7 -> 0.21 kai.kang
2015-09-23 14:08 ` Martin Jansa [this message]
2015-09-24 1:58 ` Kang Kai
2015-09-08 9:31 ` [PATCH 2/2] efibootmgr: 0.6.0 -> 0.12 kai.kang
-- strict thread matches above, loose matches on Subject: below --
2015-09-29 7:04 [meta-oe][PATCH 0/2] V2: Upgrade efivar and efibootmgr kai.kang
2015-09-29 7:04 ` [PATCH 1/2] efivar: 0.7 -> 0.21 kai.kang
2015-10-08 9:59 ` Martin Jansa
2015-10-09 7:20 ` Khem Raj
2015-10-09 8:50 ` Martin Jansa
2015-10-09 9:24 ` Kang Kai
2015-10-09 15:18 ` Khem Raj
2015-10-09 15:26 ` Martin Jansa
2015-10-09 15:53 ` Khem Raj
2015-09-30 6:21 [meta-oe][PATCH 0/2] V3: Upgrade efivar and efibootmgr kai.kang
2015-09-30 6:21 ` [PATCH 1/2] efivar: 0.7 -> 0.21 kai.kang
2015-10-10 3:31 [PATCH 0/2] V3: Upgrade efivar and efibootmgr kai.kang
2015-10-10 3:31 ` [PATCH 1/2] efivar: 0.7 -> 0.21 kai.kang
2015-10-12 6:20 ` Kang Kai
2015-10-12 6:26 [meta-oe][PATCH 0/2] V4: Upgrade efivar and efibootmgr kai.kang
2015-10-12 6:26 ` [PATCH 1/2] efivar: 0.7 -> 0.21 kai.kang
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=20150923140829.GE2384@jama \
--to=martin.jansa@gmail.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.