Bug#746606: tlsdate: incorrect path to tlsdated binary in /etc/init.d/tlsdate
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
Bug#746606: tlsdate: incorrect path to tlsdated binary in /etc/init.d/tlsdate
I am currently traveling in East Africa without access to my signing keys. Furthermore, those signing keys have expired and new keys will be generated in the near future after this trip. Pending a regeneration of key signatures from some other Debian developers, I'll upload a fix. If anyone wants to fix the init script before that time, I'd be more than happy to review a fix. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746606: tlsdate: incorrect path to tlsdated binary in /etc/init.d/tlsdate
Package: tlsdate Version: 0.0.7-1 Severity: important Dear Maintainer, After installing tlsdate I was unable to use the init script to start the tlsdated daemon. 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. Updating the path in the init script allows me to start the tlsdated daemon. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tlsdate depends on: ii libc62.18-5 ii libssl1.0.0 1.0.1g-3 tlsdate recommends no packages. Versions of packages tlsdate suggests: pn apparmor none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
