From owner-freebsd-ports@FreeBSD.ORG Fri May 31 13:27:28 2013 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 639F28AC for ; Fri, 31 May 2013 13:27:28 +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 138FA192 for ; Fri, 31 May 2013 13:27:28 +0000 (UTC) Received: from mouf.net (www@mouf [199.48.129.64]) by mouf.net (8.14.5/8.14.5) with ESMTP id r4VDRHs1017340; Fri, 31 May 2013 13:27:22 GMT (envelope-from swills@FreeBSD.org) Received: from 64.128.208.27 (SquirrelMail authenticated user swills) by mouf.net with HTTP; Fri, 31 May 2013 09:27:24 -0400 Message-ID: In-Reply-To: <51A88F42.5010503@gmail.com> References: <51A88F42.5010503@gmail.com> Date: Fri, 31 May 2013 09:27:24 -0400 Subject: Re: ruby 1.9 upgrade and puppet From: "Steve Wills" To: "bw.mail.lists" User-Agent: SquirrelMail/1.4.22 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Fri, 31 May 2013 13:27:24 +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 Cc: freebsd-ports@FreeBSD.org 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: Fri, 31 May 2013 13:27:28 -0000 > Moving to ruby 1.9 by following the instructions in UPDATING breaks > puppet. > > When updating with portmaster, at install time it says 'could not load > facter; cannot install' and exits. I had to manually run 'gem install > facter', then puppet installed. It's better to install via the port so that the package management knows it's there. This could be causing the later problems. > However, 'service puppetmaster status' > was reporting puppet as not running even though it was, so I had to kill > the running process before 'service puppetmaster start'. I assume this > is related to $command_interpreter in the rc script being changed from > ruby18 to ruby19? Although, /usr/local/bin/ruby and > /usr/local/bin/ruby19 are identical, can't the script use plain ruby > instead of ruby19? > It would probably be best to kill puppet before the upgrade. > For poudriere, puppet failed, still facter: > > ======================= >============================ > ===> Installing for puppet-3.1.1_2 > ===> Generating temporary packing list > ===> Checking if sysutils/puppet already installed > ===> Creating users and/or groups. > Creating group `puppet' with gid `814'. > Creating user `puppet' with uid `814'. > ftools not found. Using FileUtils instead.. > Could not load facter; cannot install > *** [do-install] Error code 255 > > Stop in /usr/ports/sysutils/puppet. > ===> Cleaning for puppet-3.1.1_2 > build of /usr/ports/sysutils/puppet ended at Fri May 31 11:37:10 CEST 2013 > > Rebuilding everything with 'poudriere bulk -c' worked fine. I'm aware > that rebuilding everything isn't needed, but it didn't take that long. I'm unable to reproduce any build issues. > But then, when upgrading with pkg, again I had to 'gem install facter' > manually and kill the running script before puppet would restart. Could you send me a list of installed system packages and the output of "gem list"? Thanks, Steve