Possible side effects of --enable-fhs and cfe_internal_update_policy_python_symlink
| Newsgroups | gmane.comp.sysutils.cfengine.general |
|---|---|
| Message-ID | <[email protected]> |
Hi everyone, we use the native Debian packages which are built with the --enable-fhs build option. This basically leads to sys.bindir being /usr/bin. Now in the process of updating our MPF from very old to current, I did run cf-agent -f ./update.cf and came across this problem: The policy in cfe_internal_update_policy_python_symlink however tries to find a valid python symlink target in all of PATH *except* for sys.bindir and therefore doesn't find anything and falls back to linking to /usr/libexec/platform-python. Now to add insult to injury, the policy finally wants to clean up by removing a stray "python" symlink but with sys.bindir being the system /usr/bin, it therefore removes /usr/bin/python which isn't very nice. ;) Does this problem seem valid? I suppose I can't Best regards, Moritz -- You received this message because you are subscribed to the Google Groups "help-cfengine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/help-cfengine/1b33c751-b14b-4af5-875e-e1dd42fcd8f5n%40googlegroups.com.