mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
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.88 -> 3.89.
Date: Thu, 16 Mar 2023 15:31:30 +0100	[thread overview]
Message-ID: <20230316143130.3681699-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230312091000.3208564-1-christian.melki@t2data.com>

Thanks, applied as 6d5992be3917eeef6e53aa5080fb34a16ad482fc.

Michael

[sent from post-receive hook]

On Thu, 16 Mar 2023 15:31:30 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Same as last, 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: <20230312091000.3208564-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 5d5e8fbd52b6..54170c757349 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_88_RTM
> +CA_CERTIFICATES_VERSION		:= NSS_3_89_RTM
>  CA_CERTIFICATES_MD5		:= a31809eb057bf80b67118f54a77b1856
>  CA_CERTIFICATES			:= ca-certificates-$(CA_CERTIFICATES_VERSION)
>  CA_CERTIFICATES_SUFFIX		:= txt



      reply	other threads:[~2023-03-16 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12  9:10 [ptxdist] [PATCH] " Christian Melki
2023-03-16 14:31 ` 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=20230316143130.3681699-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