From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] nss: Version bump. 3.121 -> 3.123
Date: Mon, 27 Apr 2026 09:46:02 +0200 [thread overview]
Message-ID: <20260427074602.52149-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260418154522.161049-1-christian.melki@t2data.com>
Thanks, applied as 0837d5b974048c300619246b20049e7e2ecb1d6e.
Michael
[sent from post-receive hook]
On Mon, 27 Apr 2026 09:46:02 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Various bug fixes.
> https://firefox-source-docs.mozilla.org/security/nss/releases/nss_3_123.html
> https://firefox-source-docs.mozilla.org/security/nss/releases/nss_3_122.html
>
> * Forward patchset, applies cleanly.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260418154522.161049-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/nss-3.121/0001-nss-fix-nsinstall-build.patch b/patches/nss-3.123/0001-nss-fix-nsinstall-build.patch
> similarity index 100%
> rename from patches/nss-3.121/0001-nss-fix-nsinstall-build.patch
> rename to patches/nss-3.123/0001-nss-fix-nsinstall-build.patch
> diff --git a/patches/nss-3.121/0002-add-nss.pc.in.patch b/patches/nss-3.123/0002-add-nss.pc.in.patch
> similarity index 100%
> rename from patches/nss-3.121/0002-add-nss.pc.in.patch
> rename to patches/nss-3.123/0002-add-nss.pc.in.patch
> diff --git a/patches/nss-3.121/0003-HACK-don-t-build-commands-that-need-zlib.patch b/patches/nss-3.123/0003-HACK-don-t-build-commands-that-need-zlib.patch
> similarity index 100%
> rename from patches/nss-3.121/0003-HACK-don-t-build-commands-that-need-zlib.patch
> rename to patches/nss-3.123/0003-HACK-don-t-build-commands-that-need-zlib.patch
> diff --git a/patches/nss-3.121/0004-HACK-fix-parallel-building-issue.patch b/patches/nss-3.123/0004-HACK-fix-parallel-building-issue.patch
> similarity index 100%
> rename from patches/nss-3.121/0004-HACK-fix-parallel-building-issue.patch
> rename to patches/nss-3.123/0004-HACK-fix-parallel-building-issue.patch
> diff --git a/patches/nss-3.121/0005-fix-dependency-generation.patch b/patches/nss-3.123/0005-fix-dependency-generation.patch
> similarity index 100%
> rename from patches/nss-3.121/0005-fix-dependency-generation.patch
> rename to patches/nss-3.123/0005-fix-dependency-generation.patch
> diff --git a/patches/nss-3.121/series b/patches/nss-3.123/series
> similarity index 100%
> rename from patches/nss-3.121/series
> rename to patches/nss-3.123/series
> diff --git a/rules/nss.make b/rules/nss.make
> index dd0f33695b9b..b4866e819b5c 100644
> --- a/rules/nss.make
> +++ b/rules/nss.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_NSS) += nss
> #
> # Paths and names
> #
> -NSS_VERSION := 3.121
> -NSS_MD5 := c26dbbc863c69008be8851be2e37ece8
> +NSS_VERSION := 3.123
> +NSS_MD5 := 6d9bb1f18abf0241fd99f7721723c07d
> NSS := nss-$(NSS_VERSION)
> NSS_SUFFIX := tar.gz
> NSS_URL := https://ftp.mozilla.org/pub/security/nss/releases/NSS_$(subst .,_,$(NSS_VERSION))_RTM/src/$(NSS).$(NSS_SUFFIX)
prev parent reply other threads:[~2026-04-27 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 15:45 [ptxdist] [PATCH] " Christian Melki
2026-04-27 7:46 ` 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=20260427074602.52149-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