From owner-freebsd-questions@FreeBSD.ORG Sun Apr 11 16:23:57 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4118A16A4CE for ; Sun, 11 Apr 2004 16:23:57 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2413243D46 for ; Sun, 11 Apr 2004 16:23:57 -0700 (PDT) (envelope-from lowell@be-well.ilk.org) Date: Sun, 11 Apr 2004 23:23:57 +0000 (GMT) X-Comment: Sending client does not conform to RFC822 minimum requirements X-Comment: Date has been added by Maillennium Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (rwcrmhc13) with ESMTP id <2004041123235601500ab7k0e>; Sun, 11 Apr 2004 23:23:56 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 8FE8E55; Sun, 11 Apr 2004 19:23:56 -0400 (EDT) Resent-To: freebsd-questions@freebsd.org Resent-From: Lowell Gilbert Resent-Date: 11 Apr 2004 19:23:56 -0400 X-From-Line: nobody Sun Apr 11 19:22:00 2004 Sender: lowell@be-well.ilk.org To: "Ralph M. Los" References: From: Lowell Gilbert In-Reply-To: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 17 Resent-Message-Id: <20040411232356.8FE8E55@be-well.no-ip.com> cc: freebsd-question@freebsd.org Subject: Re: Pkgtools "missing"?? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Apr 2004 23:23:57 -0000 "Ralph M. Los" writes: > Hi all, > Just did a "portupgrade portupgrade". All appeared to go well, until this: > > crazy# portupgrade -r samba > /usr/local/sbin/portupgrade:35:in `require': No such file to load -- pkgtools (LoadError) > from /usr/local/sbin/portupgrade:35 > > Well, line 35 is thus: > require "pkgtools" > > So what happened? How do I fix it? You probably tripped over the issue described in the Feb. 26 entry in /usr/ports/UPDATING. You'll need to upgrade ruby before trying to build the new portupgrade.