Re: invalid mode string error.

2009-12-04 Thread Mark Burgess
You have 3.0.2, and the Nova code is based on a frozen version of 3.0.3. No other differences. I have not had time to try this yet M nwat...@symcor.com wrote: > So Nova reports errors and community does not. Mark, does Nova perform > some stricter parsing that would account for this? > > Si

RE: invalid mode string error.

2009-12-04 Thread NWatson
So Nova reports errors and community does not. Mark, does Nova perform some stricter parsing that would account for this? Sincerely, -- Neil Watson 416-673-3465 CONFIDENTIALITY WARNING This communication, including any attachments, is for the exclusive use of addressee and may contain propri

RE: invalid mode string error.

2009-12-04 Thread Justin Lloyd
: help-cfengine-boun...@cfengine.org [mailto:help-cfengine-boun...@cfengine.org] On Behalf Of nwat...@symcor.com Sent: Friday, December 04, 2009 6:46 AM To: Nicolas Charles Cc: help-cfengine Subject: Re: invalid mode string error. Nicolas Charles wrote on 2009-12-03 09:20:07: > With the latest

Re: invalid mode string error.

2009-12-04 Thread NWatson
Nicolas Charles wrote on 2009-12-03 09:20:07: > With the latest svn build, on Ubuntu, seems to work find. > Here is the result : > # cf-agent -Kf ./foo.cf > R: ALARM: /etc/vim/vimrc wrong contents or perms 0644, root, root > R: /etc/vim/vimrc correct contents and perms 0644, root, root > I get

Re: invalid mode string error.

2009-12-03 Thread Nicolas Charles
ead parent. > https://cfengine.org/pipermail/help-cfengine/2009-December/006732.html > > Sincerely, > -- > Neil Watson > 416-673-3465 > > > > Mark Burgess > 2009-12-03 09:09 > > To > nwat...@symcor.com > cc > help-cfengine@cfengine.org > Subject

Re: invalid mode string error.

2009-12-03 Thread NWatson
It is attached to the thread parent. https://cfengine.org/pipermail/help-cfengine/2009-December/006732.html Sincerely, -- Neil Watson 416-673-3465 Mark Burgess 2009-12-03 09:09 To nwat...@symcor.com cc help-cfengine@cfengine.org Subject Re: invalid mode string error. Then you need to

Re: invalid mode string error.

2009-12-03 Thread Mark Burgess
Then you need to send your promises. nwat...@symcor.com wrote: > Could some folks kindly take a moment to attempt to duplicate my results > using either Nova or community? > > Sincerely, > -- > Neil Watson > 416-673-3465 > > Mark Burgess wrote on 2009-12-03 00:38:26: > >> Variables are not g

Re: invalid mode string error.

2009-12-03 Thread NWatson
Could some folks kindly take a moment to attempt to duplicate my results using either Nova or community? Sincerely, -- Neil Watson 416-673-3465 Mark Burgess wrote on 2009-12-03 00:38:26: > > Variables are not getting expanded / not defined. Hard to say more. > > nwat...@symcor.com wrote: > >

Re: invalid mode string error.

2009-12-02 Thread Mark Burgess
You can use {} or () for variables. Nicolas Charles wrote: > Hi Neil, > > Shouldn't it be $(mod) rather than ${mod} ? I guess the () are for > function parameters, whereas {} are for variables and classes, isn't it ? > > Regards, > Nicolas > > 2009/12/2 mailto:nwat...@symcor.com>> > > Any

Re: invalid mode string error.

2009-12-02 Thread Mark Burgess
Variables are not getting expanded / not defined. Hard to say more. nwat...@symcor.com wrote: > Anyone? > > Sincerely, > -- > Neil Watson > 416-673-3465 > > help-cfengine-boun...@cfengine.org wrote on 2009-12-01 21:07:40: > >> I've put together a test bundle for this. Nova gives out these err

Re: invalid mode string error.

2009-12-02 Thread Neil Watson
On Wed, Dec 02, 2009 at 04:17:29PM -0800, Mike Hoskins wrote: > Which has always been true, but for my own edification... Some bloggers > used to say the old 2.x parser was more easily confused by one form than > the other. I presume that is all fixed in 3.x, and does it even/still > hold f

Re: invalid mode string error.

2009-12-02 Thread Neil Watson
On Wed, Dec 02, 2009 at 04:17:29PM -0800, Mike Hoskins wrote: > Which has always been true, but for my own edification... Some bloggers > used to say the old 2.x parser was more easily confused by one form than > the other. I presume that is all fixed in 3.x, and does it even/still > hold f

Re: invalid mode string error.

2009-12-02 Thread Mike Hoskins
Neil Watson wrote: > On Wed, Dec 02, 2009 at 11:04:49PM +0100, Nicolas Charles wrote: >> Shouldn't it be $(mod) rather than ${mod} ? I guess the () are for >> function parameters, whereas {} are for variables and classes, isn't it > > {} and () can both be used to identify variables. Which ha

Re: invalid mode string error.

2009-12-02 Thread Neil Watson
On Wed, Dec 02, 2009 at 11:04:49PM +0100, Nicolas Charles wrote: > > Shouldn't it be $(mod) rather than ${mod} ? I guess the () are for > function parameters, whereas {} are for variables and classes, isn't it {} and () can both be used to identify variables. -- Neil Watson Linux/UNIX Consul

Re: invalid mode string error.

2009-12-02 Thread Nicolas Charles
Hi Neil, Shouldn't it be $(mod) rather than ${mod} ? I guess the () are for function parameters, whereas {} are for variables and classes, isn't it ? Regards, Nicolas 2009/12/2 > Anyone? > > Sincerely, > -- > Neil Watson > 416-673-3465 > > help-cfengine-boun...@cfengine.org wrote on 2009-12-01

Re: invalid mode string error.

2009-12-02 Thread NWatson
Anyone? Sincerely, -- Neil Watson 416-673-3465 help-cfengine-boun...@cfengine.org wrote on 2009-12-01 21:07:40: > I've put together a test bundle for this. Nova gives out these errors: > cf-promises -f ./foo.cf > Invalid mode string (${mod}) > Problem validating a mode string > Promise (version

Re: invalid mode string error.

2009-12-01 Thread Neil Watson
I've put together a test bundle for this. Nova gives out these errors: cf-promises -f ./foo.cf Invalid mode string (${mod}) Problem validating a mode string Promise (version not specified) belongs to bundle 'filecontents' in file './foo.cf' near line 50 Comment: ${cmt} Unknown user ${usr} Unknown