From owner-freebsd-questions@FreeBSD.ORG Sat Dec 2 17:48:25 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 17DD916A407 for ; Sat, 2 Dec 2006 17:48:25 +0000 (UTC) (envelope-from fbsd06@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44FD343C9D for ; Sat, 2 Dec 2006 17:48:03 +0000 (GMT) (envelope-from fbsd06@mlists.homeunix.com) Received: from gumby.localdomain (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 9B45A51943 for ; Sat, 2 Dec 2006 12:48:23 -0500 (EST) From: RW To: freebsd-questions@freebsd.org Date: Sat, 2 Dec 2006 17:48:17 +0000 User-Agent: KMail/1.9.4 References: <20061202074631.S84600@scorpio.seibercom.net> In-Reply-To: <20061202074631.S84600@scorpio.seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612021748.18100.fbsd06@mlists.homeunix.com> Subject: Re: pkgtools.conf error with portmanager X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Dec 2006 17:48:25 -0000 On Saturday 02 December 2006 12:54, Gerard Seibert wrote: > I know this was reported the other day; however, I have just encountered > it myself. Evidently, the last 'portupgrade' update is now causing > 'portmanager' to issue this error message: > > > ** Error occured reading /usr/local/etc/pkgtools.conf: > undefined method `x11base' for nil:NilClass > ** Error occured reading /usr/local/etc/pkgtools.conf: > undefined method `x11base' for nil:NilClass > > It doesn't appear to be fatal, although I have not allowed it to run to > completion. Renaming the 'pkgtools.conf' file alleviates the problem. > > Perhaps someone might have a suggestion. I have a simple patch that turns the ruby support off, which is good enough for me as I've alway disliked the feature. I'm not going to submit a PR as someone may be using the pkgtools.conf support. The real solution is to patch the ruby file pkgtools-to-portmanager.rb. If anyone wants this done, but doesn't know ruby, the email address of the original author (which is not the portmanager author) is in the ruby file. My patch file is below. $ cd /usr/ports/sysutils/portmanager/ && cat files/patch-no-ruby-support --- libMGPM/src/MGPMrReadConfigure.c.orig Sat Dec 2 17:10:45 2006 +++ libMGPM/src/MGPMrReadConfigure.c Sat Dec 2 17:11:37 2006 @@ -190,9 +190,7 @@ MGmStrcpy( portupgradeFileName, PREFIXDIR ); MGmStrcat( portupgradeFileName, "/sbin/portupgrade" ); - if( MGrIfFileExist( rubyFileName ) && - MGrIfFileExist( pkgtoolsFileName ) && - MGrIfFileExist( portupgradeFileName ) ) + if( 0 ) { /* * run ruby script