From: "Andreas Müller" <schnitzeltony@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/4] harfbuzz: upgrade 2.6.4 -> 2.6.7
Date: Fri, 5 Jun 2020 17:29:26 +0200 [thread overview]
Message-ID: <20200605152927.3428858-3-schnitzeltony@gmail.com> (raw)
In-Reply-To: <20200605152927.3428858-1-schnitzeltony@gmail.com>
* Seems they stopped maintaining freedesktop downloads so we missed few versions.
To stay tuned add UPSTREM_CHECKs.
* License checksum was changed by credits & date changes [1]
[1] https://github.com/harfbuzz/harfbuzz/commit/5440313924172e155e34391f033f5e6c5e2390b3#diff-7116ef0705885343c9e1b2171a06be0e
Signed-off-by: Andreas Müller <schnitzeltony@gmail.com>
---
.../harfbuzz/{harfbuzz_2.6.4.bb => harfbuzz_2.6.7.bb} | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
rename meta/recipes-graphics/harfbuzz/{harfbuzz_2.6.4.bb => harfbuzz_2.6.7.bb} (77%)
diff --git a/meta/recipes-graphics/harfbuzz/harfbuzz_2.6.4.bb b/meta/recipes-graphics/harfbuzz/harfbuzz_2.6.7.bb
similarity index 77%
rename from meta/recipes-graphics/harfbuzz/harfbuzz_2.6.4.bb
rename to meta/recipes-graphics/harfbuzz/harfbuzz_2.6.7.bb
index ee08c12bee..4f79da4170 100644
--- a/meta/recipes-graphics/harfbuzz/harfbuzz_2.6.4.bb
+++ b/meta/recipes-graphics/harfbuzz/harfbuzz_2.6.7.bb
@@ -4,12 +4,15 @@ HOMEPAGE = "http://www.freedesktop.org/wiki/Software/HarfBuzz"
BUGTRACKER = "https://bugs.freedesktop.org/enter_bug.cgi?product=HarfBuzz"
SECTION = "libs"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://COPYING;md5=e11f5c3149cdec4bb309babb020b32b9 \
+LIC_FILES_CHKSUM = "file://COPYING;md5=8f787620b7d3866d9552fd1924c07572 \
file://src/hb-ucd.cc;beginline=1;endline=15;md5=29d4dcb6410429195df67efe3382d8bc"
-SRC_URI = "http://www.freedesktop.org/software/harfbuzz/release/${BP}.tar.xz"
-SRC_URI[md5sum] = "2b3a4dfdb3e5e50055f941978944da9f"
-SRC_URI[sha256sum] = "9413b8d96132d699687ef914ebb8c50440efc87b3f775d25856d7ec347c03c12"
+UPSTREAM_CHECK_URI = "https://github.com/${BPN}/${BPN}/releases"
+UPSTREAM_CHECK_REGEX = "harfbuzz-(?P<pver>\d+(\.\d+)+).tar"
+
+SRC_URI = "https://github.com/${BPN}/${BPN}/releases/download/${PV}/${BPN}-${PV}.tar.xz"
+SRC_URI[md5sum] = "3b884586a09328c5fae76d8c200b0e1c"
+SRC_URI[sha256sum] = "49e481d06cdff97bf68d99fa26bdf785331f411614485d892ea4c78eb479b218"
inherit autotools pkgconfig lib_package gtk-doc
--
2.26.2
next prev parent reply other threads:[~2020-06-05 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 15:29 [PATCH 1/4] vte: tiny cleanup / renumber patch Andreas Müller
2020-06-05 15:29 ` [PATCH 2/4] vte: upgrade 0.60.2 -> 0.60.3 Andreas Müller
2020-06-05 15:29 ` Andreas Müller [this message]
2020-06-05 15:29 ` [PATCH 4/4] sqlite3: upgrade 3.32.1 -> 3.32.2 Andreas Müller
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=20200605152927.3428858-3-schnitzeltony@gmail.com \
--to=schnitzeltony@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 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.