Will there be a version of this AIO package for 3.7.4 (or even 3.7.3) so we
can try out the packaging without trying out all the stuff in puppet 4.0 at
the same time?
On Sat Nov 22 2014 at 11:46:16 AM Martin Alfke tux...@gmail.com wrote:
On 21 Nov 2014, at 21:46, Eric Sorenson
On Nov 24, 2014 11:33 AM, Erik Dalén erik.gustav.da...@gmail.com wrote:
Will there be a version of this AIO package for 3.7.4 (or even 3.7.3) so
we can try out the packaging without trying out all the stuff in puppet 4.0
at the same time?
+1
On Sat Nov 22 2014 at 11:46:16 AM Martin Alfke
+2
On Mon, Nov 24, 2014 at 6:01 AM, Martin Alfke tux...@gmail.com wrote:
On Nov 24, 2014 11:33 AM, Erik Dalén erik.gustav.da...@gmail.com
wrote:
Will there be a version of this AIO package for 3.7.4 (or even 3.7.3) so
we can try out the packaging without trying out all the stuff in
On Friday, November 21, 2014 3:21:15 PM UTC-6, Rob Reynolds wrote:
When we originally set out to do PUP-2628[1] for Puppet 4, we were going
to change the group resource default to not authoritative for Windows (e.g.
the specified members would be the minimum), because the thinking is that
On Friday, November 21, 2014 2:47:05 PM UTC-6, Eric Sorenson wrote:
5 - Why not use a metapackage which has no content of its own, but has
requirements on specific versions of the other 'real' packages that contain
the actual programs?
• Avoiding a coordinated major version
I'm in 100% agreement with John here.
Right now, I have a forked Hiera that I'm using based off of some patches
that I have PRs in for. Once this gets resolved, I'll merge everything back
to the mainline, but I *must* have the ability to deviate when necessary
for the best results of my users.
On Monday, November 24, 2014 9:37:38 AM UTC-6, John Bollinger wrote:
purging. I think you still end up with a slightly leaky abstraction, in
that only some systems have a concept of users' primary group, but support
for that could and probably should be recast as a provider feature. On
We have created a new low-volume read-only mailing list for
security-related announcements: puppet-security-announce.
This list will contain only announcements of Puppet Labs software
releases that address security vulnerabilities and other
security-related information. This includes information
on a slightly different tangent:
Would it be possible to get the puppet 4.x packages named puppet4 instead
of puppet? This would allow for one to ensure that bug fixes for puppet
3.x would be installed as soon as they become available for those of us
sticking with 3.x, even after the 4.x
They'll be named 'puppet-agent' and therefore won't auto-upgrade if you already
have puppet installed. I mentioned this up-thread but I can't blame you for
missing it :)
On Nov 24, 2014, at 1:02 PM, Joachim Thuau e...@korigan.net wrote:
on a slightly different tangent:
Would it be possible
On 11/24/2014 04:37 PM, John Bollinger wrote:
A (say) Group_membership resource type could allow group membership to
be expressed the same way for all systems, and it would dovetail
nicely with the new ideas for client-side queries and resource
purging. I think you still end up with a
11 matches
Mail list logo
