From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 18/20] ca-certificates: upgrade 20180409 -> 20190110
Date: Tue, 19 Feb 2019 18:47:10 +0100 [thread overview]
Message-ID: <20190219174712.60694-18-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20190219174712.60694-1-alex.kanavin@gmail.com>
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
...{ca-certificates_20180409.bb => ca-certificates_20190110.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/ca-certificates/{ca-certificates_20180409.bb => ca-certificates_20190110.bb} (98%)
diff --git a/meta/recipes-support/ca-certificates/ca-certificates_20180409.bb b/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb
similarity index 98%
rename from meta/recipes-support/ca-certificates/ca-certificates_20180409.bb
rename to meta/recipes-support/ca-certificates/ca-certificates_20190110.bb
index 0d57083c522..b9f57900c8e 100644
--- a/meta/recipes-support/ca-certificates/ca-certificates_20180409.bb
+++ b/meta/recipes-support/ca-certificates/ca-certificates_20190110.bb
@@ -14,7 +14,7 @@ DEPENDS_class-nativesdk = "openssl-native"
# Need c_rehash from openssl and run-parts from debianutils
PACKAGE_WRITE_DEPS += "openssl-native debianutils-native"
-SRCREV = "dbbd11e56af93bb79f21d0ee6059a901f83f70a5"
+SRCREV = "c28799b138b044c963d24c4a69659b6e5486e3be"
SRC_URI = "git://salsa.debian.org/debian/ca-certificates.git;protocol=https \
file://0002-update-ca-certificates-use-SYSROOT.patch \
--
2.17.1
next prev 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 ` [PATCH 13/20] webkitgtk: upgrade 2.22.5 -> 2.22.6 Alexander Kanavin
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 ` Alexander Kanavin [this message]
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-18-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