Oh well, sorry Nigel.

After posting I went to build from source and everything went
allright. Somehow I assumed facter was bundled in the puppet pkg.
Hopefully my next question won't be as stupid...

Thanks, Fabian

On 29 Apr., 16:40, Nigel Kersten <nig...@google.com> wrote:
> You need to install facter before puppet.
>
>
>
> On Wed, Apr 29, 2009 at 4:54 AM, fpeters <fabianpet...@googlemail.com> wrote:
>
> > Hi all,
>
> > I just learned about puppet the other day and thought it very
> > intriguing. Now I wanted to set up a test environment and dabble with
> > it. Unfortunately I'm running into the following on my test OSX 10.5.6
> > (Intel) install:
>
> > [ad...@osxclient ~] % puppetd -d
> > /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
> > 1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such
> > file to load -- facter (LoadError)
> >        from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/
> > ruby/1.8/rubygems/custom_require.rb:27:in `require'
> >        from /Library/Ruby/Site/1.8/puppet.rb:9
> >        from /usr/bin/puppetd:164:in `require'
> >        from /usr/bin/puppetd:164
>
> > The system is a clean install of 10.5.6 w/o developer tools. I
> > couldn't find any other references to this problem, but the very same
> > thing happens if I install on my own 10.5.6 machine (developer tools
> > installed).
>
> > Is there a known problem with the package I got from
> >https://sites.google.com/a/explanatorygap.net/puppet/?
>
> > cheers, Fabian
>
> --
> Nigel Kersten
> nig...@google.com
> System Administrator
> Google, Inc.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to