From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 15/15] ca-certificates: upgrade 20170717 -> 20180409
Date: Tue, 17 Jul 2018 17:39:10 +0100 [thread overview]
Message-ID: <20180717163910.3196-15-ross.burton@intel.com> (raw)
In-Reply-To: <20180717163910.3196-1-ross.burton@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
---
.../{ca-certificates_20170717.bb => ca-certificates_20180409.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/ca-certificates/{ca-certificates_20170717.bb => ca-certificates_20180409.bb} (95%)
diff --git a/meta/recipes-support/ca-certificates/ca-certificates_20170717.bb b/meta/recipes-support/ca-certificates/ca-certificates_20180409.bb
similarity index 95%
rename from meta/recipes-support/ca-certificates/ca-certificates_20170717.bb
rename to meta/recipes-support/ca-certificates/ca-certificates_20180409.bb
index 24d3a6e4d3e..0d57083c522 100644
--- a/meta/recipes-support/ca-certificates/ca-certificates_20170717.bb
+++ b/meta/recipes-support/ca-certificates/ca-certificates_20180409.bb
@@ -5,7 +5,7 @@ This derived from Debian's CA Certificates."
HOMEPAGE = "http://packages.debian.org/sid/ca-certificates"
SECTION = "misc"
LICENSE = "GPL-2.0+ & MPL-2.0"
-LIC_FILES_CHKSUM = "file://debian/copyright;md5=e7358b9541ccf3029e9705ed8de57968"
+LIC_FILES_CHKSUM = "file://debian/copyright;md5=aeb420429b1659507e0a5a1b123e8308"
# This is needed to ensure we can run the postinst at image creation time
DEPENDS = ""
@@ -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 = "34b8e19e541b8af4076616b2e170c7a70cdaded0"
+SRCREV = "dbbd11e56af93bb79f21d0ee6059a901f83f70a5"
SRC_URI = "git://salsa.debian.org/debian/ca-certificates.git;protocol=https \
file://0002-update-ca-certificates-use-SYSROOT.patch \
--
2.11.0
next prev parent reply other threads:[~2018-07-17 16:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 16:38 [PATCH 01/15] bc: upgrade to 1.07.1 Ross Burton
2018-07-17 16:38 ` [PATCH 02/15] tcf-agent: upgrade to 1.7.0 Ross Burton
2018-07-17 16:38 ` [PATCH 03/15] libyaml: upgrade to 0.2.1 Ross Burton
2018-07-17 16:38 ` [PATCH 04/15] btrfs-tools: upgrade 4.16.1 -> 4.17 Ross Burton
2018-07-17 16:39 ` [PATCH 05/15] gnupg: upgrade 2.2.8 -> 2.2.9 Ross Burton
2018-07-17 16:39 ` [PATCH 06/15] libgpg-error: upgrade 1.31 -> 1.32 Ross Burton
2018-07-17 16:39 ` [PATCH 07/15] sysstat: upgrade 11.7.3 -> 11.7.4 Ross Burton
2018-07-17 16:39 ` [PATCH 08/15] xz: upgrade 5.2.3 -> 5.2.4 Ross Burton
2018-07-17 16:39 ` [PATCH 09/15] strace: upgrade 4.22 -> 4.23 Ross Burton
2018-07-17 16:39 ` [PATCH 10/15] pciutils: upgrade 3.5.6 -> 3.6.1 Ross Burton
2018-07-17 16:39 ` [PATCH 11/15] libinput: upgrade 1.11.0 -> 1.11.2 Ross Burton
2018-07-17 16:39 ` [PATCH 12/15] harfbuzz: upgrade 1.7.5 -> 1.8.4 Ross Burton
2018-07-17 18:23 ` Khem Raj
2018-07-17 19:21 ` Burton, Ross
2018-07-17 16:39 ` [PATCH 13/15] shared-mime-info: upgrade 1.9 -> 1.10 Ross Burton
2018-07-17 16:39 ` [PATCH 14/15] xf86-input-libinput: upgrade 0.27.1 -> 0.28.0 Ross Burton
2018-07-17 16:39 ` Ross Burton [this message]
2018-07-17 17:18 ` [PATCH 15/15] ca-certificates: upgrade 20170717 -> 20180409 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=20180717163910.3196-15-ross.burton@intel.com \
--to=ross.burton@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