Re: Puppet SSL-related problems after updating Ruby

Hello On Fri, Jan 05, 2018 at 07:01:39PM -0500, Josh Endries wrote: > I recently updated packages on a 11.0 machine, which upgraded Ruby from > 2.3.5 to 2.3.6 (I think), and my Puppet install broke. It is logging > SSL-related issues with this message: > > SSL_read: decryption failed or bad

Puppet SSL-related problems after updating Ruby

I recently updated packages on a 11.0 machine, which upgraded Ruby from 2.3.5 to 2.3.6 (I think), and my Puppet install broke. It is logging SSL-related issues with this message: SSL_read: decryption failed or bad record mac I thought maybe it was a problem with outdated OpenSSL so I updated to

Re: updating ruby

Hi, On 02/09/2017 09:55, Herbert J. Skuhra wrote: > > DEFAULT_VERSIONS+=ruby=2.3 Err, yeah, sorry, was too early for me... Thanks for the correction. Steve signature.asc Description: OpenPGP digital signature

Re: updating ruby

Steve Wills skrev: > > Hi, > On 02/08/2017 11:20, Gerard Seibert wrote: >> On or about 20170109, the default version of ruby was updated from 2.2 >> to 2.3. However, "pkg install" wants to install version 2.2 for ports >> that require ruby. Is there a way to override this behavior? >> > > The

Re: updating ruby

Hi, On 02/08/2017 11:20, Gerard Seibert wrote: > On or about 20170109, the default version of ruby was updated from 2.2 > to 2.3. However, "pkg install" wants to install version 2.2 for ports > that require ruby. Is there a way to override this behavior? > The packages are built from the

updating ruby

On or about 20170109, the default version of ruby was updated from 2.2 to 2.3. However, "pkg install" wants to install version 2.2 for ports that require ruby. Is there a way to override this behavior? -- Carmel ___ freebsd-ports@freebsd.org mailing