Hi Dave, I'm aware that systemd is available, but I'm not yet willing to switch this machine over, because I don't yet understand or trust systemd well enough.
You didn't answer my first question. Why was the init script removed? Was it broken and no longer feasible to maintain? As for my second question, you seem to have implied that the answer is "You can't". Please correct me if I'm wrong. The fact that sysvinit is still available in testing/unstable indicates to me that other programs should maintain compatibility, when reasonably possible. If there's an incompatibility, the user needs to be told about it; IMHO ideally through a package conflict. Currently, on systems running sysvinit, your package is non-functional after installation or upgrade, and no explanation is given. That's really not friendly. -- graham On 27 September 2015 at 10:15, Dave Steele <[email protected]> wrote: >> Why was the init script removed? How can I use this package with sysvinit? >> > > Debian stable/jessie supports systemd. Command to interact are e.g. > 'systemctl {start|stop|status} cloudprintd'. > > There is problem with running the latest versions of cloudprint on Jessie, > which is unrelated to OAuth2 and systemd. An updates release is in the > works. > > -- > "Le mieux est l'ennemi du bien" - Voltaire
