Sebastian,
So, this is caused by symlinks in this module which don't have a
corresponding directory or file. Puppet 3.7.0 now checks for symlinks, and
unfortunately has a File Not Found error if the symlinks don't have a
corresponding target.
My only suggestion for working around this is to do
; On Fri, Sep 5, 2014 at 3:44 PM, Anderson Mills > wrote:
>
>> Sebastian,
>>
>> So, this is caused by symlinks in this module which don't have a
>> corresponding directory or file. Puppet 3.7.0 now checks for symlinks, and
>> unfortunately has a File
Stefan,
The answer is that dashes are preferred, but we recognized that this has
been ambiguous for a long time, so the code permits both "/" and "-".
This bug (unresolved dependencies if they are specified with a "-") was
addressed in PUP-3121 as you mentioned, but the fix version for that tic
Hello Gabriel,
The ticket that you reference has a link on it to a pull request which was
merged into Puppet 4.x.
https://github.com/puppetlabs/puppet/pull/3310
It is not intended that this will be fixed in Puppet 3.x.
As for deprecation, though it is a thorn in our side, removing support for
I believe moduledir should be set in the Puppetfile, not in r10k.yaml. (Or
was that a mistype?)
https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#moduledir
On Friday, June 17, 2016 at 3:15:28 PM UTC-7, Michael Watters wrote:
>
> I actually take the opposite approach. Modules fro
Jonathan,
What happens if you use
puppet-code deploy --all --wait
???
On Tuesday, November 29, 2016 at 9:48:36 AM UTC-6, Jonathan Gazeley wrote:
>
> I'm dabbling with a new PE 2016.4 installation as I'm hoping to finally
> migrate away from Puppet 3.
>
> We're using code manager rather than
Since v2.4.0, r10k allows data to be directed into a specific :install_path
from a git repo in the Puppetfile.
See
https://github.com/puppetlabs/r10k/blob/master/doc/puppetfile.mkd#per-item-install-path
If you have a separate repo of your "files", you could load that into a
directory in the en
James,
I also think that the PMT is operating as expected, in that it is ignoring
the dependencies of the module you are trying to install, stahnma-epel
v1.0.2. --ignore-dependencies does not tell it to ignore dependencies of
already installed modules.
I believe the behavior you're looking fo
Vijayabalan,
So the Puppetfile for r10k is not the same as for Librarian-puppet, and
there is no :path key for a mod in r10k.
You'll either have to keep them in a repo and specify a :git key, or pull
them from the forge.
Docs for r10k's use of Puppetfile!
https://docs.puppetlabs.com/pe/latest
Spriya,
This error is telling you that you have a production environment in both
your testing: and development: sources.
You cannot have the exact same environment in more than one source. To fix
this, either change the name of one environment, which is controlled by the
branch names in your c
n
On Friday, May 22, 2015 at 10:05:40 AM UTC-7, Anderson Mills wrote:
>
> Spriya,
>
> This error is telling you that you have a production environment in both
> your testing: and development: sources.
>
> You cannot have the exact same environment in more than one source. To fix
It appears that you are using "environment" (without an s) in the value for
your remote: key,
but your svn repository appears to use "environments" (with an s).
Hope that helps,
Anderson
On Friday, June 12, 2015 at 7:06:20 AM UTC-7, Spriya wrote:
>
> Hi,
>
> I am almost getting there implementi
12 matches
Mail list logo
