Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 13/20] webkitgtk: upgrade 2.22.5 -> 2.22.6
Date: Tue, 19 Feb 2019 18:47:05 +0100	[thread overview]
Message-ID: <20190219174712.60694-13-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20190219174712.60694-1-alex.kanavin@gmail.com>

Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
 .../webkit/{webkitgtk_2.22.5.bb => webkitgtk_2.22.6.bb}       | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta/recipes-sato/webkit/{webkitgtk_2.22.5.bb => webkitgtk_2.22.6.bb} (97%)

diff --git a/meta/recipes-sato/webkit/webkitgtk_2.22.5.bb b/meta/recipes-sato/webkit/webkitgtk_2.22.6.bb
similarity index 97%
rename from meta/recipes-sato/webkit/webkitgtk_2.22.5.bb
rename to meta/recipes-sato/webkit/webkitgtk_2.22.6.bb
index 3d8c0338c7d..35c70e0d026 100644
--- a/meta/recipes-sato/webkit/webkitgtk_2.22.5.bb
+++ b/meta/recipes-sato/webkit/webkitgtk_2.22.6.bb
@@ -23,8 +23,8 @@ SRC_URI = "http://www.webkitgtk.org/releases/${BPN}-${PV}.tar.xz \
            file://bad_optional_access.patch \
            "
 
-SRC_URI[md5sum] = "96a731522b800f38e70f85c22f8de477"
-SRC_URI[sha256sum] = "99d3863f418a7c3a3e37e5062950dbf2d91fb106ec1633459b0ef6f2d5f6cb13"
+SRC_URI[md5sum] = "7c21a30f7f078f0b712caf0c7ee966a4"
+SRC_URI[sha256sum] = "df90db9c0db0a2072b945fa3e1d45865922bd686c4659cce6cb5897ce357c85b"
 
 inherit cmake pkgconfig gobject-introspection perlnative distro_features_check upstream-version-is-even gtk-doc
 
-- 
2.17.1



  parent reply	other threads:[~2019-02-19 17:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19 17:46 [PATCH 01/20] libpipeline: update to 1.5.1 Alexander Kanavin
2019-02-19 17:46 ` [PATCH 02/20] libmodulemd: update to 2.1.0 Alexander Kanavin
2019-02-19 17:46 ` [PATCH 03/20] vala: upgrade 0.42.4 -> 0.42.5 Alexander Kanavin
2019-02-19 17:46 ` [PATCH 04/20] epiphany: upgrade 3.30.2 -> 3.30.3 Alexander Kanavin
2019-02-19 17:46 ` [PATCH 05/20] libdnf: upgrade 0.24.1 -> 0.26.0 Alexander Kanavin
2019-02-19 17:46 ` [PATCH 06/20] meson: upgrade 0.49.0 -> 0.49.2 Alexander Kanavin
2019-02-19 17:46 ` [PATCH 07/20] p11-kit: upgrade 0.23.14 -> 0.23.15 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 08/20] iso-codes: upgrade 4.1 -> 4.2 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 09/20] libcomps: upgrade 0.1.9 -> 0.1.10 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 10/20] lighttpd: upgrade 1.4.52 -> 1.4.53 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 11/20] createrepo-c: upgrade 0.12.0 -> 0.12.1 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 12/20] gcr: upgrade 3.28.0 -> 3.28.1 Alexander Kanavin
2019-02-19 17:47 ` Alexander Kanavin [this message]
2019-02-19 17:47 ` [PATCH 14/20] librepo: upgrade 1.9.3 -> 1.9.4 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 15/20] btrfs-tools: upgrade 4.19.1 -> 4.20.1 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 16/20] dnf: upgrade 4.0.10 -> 4.1.0 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 17/20] libwebp: upgrade 1.0.1 -> 1.0.2 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 18/20] ca-certificates: upgrade 20180409 -> 20190110 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 19/20] ffmpeg: update to 4.1.1 Alexander Kanavin
2019-02-19 17:47 ` [PATCH 20/20] menu-cache: fix upstream version check Alexander Kanavin

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=20190219174712.60694-13-alex.kanavin@gmail.com \
    --to=alex.kanavin@gmail.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