Package: qcontrol Version: 0.5.5-2 Severity: important Dear Maintainer,
I noticed that qcontrol daemon does not start at boot on a TS 212P running stretch. I see that in the list of supported models (/etc/qcontdol.conf) the 212P is missing but if I start the daemon manually (service qcontrold start) everything works. I assume the problem is not the model but something weird in the integration of qcontrol with systemd (I found that the same happened in jessie but I never used at that time). I put the severity to important because if you do not start it yourself (or do not hack the start method) the package is "unusable". I understand it is maybe a bit overstated. It is up to you to renormalize it. -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 4.9.0-6-marvell Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages qcontrol depends on: ii libc6 2.24-11+deb9u3 ii liblua5.1-0 5.1.5-8.1+b2 ii udev 232-25+deb9u2 qcontrol recommends no packages. qcontrol suggests no packages. -- no debconf information
