>
> An addendum: if a user installs Puppet from a gem or source (for
> instance) onto an OS release that doesn't have a working policy for that
> version of Puppet, they will probably want to disable the context
> switch. Config of this sort, or a command line argument might work?
>
This is
On Tue, Aug 26, 2014 at 10:23 AM, Eric Sorenson <
eric.soren...@puppetlabs.com> wrote:
> After the Puppet 3.5.0 release problems, we had a retrospective and tried
> to figure out some process improvements which would have surfaced the
> problems earlier. Despite a lengthy 4-week release candidate
On 28/08/14 17:17, Henrik Lindberg wrote:
> On 2014-28-08 9:13, Dominic Cleal wrote:
>> On 26/08/14 18:23, Eric Sorenson wrote:
>>> After the Puppet 3.5.0 release problems, we had a retrospective and tried
>>> to figure out some process improvements which would have surfaced the
>>> problems earl
On 2014-28-08 9:13, Dominic Cleal wrote:
On 26/08/14 18:23, Eric Sorenson wrote:
After the Puppet 3.5.0 release problems, we had a retrospective and tried to
figure out some process improvements which would have surfaced the problems
earlier. Despite a lengthy 4-week release candidate cycle, t
On 2014-28-08 10:02, Felix Frank wrote:
Hi,
this question would be more appropriate on the puppet-users list.
Or even better in the geppetto list :-)
- henrik
--
Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/
--
You received this message because you are subscribe
I'll start out by saying that we've worked around the problem ... but, when
you're operating in cloud and constantly booting new machines, dependencies
like Facter are rarely explicitly versioned. That is to say, often you will
see someone pin the version of Puppet that they install, but they may n
Attending: Ethan, Rob, JoshP, JoshC, Felix, RobBirnie
Short triage this week while working on 3.7 release.
New:
Facter
771: Fact-685 processor speed fact on OpenBSD
- Ethan to merge
770: PUP-3128 Added support for Manjaro Linux to Facter
- JoshP to notify contributor about contributor guid
On 2014-08-28 10:02, Felix Frank wrote:
Hi,
this question would be more appropriate on the puppet-users list.
I suspect that the cause for your issue got lost during anonymization.
Does the module/subdirectory/class name contain some unusual character
outside the [a-zA-Z0-9_] range?
Also, doe
On 2014-08-28 00:51, Kylo Ginsberg wrote:
But going forward there's a question about how to handle changes to fact
*values*. One proposal is that we identify (and of course test against)
some essential facts that we "care a lot about" (such as
'lsbmajdistrelease") and set some rules, like:
(a) w
On 28/08/14 10:01, Dominic Cleal wrote:
> 2. names of SELinux domains are most likely governed by the distribution
> rather than the Puppet project, as at least in Fedora and EL, an SELinux
> policy for Puppet is shipped as part of the base targeted policy and not
> as part of Puppet.
>
> This mea
On 27/08/14 20:00, Joshua Partlow wrote:
> Hi everyone,
>
> There is a PR for Puppet to address difficulties setting security
> contexts in SELinux for specific puppet subcommands
> (https://github.com/puppetlabs/puppet/pull/2997). The contributer (Lukáš
> Zapletal) originally was looking to add a
Hi,
this question would be more appropriate on the puppet-users list.
I suspect that the cause for your issue got lost during anonymization.
Does the module/subdirectory/class name contain some unusual character
outside the [a-zA-Z0-9_] range?
On 08/28/2014 01:25 AM, Abel Paz wrote:
> in using e
On 26/08/14 18:23, Eric Sorenson wrote:
> After the Puppet 3.5.0 release problems, we had a retrospective and tried to
> figure out some process improvements which would have surfaced the problems
> earlier. Despite a lengthy 4-week release candidate cycle, that release still
> had a fatal flaw
13 matches
Mail list logo
