From owner-freebsd-ports-bugs@freebsd.org Tue Mar 28 00:19:06 2017 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE111D1E4A7 for ; Tue, 28 Mar 2017 00:19:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B09FA32C for ; Tue, 28 Mar 2017 00:19:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2S0J6CT050370 for ; Tue, 28 Mar 2017 00:19:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 216807] Update sysutils/puppet4: 4.9.1 Date: Tue, 28 Mar 2017 00:19:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: freebsd@zleslie.info X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: romain@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 00:19:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216807 --- Comment #9 from Zach Leslie --- Hi Romain, The bit about 4.9.4 that I'm uncertain about, is that it looks like hiera u= sers who are using the 'eyaml' backend will require require action for their set= up to continue work as expected. I think this has the information. https://docs.puppet.com/puppet/4.9/hiera_migrate.html#updated-hiera-eyaml-u= sers-go-for-it The release notes seem to indicate that for the common case, there is no ac= tion required. I suspect that this is stable enough, I was only nervous of surprising users without a helpful message. Perhaps "go read the release notes" is enough? I'm unsure. Also, thank you for helping here. I'm never sure who to ask to review the Puppet PRs, and sometimes they sit out for a while without review. So I appreciate your time. --=20 You are receiving this mail because: You are on the CC list for the bug.=