Hi, On Thu, Dec 30, 2021 at 06:04:30AM -0300, Eppur Si Muove wrote: > I'm with this new installation of a virtual machine of Debian Testing, using > runit as init, > and I wanted to install mpd, but that process returned this: > ... > Configurando mpd (0.23.5-1+b1) ... > /etc/mpd.conf must have pid_file set; cannot stop daemon. ... failed! > invoke-rc.d: initscript mpd, action "restart" failed. > dpkg: erro ao processar o pacote mpd (--configure): > o subprocesso instalado, do pacote mpd, o script post-installation retornou > erro do status de saĆda 1 > Erros foram encontrados durante o processamento de: > mpd > E: Sub-process /usr/bin/dpkg returned an error code (1)
it becomes difficult to support systemd and alternative init systems at the same time. The /etc/mpd.conf file that comes with the package is configured to be used with systemd, and thus doesn't set pid_file or log_file any more. However the init script expects it to be there and won't run if it isn't. I might accept a patch to the initscript to not fail with the mpd.conf shipped by the package, but I won't have time to develop one myself. > I tried the following workaround: > - # reboot > - uncommented the line aboud PID file in /etc/mpd.conf > - # mkdir /run/mpd > - # touch /run/mpd/pid > - # chown mpd /run/mpd/pid > - # apt upgrade I would expect it to be enough to uncomment the pid_file line and run sudo dpkg --configure -a However if you weren't going to use and configure mpd just yet, I would expect leaving mpd.conf as-is and just disabling mpd should also do the trick: sudo update-rc.d disable mpd Florian