Totally a fair point, thanks for the feedback!
On Fri, Aug 24, 2018 at 8:57 AM Tim Skirvin wrote:
> Ben Ford writes:
>
> [puppetlabs/apache is dropping support for RHEL6 and family]
> > Is there a reason you can't pin to the module to a version that supports
> > your needs?
>
> We proba
What happens when there's a bug fix or security update that you need?
Pinning versions also only works as long as you have no *other* modules
that depend on a newer version of the apache module.
IMO the apache module should not be dropping support for an Apache release
that is still widely use
Ben Ford writes:
[puppetlabs/apache is dropping support for RHEL6 and family]
> Is there a reason you can't pin to the module to a version that supports
> your needs?
We probably will do so for the duration of the transition. But
frankly my management is already pretty frustrated with t
Is there a reason you can't pin to the module to a version that supports
your needs?
Any users that use either Apache 2.2 or use one of the above operating
> systems should pin to an older version of the module. We will continue to
> support these operating systems for older versions of the module
Davin Hanlon writes:
> Quick note to let you know of some major work that we're performing
> to the module. As you probably know, Apache 2.2 has been end-of-lifed
> since the start of 2018 [...] Therefore, we're taking steps to remove
> support for that version of Apache from the module. This als
I found what I had was working. Was just thrown off by the warnings.
On Thu, Oct 13, 2011 at 12:07 AM, thesheff17 wrote:
> I'm getting this and it isn't applying my apache module. Is it because
> of these warnings?
>
> notice: Starting Puppet client version 2.7.5
> /usr/local/rvm/gems/ruby-1.9.
