Re: Using absolute path for ExecStart in espeakup.service

[john doe <johndoe65534@mail.com>]

On 1/10/2019 9:31 PM, Samuel Thibault wrote:
> Hello,
>
> john doe, le jeu. 10 janv. 2019 18:09:35 +0100, a ecrit:
>> According to the below message and to (1, 'execstart=') the command
>> 'ExecStart' should use a fully qualified path when 'execstop=' is not
>> specified.
>
>> Observed on Debian Stretch.
>
> This is fixed in stretch-proposed-updates's version 1:0.80-5+deb9u3, to
> be included in next Scretch.
>

While upgrading espeakup to that version I get:

Preparing to unpack .../42-espeakup_1%3a0.80-5+deb9u3_amd64.deb ...
Failed to stop espeakup.service: Unit espeakup.service not loaded.
invoke-rc.d: initscript espeakup, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit
status 5
dpkg: trying script from the new package instead ...
Failed to stop espeakup.service: Unit espeakup.service not loaded.
invoke-rc.d: initscript espeakup, action "stop" failed.
dpkg: error processing archive
/tmp/apt-dpkg-install-aCTNxk/42-espeakup_1%3a0.80-5+deb9u3_amd64.deb
(--unpack):
 subprocess new pre-removal script returned error exit status 5
update-rc.d: warning: start and stop actions are no longer supported;
falling back to defaults
Errors were encountered while processing:
 /tmp/apt-dpkg-install-aCTNxk/42-espeakup_1%3a0.80-5+deb9u3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

--
John Doe