Package: uwsgi-emperor
Version: 2.0.18-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After installing uwsgi-emperor 2.0.18 it's impossible to change the
running state of the service, as the provided init-script is doing
nothing. This can be easily seen by the script being all of 27 lines
long, ending just after setting up the variables, where the one from the
2.0.7 version has a total of 136 lines.

As there is no SystemD unit present (as discussed in #833067) this means
there is actually no way to start this service.

Checking, it seems that this issue is also present in 2.0.14 from
stretch, and is present in 2.0.19 for bullseye.

-- System Information:
Debian Release: 10.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (90, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages uwsgi-emperor depends on:
ii  uwsgi-core  2.0.18-1

uwsgi-emperor recommends no packages.

uwsgi-emperor suggests no packages.

-- Configuration Files:
/etc/default/uwsgi-emperor changed [not included]

-- no debconf information

Reply via email to