Bug#766533: tlsdate cannot be started with systemd

2014-10-24 Thread Jacob Appelbaum
Thank you for testing! I plan to release a new tlsdate tonight - I'll tag a release and then poke h0lger to upload it tomorrow. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#766533: tlsdate cannot be started with systemd

2014-10-23 Thread Kill Your TV
On Thu, 23 Oct 2014 21:00:01 + (UTC) Jacob Appelbaum wrote: > I'm aware of this issue with the AUR package of tlsdate - thanks for > confirming it also impacts Debian! > > I'm planning a new upstream release for another minor fix - it will be > fixed in 0.0.12. > > Could you confirm that it

Bug#766533: tlsdate cannot be started with systemd

2014-10-23 Thread Jacob Appelbaum
I'm aware of this issue with the AUR package of tlsdate - thanks for confirming it also impacts Debian! I'm planning a new upstream release for another minor fix - it will be fixed in 0.0.12. Could you confirm that it works with the following service file: [Unit] Description=Secure parasitic rdat

Bug#766533: tlsdate cannot be started with systemd

2014-10-23 Thread Kill Your TV
Package: tlsdate Version: 0.0.11-2 Severity: normal On a Debian unstable system with systemd, updating tlsdate from 0.0.8-1 to 0.0.11-2 fails when systemd goes to start the daemon. I resolved this locally by changing Type=forking to Type=simple but I'm not sure that this is the proper "fix". Th