Summary: | =sys-process/systemd-cron-1.5.10 references /usr/bin/systemctl | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Graham Murray <gmurray> |
Component: | Current packages | Assignee: | Richard Freeman <rich0> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ikelos, jstein, me, pacho, realnc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://github.com/systemd-cron/systemd-cron/pull/56 https://github.com/systemd-cron/systemd-cron/issues/54 https://github.com/gentoo/gentoo/pull/6365 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 625954 |
Description
Graham Murray
2017-07-17 10:02:42 UTC
it also installs 'systemd-crontab-generator' in '/usr/lib/systemd/system-generator/' instead of '/lib/systemd/system-generator/' This is reasonably easy to fix, it just requires inserting "--bindir ${EPREFIX}/bin \" into the src_configure phase. The hard part is figuring out whether the user is using >=systemd-234 or <systemd-234 as to whether to pass that flag... I think a couple changes need to happen upstream: 1. Remove the absolute path references to systemctl and let the shell (/bin/sh) find it in PATH. 2. Add independent configure options for the system unit dir and the system generator directories, instead of coupling them to libdir. Upstream bug: https://github.com/systemd-cron/systemd-cron/issues/54 As upstream bug looks to be stalled maybe we could, for now, simply make a new revision hard depending on >=234 and remember to stabilize that version when newer systemd is stabilized (In reply to Pacho Ramos from comment #5) > As upstream bug looks to be stalled maybe we could, for now, simply make a > new revision hard depending on >=234 and remember to stabilize that version > when newer systemd is stabilized IMO Mike's suggestion to just rely on PATH is the simpler one here. No harder to patch in than changing the location in the first place. It's ok if it is easy to do, I was wondering because this is the only one left with this breakage :/, but I don't care about what solution is chosen finally :) The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2919bd92a88850f39364f67a905bc02610361c00 commit 2919bd92a88850f39364f67a905bc02610361c00 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2017-12-09 18:21:41 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2017-12-09 18:22:20 +0000 sys-process/systemd-cron: bump to 1.5.12 Fixes rootprefix issues. Closes: https://bugs.gentoo.org/625400 Package-Manager: Portage-2.3.15, Repoman-2.3.6_p7 sys-process/systemd-cron/Manifest | 1 + .../systemd-cron/systemd-cron-1.5.12.ebuild | 75 ++++++++++++++++++++++ 2 files changed, 76 insertions(+) |