Bug#1104206: nmu: uwsgi-plugin-gccgo_0.0.3 uwsgi-plugin-glusterfs_0.0.3 uwsgi-plugin-java_0.0.5 uwsgi-plugin-lua_0.0.2 uwsgi-plugin-psgi_0.0.2 uwsgi-plugin-pypy_0.0.3 uwsgi-plugin-python_0.0.2 uwsgi-plugin-rados_0.0.3 uwsgi-plugin-ruby_0.0.2 uwsgi-plugin-php_0.0.15 uwsgi-plugin-luajit_0.0.8
- To: Alexandre Rossi <niol@zincube.net>, 1104206@bugs.debian.org
- Subject: Bug#1104206: nmu: uwsgi-plugin-gccgo_0.0.3 uwsgi-plugin-glusterfs_0.0.3 uwsgi-plugin-java_0.0.5 uwsgi-plugin-lua_0.0.2 uwsgi-plugin-psgi_0.0.2 uwsgi-plugin-pypy_0.0.3 uwsgi-plugin-python_0.0.2 uwsgi-plugin-rados_0.0.3 uwsgi-plugin-ruby_0.0.2 uwsgi-plugin-php_0.0.15 uwsgi-plugin-luajit_0.0.8
- From: Sebastian Ramacher <sramacher@debian.org>
- Date: Sat, 3 May 2025 17:18:45 +0200
- Message-id: <[🔎] aBYz1YZ0j1Z8jMmu@ramacher.at>
- Reply-to: Sebastian Ramacher <sramacher@debian.org>, 1104206@bugs.debian.org
- In-reply-to: <D9HB8F7F9NOV.1ZMEIE7JGUCZG@ripley>
- References: <D9HB8F7F9NOV.1ZMEIE7JGUCZG@ripley> <D9HB8F7F9NOV.1ZMEIE7JGUCZG@ripley>
Control: tags -1 forky
On 2025-04-27 11:23:07 +0200, Alexandre Rossi wrote:
> Package: release.debian.org
> Control: affects -1 + src:uwsgi-plugin-gccgo src:uwsgi-plugin-glusterfs src:uwsgi-plugin-java src:uwsgi-plugin-lua src:uwsgi-plugin-psgi src:uwsgi-plugin-pypy src:uwsgi-plugin-python src:uwsgi-plugin-rados src:uwsgi-plugin-ruby src:uwsgi-plugin-php src:uwsgi-plugin-luajit
> X-Debbugs-Cc: uWSGI packaging team <pkg-uwsgi-devel@lists.alioth.debian.org>
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> Severity: normal
>
> Hi,
>
> uwsgi.h has changed in the latest upstream, and externally built plugins need a
> rebuild to be aligned with this change.
>
> nmu uwsgi-plugin-gccgo_0.0.3 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
> nmu uwsgi-plugin-glusterfs_0.0.3 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
> nmu uwsgi-plugin-java_0.0.5 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
> nmu uwsgi-plugin-lua_0.0.2 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
> nmu uwsgi-plugin-luajit_0.0.8 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
> nmu uwsgi-plugin-psgi_0.0.2 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
> nmu uwsgi-plugin-pypy_0.0.3 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
> nmu uwsgi-plugin-python_0.0.2 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
> nmu uwsgi-plugin-rados_0.0.3 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
> nmu uwsgi-plugin-ruby_0.0.3 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
> nmu uwsgi-plugin-php_0.0.15 . ANY . unstable . -m "rebuild against latest uwsgi.h (API change)"
We are past the point of updates that are large or disruptive. Requiring
rebuilds of reverse dependencies falls into the later category. So
unless there is a very good reason, let's postpone this to forky.
Cheers
--
Sebastian Ramacher
Reply to: