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.86 -> 3.87.
Date: Fri, 10 Feb 2023 15:17:18 +0100 [thread overview]
Message-ID: <20230210141718.3533866-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230206091012.1727700-1-christian.melki@t2data.com>
Thanks, applied as 67cebea4330e127614fe4dd8b0ac074729b9578c.
Michael
[sent from post-receive hook]
On Fri, 10 Feb 2023 15:17:17 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Actually, no changes to the raw cert textfile.
> Bump the version to the latest one anyway.
> This eliminates the question of "latest".
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230206091012.1727700-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 00014d60c5c4..17919347c97f 100644
> --- a/rules/ca-certificates.make
> +++ b/rules/ca-certificates.make
> @@ -14,7 +14,7 @@ PACKAGES-$(PTXCONF_CA_CERTIFICATES) += ca-certificates
> #
> # Paths and names
> #
> -CA_CERTIFICATES_VERSION := NSS_3_86_RTM
> +CA_CERTIFICATES_VERSION := NSS_3_87_RTM
> CA_CERTIFICATES_MD5 := a31809eb057bf80b67118f54a77b1856
> CA_CERTIFICATES := ca-certificates-$(CA_CERTIFICATES_VERSION)
> CA_CERTIFICATES_SUFFIX := txt
prev parent reply other threads:[~2023-02-10 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 9:10 [ptxdist] [PATCH] " Christian Melki
2023-02-06 9:10 ` [ptxdist] [PATCH] nss: " Christian Melki
2023-02-10 14:17 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-02-10 14:17 ` 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=20230210141718.3533866-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