the ebuild explicitly calls configure as: .. --with-systemd=/usr/$(get_libdir)/systemd/system .. which obviously causes systemd-service files to be installed into /usr/lib/systemd/system Fix is trivial by omitting the path override: .. --with-systemd .. (alas this easy fix will break tinc with "legacy" <sys-apps/systemd-234 ..) Blocks: #625954 Reproducible: Always
/usr/$(get_libdir)/systemd/system is wrong already: the get_libdir call will return "lib64" on amd64, whereas the units should end up in "lib". I suggest updating this to: inherit systemd --with-systemd="$(systemd_get_systemunitdir)"
[master a25c68784d7] net-vpn/tinc: Fix systemd units installation to not hardcode paths (#634650 by Mike Gilbert) 2 files changed, 3 insertions(+), 3 deletions(-)