[pkg-uWSGI-devel] Bug#1039408: uwsgi: ships sysv-init script without systemd unit

[Luca Boccassi]

On Thu, 31 Aug 2023 at 07:45, Alexandre Rossi <niol at zincube.net> wrote:
>
> Hi,
>
> > uwsgi has been flagged by Lintian as shipping a sysv-init script
> > without a corresponding systemd unit file. The default init system in
> > Debian is systemd, and so far this worked because a transitional
> > sysv-init-to-unit generator was shipped by systemd. This is in the
> > process of being deprecated and will be removed by the time Trixie
> > ships, so the remaining packages that ship init scripts without
> > systemd units will stop working.
>
> [...]
>
> > In case this is a false positive, please add a Lintian override to
> > silence it and then close this bug.
>
> My view on this is that the following template units provided by
> uwsgi-core enable the initscript functionality.
>
>     /lib/systemd/system/uwsgi-app at .service
>     /lib/systemd/system/uwsgi-app at .socket
>
> See full change[1] for documentation.
>
> From the initscript documentation[2] and a quick look at the script,
> it seems that it manages multiple uwsgi services from a
> directory of configuration files. I think think if using systemd
> that it is better managed using template units.
>
> The above template lack supports for multiple type of configuration
> files, assume INI, but this is easily fixable by overriding
> the units.
>
> uwsgi-emperor[3], from my understanding, does the same, and thus
> does not need an initscript or systemd service unit.
>
> My conclusion is that this is already fixed and that a lintian
> override is relevant here, but I do not know if I'm missing something.

Thanks for looking into this, it definitely sounds like a false
positive - Lintian just does a 1:1 name matching I think. So please do
add a Lintian override for it and close this bug.