From: Zurab Kvachadze <zurabid2016@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: Zurab Kvachadze <zurabid2016@gmail.com>
Subject: [gentoo-dev] [PATCH 0/1] 2025-07-02-NGINX-packaging-changes: Add news item
Date: Thu, 3 Jul 2025 00:39:53 +0200 [thread overview]
Message-ID: <20250702223954.8462-1-zurabid2016@gmail.com> (raw)
This is a second revision of a NEWS item describing user-facing changes from
rebasing www-servers/nginx on top of nginx.eclass introduced in [1]. The patch
series can be accessed in [2].
The 1st revision of this NEWS item lives in [3].
nginx_upstream_check_module was one of the modules that was requested to be
ported. Unfortunately, due to the module requiring patching the system NGINX
server, it was impossible to add it as a separate package.
One possible solution for the affected users is to manually add the patches
under /etc/portage/patches and package nginx_upstream_check_module in their
private overlays (utilising nginx-module.eclass).
[1]: https://github.com/gentoo/gentoo/pull/37590
[2]: https://public-inbox.gentoo.org/gentoo-dev/20250702220705.4649-1-zurabid2016@gmail.com/
[3]: https://public-inbox.gentoo.org/gentoo-dev/20250221153621.26266-1-zurabid2016@gmail.com/
Zurab Kvachadze (1):
2025-07-02-NGINX-packaging-changes: Add news item
.../2025-07-02-NGINX-packaging-changes.txt | 124 ++++++++++++++++++
1 file changed, 124 insertions(+)
create mode 100644 2025-07-02-NGINX-packaging-changes/2025-07-02-NGINX-packaging-changes.txt
--
2.49.0
next reply other threads:[~2025-07-02 22:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 22:39 Zurab Kvachadze [this message]
2025-07-02 22:39 ` [gentoo-dev] [PATCH 1/1] 2025-07-02-NGINX-packaging-changes: Add news item Zurab Kvachadze
2025-07-02 22:43 ` [gentoo-dev] Re: [PATCH 0/1] " Zurab Kvachadze
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=20250702223954.8462-1-zurabid2016@gmail.com \
--to=zurabid2016@gmail.com \
--cc=gentoo-dev@lists.gentoo.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