From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/nginx: security update to 1.26.1
Date: Mon, 5 Aug 2024 22:40:59 +0200 [thread overview]
Message-ID: <20240805224059.4494a56b@windsurf> (raw)
In-Reply-To: <ZrDeobsGFJYy4gL/@waldemar-brodkorb.de>
On Mon, 5 Aug 2024 16:16:01 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> See here for a Changelog and CVE's:
> http://nginx.org/en/CHANGES-1.26
>
> Patch 0006 is no longer required as the openssl library is found without
> this patch, which does not apply anymore.
>
> Patch 0009 is no longer required as it was fixed in another way upstream:
> https://hg.nginx.org/nginx/rev/fb989e24c60a
>
> Patch 0011 is upstream:
> https://hg.nginx.org/nginx/rev/f58b6f636238
>
> Reorder the remaining patches and update .checkpackageignore accordingly.
>
> The LICENSE file is changed, the year changed from 2022 to 2024.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> v1->v2:
> - forgot to update LICENSE file hash and information about the
> changes (requested by Thomas P.)
> ---
> .checkpackageignore | 8 +-
> ...-auto-lib-libgd-conf-use-pkg-config.patch} | 0
> ...auto-lib-openssl-conf-use-pkg-config.patch | 251 ------------------
> ...inux_config.h-only-include-dlfcn.h-.patch} | 0
> ...of-endianness-for-cross-compilation.patch} | 0
> ...to-os-linux-fix-build-with-libxcrypt.patch | 38 ---
> ...ix-compile-error-in-configure-script.patch | 33 ---
> package/nginx/nginx.hash | 4 +-
> package/nginx/nginx.mk | 2 +-
> 9 files changed, 6 insertions(+), 330 deletions(-)
> rename package/nginx/{0007-auto-lib-libgd-conf-use-pkg-config.patch => 0006-auto-lib-libgd-conf-use-pkg-config.patch} (100%)
> delete mode 100644 package/nginx/0006-auto-lib-openssl-conf-use-pkg-config.patch
> rename package/nginx/{0008-src-os-unix-ngx_linux_config.h-only-include-dlfcn.h-.patch => 0007-src-os-unix-ngx_linux_config.h-only-include-dlfcn.h-.patch} (100%)
> rename package/nginx/{0010-Allow-forcing-of-endianness-for-cross-compilation.patch => 0008-Allow-forcing-of-endianness-for-cross-compilation.patch} (100%)
> delete mode 100644 package/nginx/0009-auto-os-linux-fix-build-with-libxcrypt.patch
> delete mode 100644 package/nginx/0011-Fix-compile-error-in-configure-script.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-08-05 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 14:16 [Buildroot] [PATCH v2] package/nginx: security update to 1.26.1 Waldemar Brodkorb
2024-08-05 20:40 ` Thomas Petazzoni via buildroot [this message]
2024-09-03 18:58 ` Peter Korsgaard
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=20240805224059.4494a56b@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.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