On Thu, Nov 11, 2010 at 6:43 PM, donavan wrote:
> On Nov 11, 2:15 am, Daniel Pittman wrote:
>> Leonko writes:
>>
>> I think it is mentioned obliquely a few times, but there certainly isn't
>> anywhere super-obvious that explains this feature of manifest auto-loading.
>
> Yes, +1 to an issue for
On Nov 11, 2:15 am, Daniel Pittman wrote:
> Leonko writes:
>
> I think it is mentioned obliquely a few times, but there certainly isn't
> anywhere super-obvious that explains this feature of manifest auto-loading.
Yes, +1 to an issue for documenting it. That said #5044 is the best
explanation of
Leonko writes:
I think it is mentioned obliquely a few times, but there certainly isn't
anywhere super-obvious that explains this feature of manifest auto-loading.
It would be great if you could file a bug report about that, so that this can
be fixed and avoid someone else hitting the same issue
Thank you. Now it's work. But why in documentation is nothing about it?
Leonid S. Batizhevsky
On Thu, Nov 11, 2010 at 12:02, luke.bigum wrote:
> Try rename:
>
> modules/postgresql/
>
> to:
>
> modules/postgres/
>
> so it matches the name of your class.
>
--
You received this message because y
Try rename:
modules/postgresql/
to:
modules/postgres/
so it matches the name of your class.
On Nov 11, 8:54 am, Leonko wrote:
> Hello. I use puppet 2.6.3-rc2
> Now I try move my classes to modules.
> But I got a problem that Puppet does not sees modules.
>
> in puppet.conf:
>
> [main]
> l
