You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My Debian system is using sysvinit and elogind. This makes the debian packages fail to install due to their reliance on systemctl to start and stop the software.
Selecting previously unselected package rtpmidid.
(Reading database ... 755593 files and directories currently installed.)
Preparing to unpack rtpmidid_20.07_amd64.deb ...
Unpacking rtpmidid (20.07) ...
Setting up rtpmidid (20.07) ...
Adding user rtpmidid to group audio
/var/lib/dpkg/info/rtpmidid.postinst: 28: systemctl: not found
/var/lib/dpkg/info/rtpmidid.postinst: 29: systemctl: not found
dpkg: error processing package rtpmidid (--install):
installed rtpmidid package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
rtpmidid
I'd suggest checking that it exists and alerting the user that the program cannot be started automatically without systemd, or else maybe some LSB init scripts.
It looks like maybe you were attempting to do this, but at some point your postinst script got messed up. Line 27 of one of them currently reads: if [ -e /usr.
Alternatively you could make systemd | systemctl a hard dependency, but I'd personally rather you didn't since it's unnecessary. I just got it working on my system by rebuilding the debian package with some tweaks to postinst/prerm and a little setgid/setuid trickery (hopefully safe enough) to make rtpmidid run as the rtpmidid user and create a socket file with correct permissions (rtpmidid:audio ownership, I think).
Something like:
type systemctl
if [ $? -ne 0 ]; then
# handle systemctl not found
else
# systemctl commands
fi
Setting up /var/run/rtpmidid and the like would probably be left up to the user on such systems (unless a few more changes are made, anyway), so maybe that would be something to warn people about in the handling section.
The text was updated successfully, but these errors were encountered:
This is also problem on WSL2 (Windows Subsystem for Linux) in Windows 10, though it also lacks the /dev/snd/seq kernel driver - quess rtpmidid can't be easily implemented without ALSA sequencer support (instead of sequencer device some other interface or API would be needed).
My Debian system is using
sysvinit
andelogind
. This makes the debian packages fail to install due to their reliance onsystemctl
to start and stop the software.I'd suggest checking that it exists and alerting the user that the program cannot be started automatically without systemd, or else maybe some LSB init scripts.
It looks like maybe you were attempting to do this, but at some point your postinst script got messed up. Line 27 of one of them currently reads:
if [ -e /usr
.Alternatively you could make
systemd | systemctl
a hard dependency, but I'd personally rather you didn't since it's unnecessary. I just got it working on my system by rebuilding the debian package with some tweaks topostinst
/prerm
and a little setgid/setuid trickery (hopefully safe enough) to makertpmidid
run as thertpmidid
user and create a socket file with correct permissions (rtpmidid:audio
ownership, I think).Something like:
Setting up /var/run/rtpmidid and the like would probably be left up to the user on such systems (unless a few more changes are made, anyway), so maybe that would be something to warn people about in the handling section.
The text was updated successfully, but these errors were encountered: