Hi good folks of gentoo. In the current release 1.2.0 of net-nntp/sabnzbd the systemd unit is broken. The ExecStart path is wrong: ExecStart=/usr/bin/sabnzbd --logging 1 --browser 0 /usr/bin/sabnzbd does not exist. The correct entry would be ExecStart=/usr/share/sabnzbd/SABnzbd.py --logging 1 --browser 0 (or symlink /usr/bin/sabnzbd to /usr/share/sabnzbd/SABnzbd.py - whatever makes more sense to the package maintainer) Reproducible: Always Steps to Reproduce: 1. emerge net-nntp/sabnzbd 2. systemctl start sabnzbd@user Actual Results: Feb 27 18:40:35 nas systemd[14366]: sabnzbd@mike.service: Failed at step EXEC spawning /usr/bin/sabnzbd: No such file or directory Feb 27 18:40:35 nas systemd[1]: sabnzbd@mike.service: Main process exited, code=exited, status=203/EXEC Feb 27 18:40:35 nas systemd[1]: sabnzbd@mike.service: Unit entered failed state. Feb 27 18:40:35 nas systemd[1]: sabnzbd@mike.service: Failed with result 'exit-code'. Expected Results: running service
commit 16437399ccd527c7e1b47d6efc7e2136f0d0e8e3 Author: Justin Bronder <jsbronder@gentoo.org> Date: Thu Mar 9 16:46:28 2017 -0500 net-nntp/sabnzbd: bump and systemd fix bump: #611438, thanks to Sébastien P. systemd fix: #611128, thanks to Michael Hampicke. Package-Manager: portage-2.3.3
