Currently running Defender on SFOS Community edition on a PinePhone Pro and this dependency loop happens:
basic.targets depends on ...
paths.target which depends on ...
harbour-defender.path which depends on ..
home and unlocking home and all these things
which in turn depend on basic targets.
The recent systemd version in that SFOS version is actually able to detect the circular dependency, and solves it...
...by removing paths.target.
My suggestion would be to add DefaultDependencies=no in harbour's paths' units.
This way harbour's paths are started as part of paths.target, but there is no implicit "After=" in the target, thus it breaks the circular dependency, while the path is still scheduled for restart.
Currently running Defender on SFOS Community edition on a PinePhone Pro and this dependency loop happens:
The recent systemd version in that SFOS version is actually able to detect the circular dependency, and solves it... ...by removing paths.target.
My suggestion would be to add
DefaultDependencies=no
in harbour's paths' units. This way harbour's paths are started as part of paths.target, but there is no implicit "After=" in the target, thus it breaks the circular dependency, while the path is still scheduled for restart.I'll make a PR.