From: Khem Raj <raj.khem@gmail.com>
To: Ricardo Salveti <ricardo@foundries.io>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] libp11: upgrade 0.4.10 -> 11
Date: Thu, 27 Feb 2020 11:02:21 -0800 [thread overview]
Message-ID: <CAMKF1spoR9p1UDrPHsW+MA6sK7DnUgDyxy+voZODM27rus_JfA@mail.gmail.com> (raw)
In-Reply-To: <CAAaKDhE__cs1WdFWSN7_JRDfX_TzyxUr0eQpYWNTRSxvmdoZ7w@mail.gmail.com>
On Thu, Feb 27, 2020 at 9:53 AM Ricardo Salveti <ricardo@foundries.io> wrote:
>
> Hi,
>
> On Fri, Feb 14, 2020 at 1:12 PM Wang Mingyu <wangmy@cn.fujitsu.com> wrote:
> >
> > Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
> > ---
> > .../recipes-support/libp11/{libp11_0.4.10.bb => libp11_11.bb} | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> > rename meta-oe/recipes-support/libp11/{libp11_0.4.10.bb => libp11_11.bb} (93%)
> >
> > diff --git a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb b/meta-oe/recipes-support/libp11/libp11_11.bb
> > similarity index 93%
> > rename from meta-oe/recipes-support/libp11/libp11_0.4.10.bb
> > rename to meta-oe/recipes-support/libp11/libp11_11.bb
> > index 655db4907..5a0951df2 100644
> > --- a/meta-oe/recipes-support/libp11/libp11_0.4.10.bb
> > +++ b/meta-oe/recipes-support/libp11/libp11_11.bb
> > @@ -10,7 +10,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=fad9b3332be894bab9bc501572864b29"
> > DEPENDS = "libtool openssl"
> >
> > SRC_URI = "git://github.com/OpenSC/libp11.git"
> > -SRCREV = "973d31f3f58d5549ddd8b1f822ce8f72186f9d68"
> > +SRCREV = "e1210903291b1de9eabcad26e740a4b2fbcca692"
>
> Is this change really correct? The latest libp11 upstream release is
> 0.4.10, as you can see at https://github.com/OpenSC/libp11/releases.
> The next one seems that will be 0.4.11, so now sure how it was moved
> to 11 directly.
>
> Also, the SRCREV seems incorrect, as it is pointing out to the 0.4.9
> release (https://github.com/OpenSC/libp11/commit/e1210903291b1de9eabcad26e740a4b2fbcca6920).
>
> In the end this change is increasing the PV but moving SRCREV to an
> even older release.
>
you are right, and it escaped me. Would you be willing to send a patch
to correct it
since it was not long time ago.
> Thanks,
> --
> Ricardo Salveti
prev parent reply other threads:[~2020-02-27 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 23:43 [meta-oe][PATCH] cryptsetup: upgrade 2.2.2 -> 2.3.0 Wang Mingyu
2020-02-14 23:43 ` [meta-oe][PATCH] fio: upgrade 3.17 -> 3.18 Wang Mingyu
2020-02-15 8:40 ` Khem Raj
2020-02-18 19:37 ` Jonathan Richardson
2020-02-18 22:09 ` Adrian Bunk
2020-02-19 0:37 ` Jonathan Richardson
2020-02-19 2:36 ` Khem Raj
2020-02-14 23:43 ` [meta-oe][PATCH] hwdata: upgrade 0.331 -> 0.332 Wang Mingyu
2020-02-14 23:43 ` [meta-oe][PATCH] libdbi-perl: upgrade 1.642 -> 1.643 Wang Mingyu
2020-02-14 23:43 ` [meta-oe][PATCH] libp11: upgrade 0.4.10 -> 11 Wang Mingyu
2020-02-27 17:52 ` Ricardo Salveti
2020-02-27 17:57 ` Ricardo Salveti
2020-02-27 19:02 ` Khem Raj [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=CAMKF1spoR9p1UDrPHsW+MA6sK7DnUgDyxy+voZODM27rus_JfA@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ricardo@foundries.io \
/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.