<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Ervin,</p>
<p>You conveniently left out my responses.</p>
<p><br>
</p>
<p><a class="moz-txt-link-freetext" href="https://alioth-lists.debian.net/pipermail/pkg-nginx-maintainers/2022q3/001903.html">https://alioth-lists.debian.net/pipermail/pkg-nginx-maintainers/2022q3/001903.html</a></p>
<p><a class="moz-txt-link-freetext" href="https://alioth-lists.debian.net/pipermail/pkg-nginx-maintainers/2022q3/001905.html">https://alioth-lists.debian.net/pipermail/pkg-nginx-maintainers/2022q3/001905.html</a></p>
<p><a class="moz-txt-link-freetext" href="https://alioth-lists.debian.net/pipermail/pkg-nginx-maintainers/2022q3/001910.html">https://alioth-lists.debian.net/pipermail/pkg-nginx-maintainers/2022q3/001910.html</a></p>
<p><br>
Then things got busy with all of us.<br>
</p>
<p>Because we're handling a dozen things at once, the first goal we
were going to have with NGINX currently in Debian is to take all
'upstream' modules we already ship that're third party and, where
doable, we will be converting those to dynamic modules in separate
packages and repositories. This way, we know everything works.</p>
<p>Once that's completed, we can look at 'adopting' other modules.
However, there is <b>nothing stopping you</b> from going to
Debian and upload your own source package with nginx mod security
packaged as a dynamic module like the Lua module is and such.
We'd like to be comaintaining the package in case we have to
trigger rebuilds or do a patch to the packaging because something
changed with nginx-dev or such, however that's not a hard
requirement.</p>
<p>If you wish for us to 'adopt' this, then you need to have
patience while we finish working on the nginx package as is before
we adopt any extra modules into our purview for packaging.</p>
<p><br>
</p>
<p>Thomas</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 11/11/22 11:05, Ervin Hegedüs wrote:<br>
</div>
<blockquote type="cite" cite="mid:20221111160504.rpdqbkeciocirrpj@arxnet.hu">
<pre class="moz-quote-pre" wrap="">Hi all,
On Fri, Nov 11, 2022 at 03:59:38PM +0100, Jan Mojzis wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">currently,
nginx and all modules distributed with it are compatible with PCRE2.
The last problem is with the libnginx-mod-http-lua module,
which PCRE2 does not support.
Issue here: <a class="moz-txt-link-freetext" href="https://github.com/openresty/lua-nginx-module/issues/1984">https://github.com/openresty/lua-nginx-module/issues/1984</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
it's good to know, thanks for information.
Few weeks ago I asked you (the team) about how can I add a new
Nginx module to the upstream?
Here is the e-mail:
<a class="moz-txt-link-freetext" href="https://alioth-lists.debian.net/pipermail/pkg-nginx-maintainers/2022q3/001902.html">https://alioth-lists.debian.net/pipermail/pkg-nginx-maintainers/2022q3/001902.html</a>
The introduced package (libnginx-mod-http-security) does not depend on any kind
of pcre packages, but the used "3rd-party" library depends: the
libmodsecurity3 needs pcre or pcre2. The current version of this
package still uses the old pcre library - do you think would it
be good to switch to pcre2?
Btw: is there any news about accepting of the mentioned package?
Thanks,
a.
_______________________________________________
Pkg-nginx-maintainers mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pkg-nginx-maintainers@alioth-lists.debian.net">Pkg-nginx-maintainers@alioth-lists.debian.net</a>
<a class="moz-txt-link-freetext" href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nginx-maintainers">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-nginx-maintainers</a>
</pre>
</blockquote>
</body>
</html>