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

["Alexandre Rossi" <niol@zincube.net>]

Hi,

> > > src:uwsgi is currently blocked[2] from transitionning to testing, So now we have

[...]

> >
> > This misses the point. How does an update with 151 files changed, 2495
> > insertions(+), 3114 deletions(-) qualify as small and targetted fix?
>
> This analysis misses the fact that among those changes, most were already
> in debian/patches. Anyway, I understand that we have missed the 2025-04-15
> deadline and that rules must be enforced.

Sorry to come back to you on this, but now I think we need to do something about
this (for instance #1105144). I'm thus asking for an exception on this. I think
in the long term, having 2.0.29 in trixie will be less work for us (no need to
revert), the release team (no need to allow our reverted version into trixie)
and more importantly the security team (less gap with upstream during trixie
support). I think the risks are low for such slow moving software as uwsgi is.

Thanks for reconsidering,

Alex