From owner-freebsd-questions Tue Aug 27 19: 4: 5 2002 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 C540D37B400 for ; Tue, 27 Aug 2002 19:04:02 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3231643E72 for ; Tue, 27 Aug 2002 19:04:02 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.5/8.12.5) id g7S241v7046586; Tue, 27 Aug 2002 21:04:01 -0500 (CDT) (envelope-from dan) Date: Tue, 27 Aug 2002 21:04:01 -0500 From: Dan Nelson To: Troy Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Somehow broke pkgdb Message-ID: <20020828020401.GH75117@dan.emsphone.com> References: <3D6C2780.3A4CB53E@myrealbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D6C2780.3A4CB53E@myrealbox.com> X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.1i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Aug 27), Troy said: > I was running pkgdb before using portupgrade to do some upgrading.. when > it came across a stale dependency for ruby. After having it check the > version history, I told it not to do anything with it. Then later I go > to run pkgdb again, and now I get this: > > > pkgdb -F > /usr/local/sbin/pkgdb:34:in `require': No such file to load -- > optparse(LoadError) from /usr/local/sbin/pkgdb:34 > > I figured it must have done something to ruby which it requires to run, > so I deinstalled the portupgrade, ruby, etc and rebuilding them all but > it still does this. Any ideas? Remove and reinstall the ruby-shim-ruby18 port; it provides optparse now. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message