Package: uwsgi-emperor Version: 2.0.19.1-3 Followup-For: Bug #969372 Dear Maintainer,
it seems this bug still exists in 2.0.19.1-3. I've upgraded from 2.0.19.1-1 this morning and since then the uwsgi-emperor can't be started using systemd or /etc/init.d/uwsgi-emperor script. I tried to purge and install the uwsgi-emperor package. The /etc/init.d/uwsgi-emperor still seems to be broken. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (90, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages uwsgi-emperor depends on: ii uwsgi-core 2.0.19.1-3 uwsgi-emperor recommends no packages. uwsgi-emperor suggests no packages. -- no debconf information
