Short version: upstream tinc 1.0.28 introduces systemd services files. Because python-dnspython is (right now) not available from stable but only from backports, tinc will also be installed from backports version 1.0.28-1~bpo8+1 instead of stable version 1.0.24-2.1+b1, thus using the upstream systemd services files.
The problem is, tinc won't start from systemd - but works fine when started manually.
Pull #194 has 4473fc73691376288d4a41c2796a9a469ea8e460 which ensures tinc is installed from stable.
I have a feeling that upstream tinc is not the giulty here, it might be the way we use systemd that is wrong. This issue is created to track down this behaviour, if/whenever this behaviour happens again.
Short version: upstream tinc 1.0.28 introduces systemd services files. Because
python-dnspythonis (right now) not available fromstablebut only frombackports, tinc will also be installed frombackportsversion1.0.28-1~bpo8+1instead ofstableversion1.0.24-2.1+b1, thus using the upstream systemd services files.The problem is, tinc won't start from systemd - but works fine when started manually.
Pull #194 has 4473fc73691376288d4a41c2796a9a469ea8e460 which ensures tinc is installed from
stable.I have a feeling that upstream tinc is not the giulty here, it might be the way we use systemd that is wrong. This issue is created to track down this behaviour, if/whenever this behaviour happens again.