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-de...@lists.alioth.debian.org>
User: release.debian....@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)"
Thanks!
--
Some context for this construct (debian/README.source):
Native package shipping build of upstream code
----------------------------------------------
This is a Debian native package, yet is virtually empty and depends on
and essentially builds from a *-src package from an upstream project.
Reason for this construct is that the upstream project includes plugins
for a wide range for programming languages and frameworks, causing
headaches with transitions of those: By separating the build of each
uwsgi plugin, changes to Perl ABI, MongoDB ABI, PHP ABI, etc. can
transition independently of each other - and if a particular uwsgi
plugin shows problematic for a transition then it can be dropped
without affecting the rest of uwsgi.
