On Thursday, January 10, 2013 5:58:02 AM UTC+11, Andy Parker wrote:
>
>
> Yeah, we've been finding these things. There are quite a few settings that
> are defined in there, but don't actually get used. Josh and I were looking
> into some of those, and I just had a conversation with him about sign
I'm not sure what was wrong on my dev system. My best guess is it had
something to do with having Puppet installed previously via RPM. I loaded a
new system without Puppet, downloaded the source and only got 8 errors. Still
more than I was expecting, but at least a manageable number to debug.
OK, I ran it as a non-root user and that did clear up some of the errors. All
of the permission denied presumably. I am still getting a lot of errors that
indicate a "File not found"
Here's another example error
john@linux3 [/usr/local/dev/puppetsrc/puppet]
$ rspec ./spec/unit/transaction/res
Are you running the tests as root? The problem may be that Puppet is
giving up permissions and as a result cannot read from the temporary
directories created earlier as root.
Do you have this problem if you run the tests as a non-root user?
-Jeff
On Sun, Jan 13, 2013 at 1:02 PM, John Julien w
Hi,
I'm working on https://projects.puppetlabs.com/issues/7911 (Can't handle
local users in LDAP environment)
My original thought was to add the parameter "forcelocal" to the
useradd/groupadd providers. My plan is to use the luseradd and lgroupadd
commands utilizing a stripped down libuser.co
Hi,
I am attempting to run the rspec tests on a freshly forked copy of Puppet
from master.
I was expecting a 100% success rate since I read no pull requests are
merged unless they pass these tests. I'm wondering if there might be
something I'm missing in the setup of my dev environment becau
