From owner-freebsd-ports@FreeBSD.ORG Sat Jun 1 01:09:41 2013 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C52AB1B2 for ; Sat, 1 Jun 2013 01:09:41 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) by mx1.freebsd.org (Postfix) with ESMTP id 8CD40638 for ; Sat, 1 Jun 2013 01:09:41 +0000 (UTC) Received: from meatwad.mouf.net (cpe-098-122-135-254.nc.res.rr.com [98.122.135.254]) (authenticated bits=0) by mouf.net (8.14.5/8.14.5) with ESMTP id r5119V6R029883 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 1 Jun 2013 01:09:37 GMT (envelope-from swills@FreeBSD.org) Message-ID: <51A949C8.2080009@FreeBSD.org> Date: Sat, 01 Jun 2013 01:09:28 +0000 From: Steve Wills User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130413 Thunderbird/17.0.5 MIME-Version: 1.0 To: "bw.mail.lists" , FreeBSD Mailing List Subject: Re: ruby 1.9 upgrade and puppet References: <51A88F42.5010503@gmail.com> <51A90FD2.1010103@gmail.com> In-Reply-To: <51A90FD2.1010103@gmail.com> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Sat, 01 Jun 2013 01:09:37 +0000 (UTC) X-Spam-Status: No, score=0.0 required=4.5 tests=none autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.97.8 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jun 2013 01:09:41 -0000 On 05/31/13 21:02, bw.mail.lists wrote: > >>> >>> It would probably be best to kill puppet before the upgrade. >> >> This is definitely the problem here. I'm afraid you'll have to >> manually kill it here, since the old rc script has been >> deinstalled. You'll only have to do it this once. >> > > Not a problem (except for UPDATING), but since $command_interpreter > is set to ruby19 in the new script, doesn't that mean that the same > thing will happen on the next ruby update? Yes, but it's pretty rare and I'm not sure how we could avoid it. I've added a note to UPDATING reminding users to stop the software before updating. The other issues you had were caused by a bug in the facter port and should be fixed now with sysutils/rubygem-facter 1.6.18_2. Please update and let me know if you have any further issues. Steve