After update from CFEngine 3.3.9 to 3.4.4 errors are reported for regular expressions at places that should NOT be parsed as regular expression in the first place. This happens with promises using edit_template and insert_lines. A simple test case will be attached. This and similar problems are reported in the CFEngine bug tracker: https://cfengine.com/dev/issues/1986 https://cfengine.com/dev/issues/1837 https://cfengine.com/dev/issues/1897 https://cfengine.com/dev/issues/2083 https://cfengine.com/dev/issues/1820 https://cfengine.com/dev/issues/1865 It seems the promises are kept in all cases, so the files are created as expected, but there are always this error messages without a reason, making it difficult to see the real errors. Reproducible: Always
Created attachment 344224 [details] emerge --info
Created attachment 344226 [details] Test case with promises for CFEngine
Created attachment 344228 [details] Template file for the test case
Having the test case as /tmp/test.cf and the template as /tmp/cfe-test.template the problem can be reproduced with: /usr/sbin/cf-agent --no-lock --file /tmp/test.cf Regular expression error "range out of order in character class" in expression "# This should be a comment without any expansions. [but this will give an error: mysql-5.1]!" at 87 Regular expression error "range out of order in character class" in expression "[This is ok? No: php-5.3.ini or so...]" at 21 Regular expression error "nothing to repeat" in expression "* also found in CFE-Bug#1820" at 0 Regular expression error "unmatched parentheses" in expression "And parenthesis ) are also a problem, at least single ones. I have them in security related strings like salts and encryption keys." at 16 R: CFE test ok
The upstream bugs #1897 and #2083 have been closed, so this should be fixed in the next 3.4.x release.
Re-assign to the new maintainer.
I bumped 3.4.4 to 3.4.5 is this fixed for you now?
Unfortunately net-misc/cfengine-3.4.5 does _not_ fix this issue, same errors as before. Seems the fix did not go into the 3.4.x version. Comment #20 here https://cfengine.com/dev/issues/2083#note-20 tells us: "Right now this commit lives in the master branch and so would more naturally lend itself to a 3.5.x release." So hopefully a later version will have this fixed.
Version 3.5.3 now in tree, so the issue should be fixed there, right? Please repoen if something is wrong...
