Hi,
I've just taken a look at this issue together with someone else during
the Montreal BSP and we think that the init script is possibly the
source of the problem:
the stop action fails if it is called when the service is not running,
which is the case when you install the package on a new system.
the init script should rather exit cleanly if start-stop-daemon --stop
reports that it failed because the daemon is not running, e.g. ignore
exit code 1 from start-stop-daemon.
however, when we tried to apply a modification to the init script, we
tried to build the package to verify that our solution works but we were
unable to even build it. there are multiple patches in debian/patches/
that currently do not apply cleanly.
e.g.
$ dpkg-buildpackage
dpkg-buildpackage: info: source package timidity
dpkg-buildpackage: info: source version 2.14.0-9
dpkg-buildpackage: info: source distribution UNRELEASED
dpkg-buildpackage: info: source changed by Bastien Roucariès
<ro...@debian.org>
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build .
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying
0001-don-t-url_unexpand_home_dir-when-opening-a-file.patch
dpkg-source: info: applying 0002-improve-error-message.patch
patching file timidity/timidity.c
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored
dpkg-source: info: the patch has fuzz which is not allowed, or is malformed
dpkg-source: info: if patch '0002-improve-error-message.patch' is
correctly applied by quilt, use 'quilt refresh' to update it
dpkg-source: info: if the file is present in the unpacked source, make
sure it is also present in the orig tarball
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B
.pc/0002-improve-error-message.patch/ --reject-file=- <
timidity/debian/patches/0002-improve-error-message.patch subprocess
returned exit status 1
dpkg-buildpackage: error: dpkg-source --before-build . subprocess
returned exit status 2
