Aleksey,
It could be that the RPM package you installed contained a custom
library.cf, which contained some things from cfengine_stdlib.cf plus
some additional definitions (which are now missing since you removed
library.cf). I guess you could try copying the missing definitions (e.g.
def(), upgrade_cfexecd(), DeleteLinesMatching(), as per the errors
below) into your policy files (maybe create your own version of
library.cf, and include it alongside cfengine_stdlib.cf). You may need
to repeat the process a few times to get all the dependencies copied over.
--Diego
On 9/20/2010 1:36 AM, Aleksey Tsalolikhin wrote:
> On Sun, Sep 19, 2010 at 11:23 PM, Mark Burgess<mark.burg...@iu.hio.no> wrote:
>> library.cf is an old version of stdlib, you don't need both, so I would take
>> out the
>> librart.cf which probably has some dual definitions.
>>
>> M
> Dear Mark,
>
> Thank you. I tried taking out library.cf and putting
> cfengine_stlib.cf in its stead. No go.
>
>
>
> cf3:/var/cfengine/inputs/cfengine_stdlib.cf:371,1: Redefinition of
> body immediate for action is a broken promise, near token '{'
> Undeclared promise body "def()" was referenced in a promise
> Undeclared promise bundle "upgrade_cfexecd()" was referenced in a promise
> Undeclared promise bundle "DeleteLinesMatching()" was referenced in a promise
> body "longjob()" was undeclared, but used in a promise near line 68 of
> /var/cfengine/inputs/site.cf
> body "WarnOnly()" was undeclared, but used in a promise near line 76
> of /var/cfengine/inputs/site.cf
> body "upgrade_cfexecd()" was undeclared, but used in a promise near
> line 84 of /var/cfengine/inputs/site.cf
> body "def()" was undeclared, but used in a promise near line 113 of
> /var/cfengine/inputs/site.cf
> ...
> cf-agent was not able to get confirmation of promises from
> cf-promises, so going to failsafe
>
>
> My promises.cf came straight from
> /usr/local/share/doc/cfengine/inputs/promises.cf
>
> Here it is, with the edit:
>
>
>
> body common control
>
> {
> bundlesequence => {
> "update",
> "garbage_collection",
> "main",
> "cfengine",
> };
>
>
> inputs => {
> "update.cf",
> "site.cf",
> "cfengine_stdlib.cf", # this was library.cf
> };
>
> }
>
> The product I am trying to get is: cfengine 3 running cfagent and
> cf-agent; keep running my cfengine 2 policies and allow me to
> gradually migrate cfengine 2 policies to cfengine 3 promises (and I
> need COPBL for cfengine 3 promises).
>
> Truly,
> -at
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@cfengine.org
> https://cfengine.org/mailman/listinfo/help-cfengine
_______________________________________________
Help-cfengine mailing list
Help-cfengine@cfengine.org
https://cfengine.org/mailman/listinfo/help-cfengine
