package: tlsdate
severity: important

Hi,

lintian shows this problem in tlsdate:

E: tlsdate: systemd-no-service-for-init-script tlsdate
N: 
N:    The listed init.d script has no systemd equivalent.
N:    
N:    Systemd has a SysV init.d script compatibility mode. It provides access
N:    to each SysV init.d script as long as there is no native service file
N:    with the same name (e.g. /lib/systemd/system/rsyslog.service corresponds
N:    to /etc/init.d/rsyslog).
N:    
N:    Your package ships a service file, but for the listed init.d script,
N:    there is no corresponding systemd service file.
N:    
N:    Severity: serious, Certainty: certain
N:    
N:    Check: systemd, Type: binary

This is because the init script is called "tlsdate", while the systemd service  
file is called "tlsdated".

I'd recommend to renamed the initscript to "tlsdated" too.

And I'm too lazy to check whether this results in tlsdate started twice on 
systems running systemd, but I strongly suspect so, thus the severity.


cheers,
        Holger

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to