Control: severity -1 serious Hi,
> Looking at the init script I found that it specified the path to the > tlsdated binary as /etc/bin/tlsdated but the package installs the > binary to /usr/sbin/tlsdate. As such the init script is unable to > start as the specified binary isn't found. Reproduced. Thanks for reporting this bug to Debian. IMO, this is clearly RC: the initscript silently exits with return code 0, which makes one think that the service was successfully started, so the user has little chances to notice that there's an actual problem to fix, and leaves the system exposed to whatever problem or threat tlsdated was supposed to take care of. Raising severity accordingly. @RC bug hunters: this one seems to be trivially fixable by adding *one* char in the initscript. Enjoy. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
