From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] ca-certificates: Version bump. 3.100 -> 3.101
Date: Sat, 15 Jun 2024 16:58:48 +0200 [thread overview]
Message-ID: <20240615145848.4136285-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20240610191438.154471-1-christian.melki@t2data.com>
Thanks, applied as 4e4d7391386a454b98e23edf72948f0fea1b1690.
Michael
[sent from post-receive hook]
On Sat, 15 Jun 2024 16:58:48 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> https://firefox-source-docs.mozilla.org/security/nss/releases/nss_3_101.html
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20240610191438.154471-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/ca-certificates.make b/rules/ca-certificates.make
> index a667d2d26911..8eeec10865c8 100644
> --- a/rules/ca-certificates.make
> +++ b/rules/ca-certificates.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_CA_CERTIFICATES) += ca-certificates
> #
> # Paths and names
> #
> -CA_CERTIFICATES_VERSION := NSS_3_100_RTM
> -CA_CERTIFICATES_MD5 := c5dc443a649e31ebdb26243bbb5855ad
> +CA_CERTIFICATES_VERSION := NSS_3_101_RTM
> +CA_CERTIFICATES_MD5 := 429b34c077b1c133321e553266c552da
> CA_CERTIFICATES := ca-certificates-$(CA_CERTIFICATES_VERSION)
> CA_CERTIFICATES_SUFFIX := txt
> CA_CERTIFICATES_URL := https://hg.mozilla.org/projects/nss/raw-file/$(CA_CERTIFICATES_VERSION)/lib/ckfw/builtins/certdata.$(CA_CERTIFICATES_SUFFIX)
prev parent reply other threads:[~2024-06-15 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 19:14 [ptxdist] [PATCH] " Christian Melki
2024-06-10 19:14 ` [ptxdist] [PATCH] nss: " Christian Melki
2024-06-15 14:58 ` [ptxdist] [APPLIED] " Michael Olbrich
2024-06-15 14:58 ` Michael Olbrich [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=20240615145848.4136285-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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