From: <wangmy@fujitsu.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-oe] [PATCH] lcms: upgrade 2.14 -> 2.15
Date: Wed, 8 Mar 2023 21:20:42 +0800 [thread overview]
Message-ID: <1678281642-25317-5-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1678281642-25317-1-git-send-email-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
meta-oe/recipes-support/lcms/{lcms_2.14.bb => lcms_2.15.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-support/lcms/{lcms_2.14.bb => lcms_2.15.bb} (79%)
diff --git a/meta-oe/recipes-support/lcms/lcms_2.14.bb b/meta-oe/recipes-support/lcms/lcms_2.15.bb
similarity index 79%
rename from meta-oe/recipes-support/lcms/lcms_2.14.bb
rename to meta-oe/recipes-support/lcms/lcms_2.15.bb
index eb671449f..3656e1cfd 100644
--- a/meta-oe/recipes-support/lcms/lcms_2.14.bb
+++ b/meta-oe/recipes-support/lcms/lcms_2.15.bb
@@ -4,7 +4,7 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://COPYING;md5=ac638b4bc6b67582a11379cfbaeb93dd"
SRC_URI = "${SOURCEFORGE_MIRROR}/lcms/lcms2-${PV}.tar.gz"
-SRC_URI[sha256sum] = "28474ea6f6591c4d4cee972123587001a4e6e353412a41b3e9e82219818d5740"
+SRC_URI[sha256sum] = "b20cbcbd0f503433be2a4e81462106fa61050a35074dc24a4e356792d971ab39"
DEPENDS = "tiff"
--
2.34.1
prev parent reply other threads:[~2023-03-08 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 13:20 [oe] [meta-oe] [PATCH] ctags: upgrade 6.0.20230212.0 -> 6.0.20230305.0 wangmy
2023-03-08 13:20 ` [oe] [meta-oe] [PATCH] freerdp: upgrade 2.9.0 -> 2.10.0 wangmy
2023-03-08 13:20 ` [oe] [meta-oe] [PATCH] gsoap: upgrade 2.0.106 -> 2.0.124 wangmy
2023-03-08 13:20 ` [oe] [meta-oe] [PATCH] hwdata: upgrade 0.367 -> 0.368 wangmy
2023-03-08 13:20 ` wangmy [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=1678281642-25317-5-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox