Control: severity -1 serious Hi! Do yoy have any news about this issue?
After more than two years the error message is slightly different: The following NEW packages will be installed: collectd collectd-core 0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/1106 kB of archives. After this operation, 4135 kB of additional disk space will be used. Do you want to continue? [Y/n] Preconfiguring packages ... Selecting previously unselected package collectd-core. (Reading database ... 173831 files and directories currently installed.) Preparing to unpack .../collectd-core_5.7.1-1.1_amd64.deb ... Unpacking collectd-core (5.7.1-1.1) ... Selecting previously unselected package collectd. Preparing to unpack .../collectd_5.7.1-1.1_amd64.deb ... Unpacking collectd (5.7.1-1.1) ... Setting up collectd-core (5.7.1-1.1) ... Created symlink /etc/systemd/system/multi-user.target.wants/collectd.service -> /lib/systemd/system/collectd.service. Processing triggers for systemd (232-19) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up collectd (5.7.1-1.1) ... Job for collectd.service failed because the control process exited with error code. See "systemctl status collectd.service" and "journalctl -xe" for details. invoke-rc.d: initscript collectd, action "restart" failed. * collectd.service - Statistics collection and monitoring daemon Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sat 2017-03-25 10:35:21 CET; 8ms ago Docs: man:collectd(1) man:collectd.conf(5) https://collectd.org Process: 20181 ExecStartPre=/usr/sbin/collectd -t (code=exited, status=1/FAILURE) dpkg: error processing package collectd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: collectd E: Sub-process /usr/bin/dpkg returned an error code (1) but the result remains the same (uninstallable package) :( I think that this issue violates the Debian Policy (section 6.3), therefore I raise the severity of this bug to "serious" accordingly. Feel free to downgrade the bug severity as appropriate. Thanks.
