From: Anuj Mittal <anuj.mittal@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/3] wayland-protocols: upgrade 1.16 -> 1.17
Date: Thu, 7 Feb 2019 13:57:13 +0800 [thread overview]
Message-ID: <20190207055714.25880-2-anuj.mittal@intel.com> (raw)
In-Reply-To: <20190207055714.25880-1-anuj.mittal@intel.com>
For changes, see:
https://lists.freedesktop.org/archives/wayland-devel/2018-November/039662.html
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
---
.../{wayland-protocols_1.16.bb => wayland-protocols_1.17.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-graphics/wayland/{wayland-protocols_1.16.bb => wayland-protocols_1.17.bb} (86%)
diff --git a/meta/recipes-graphics/wayland/wayland-protocols_1.16.bb b/meta/recipes-graphics/wayland/wayland-protocols_1.17.bb
similarity index 86%
rename from meta/recipes-graphics/wayland/wayland-protocols_1.16.bb
rename to meta/recipes-graphics/wayland/wayland-protocols_1.17.bb
index fc4b711172..ca8f06c551 100644
--- a/meta/recipes-graphics/wayland/wayland-protocols_1.16.bb
+++ b/meta/recipes-graphics/wayland/wayland-protocols_1.17.bb
@@ -11,8 +11,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=c7b12b6702da38ca028ace54aae3d484 \
SRC_URI = "https://wayland.freedesktop.org/releases/${BPN}-${PV}.tar.xz \
"
-SRC_URI[md5sum] = "e0b523ff162e30bab46be1d65d527683"
-SRC_URI[sha256sum] = "6b1485951fdcd36a960c870c46f28b03a3e5121fb46246916333ed07f78c98c5"
+SRC_URI[md5sum] = "55ddd5fdb02b73b9de9559aaec267315"
+SRC_URI[sha256sum] = "df1319cf9705643aea9fd16f9056f4e5b2471bd10c0cc3713d4a4cdc23d6812f"
UPSTREAM_CHECK_URI = "https://wayland.freedesktop.org/releases.html"
--
2.17.1
next prev parent reply other threads:[~2019-02-07 5:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 5:57 [PATCH 1/3] libva: upgrade 2.3.0 -> 2.4.0 Anuj Mittal
2019-02-07 5:57 ` Anuj Mittal [this message]
2019-02-07 5:57 ` [PATCH 3/3] libva-utils: " Anuj Mittal
2019-02-07 21:05 ` [PATCH 1/3] libva: " Richard Purdie
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=20190207055714.25880-2-anuj.mittal@intel.com \
--to=anuj.mittal@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