Package: systemd Version: 235-3 Severity: important Tags: patch upstream fixed-upstream
After upgrading to systemd 235-3 I ran into the exact issue described at https://github.com/systemd/systemd/issues/7055 That is, systemd segfaults when trying to start a unit that makes use of BindPaths or BindReadOnlyPaths. Fortunately it's the child process that segfaults, not the main systemd process itself - but it still makes it impossible to start the unit. A trivial one-line fix is available at https://github.com/yuwata/systemd/commit/a8cabc612b16834260831a8163ae4b479b5c33a5 In the mean time, a workaround is to rollback to systemd 234-3. _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
