Dear Maintainer(s),
clsync ships /etc/init.d/clsync but no corresponding native systemd
unit. This worked so far because systemd shipped a transitional
sysv-init-to-unit generator, which was removed upstream in v260.
systemd is now 261.2-1 in testing and 262~rc3-1 in unstable, so the
init script is already inert and the daemon no longer starts.
This was likely missed by the original mass bug filing because the
package does ship clsync@.service, so Lintian does not flag it. That
unit is not a replacement, it is a template running one instance per
config block (clsync -K %i) from /etc/clsync/clsync.conf, whereas the
init script runs a single daemon configured through $CLSYNC_ARGS in
/etc/default/clsync. Existing sysv users have no path to it without
rewriting their configuration.
What is needed is a plain clsync.service reproducing the init script,
Type=exec with -b0, EnvironmentFile=-/etc/default/clsync with
$CLSYNC_ARGS, IOSchedulingClass=idle in place of the ionice wrapper,
and ExecReload=/bin/kill -HUP $MAINPID. The init script can stay for
sysvinit users. CLSYNC_IONICE_CLASS cannot be carried over, as
IOSchedulingClass= does not expand variables.
I intend to prepare an NMU for this.
Nadzeya
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEuVOE/FJ0HcdfWSw//lAdKwFeZPsFAmqtgsQACgkQ/lAdKwFe
ZPuazg//R06qNDqGL5bYGgKDcc0tjx26ZKjUisv8eSvnwE6tpWipQ626bO4ikFA1
snomHUWj/f9yz4yom48C6mgi6VydnxvqDpcSNW8u98x7exBO8XsZJ34B2DwyLxiG
yBdnleR3kMf6OR3+RjcbJ42yHYC2Wu4EdP4LdHc8hYl73MJbpouGABvtGJJ9dK8c
m/kSDbysB3a14S5UaE+o/K848xmnsO2Sbv553atV3ulTYvEcgu45a9so6UxbHnsV
exfy9txfuTd4dpH1xEl4Vvwgj52tj5DnpGE1wOeU5zMja0G92Y/WoZc3k+dO/CTN
IYw7H83bMyPmQ78vOmYoCZpSWuG8OGMVTLntx61nHJRQrhfJI91t2AvpEoeifvRx
aJTybruTZFfU5x+At2ze1BG0kj0JF/WNX8MWqS720qFSzAvhSGRMbVig76MNhNGb
GLeyWEpGo+9KRgDCVk2lT10FstczgLChSYIywGsudIpbq3SiGuNfQm08ZhHqUbB7
QFBIJ9Mh50tO1RxXgicgXHF5mz4tYUkJWh1bY7R5za78QY8Ua1DEQZPsf6iqsNOC
7JOtpOoaJEP29z6sQHnm7mbCsVzWR7TgGdQQcryw+tkw3j+ZJTYm9Z+4NjH5z+bz
UhjgaIzByCQ+MLKt6ckHDgC6I3pvCv3OjsJgQSmEMqKGUps7F04=
=koJk
-----END PGP SIGNATURE-----