Re: Possible side effects of --enable-fhs and cfe_internal_update_policy_python_symlink

OTOH, a possible solution IMO would probably include reverting 
https://github.com/cfengine/masterfiles/commit/d37c6d1929913d8cb9b269ce02ec823ade29b440 
which isn't really necessary anymore since 
https://github.com/cfengine/masterfiles/commit/a864d5cced81b37cf0f0ed9e61d392bd6ed96194 
right?

[email protected] schrieb am Freitag, 3. Februar 2023 um 16:37:30 UTC+1:

> 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/22b65f54-05f2-4b74-a70b-69e379e04c96n%40googlegroups.com.