Re: [etch-users] New user of etch having difficulty getting etch-3.19.0 to work

[Jason H. <jh...@ap...>]

A follow-up note:  I noticed that you're running under ruby 1.9.  That's the reason you're the first to stumble upon this issue, as Find.find in ruby 1.8 doesn't complain if you ask it to look at a directory that doesn't exist.

To be honest I had not yet tested etch under ruby 1.9, but you've just reminded me that I needed to do so.  The first pass resulted in 5 errors from the etch test suite.  None look terribly fatal for normal operations, so you're probably fine.  There are some ugly warnings from some of the gems and libraries that etch uses, I'll hide those in the next release.

Jason

On May 3, 2011, at 9:33 PM, Jason Heiss wrote:

> Looking at line etch.rb:173 it looks like /etc/etchserver/source doesn't exist.  That's the directory where configuration for files that you want etch to manage would live.  I.e. if you want etch to manage /etc/motd then the configuration for that would live in /etc/etchserver/source/etc/motd/
> 
> On May 3, 2011, at 12:20 PM, Johnston, Nathaniel wrote:
> 
>> /opt/ruby/ruby-1.9.2-p180/lib/ruby/1.9.1/find.rb:38:in `block in find'