From owner-freebsd-questions@FreeBSD.ORG Mon Jun 21 19:14:38 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 AB0BE16A4CE for ; Mon, 21 Jun 2004 19:14:38 +0000 (GMT) Received: from delivery.infowest.com (delivery.infowest.com [204.17.177.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 925FC43D55 for ; Mon, 21 Jun 2004 19:14:38 +0000 (GMT) (envelope-from jedi@infowest.com) Received: from infowest.com (hogwarts.eq.net [209.33.211.132]) by delivery.infowest.com (Postfix) with ESMTP id 2F78AEAC02E for ; Mon, 21 Jun 2004 13:14:38 -0600 (MDT) Message-ID: <40D733A4.70908@infowest.com> Date: Mon, 21 Jun 2004 13:14:44 -0600 From: Kendall Gifford User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: In-Reply-To: X-Enigmail-Version: 0.81.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: missing ports; portsdb problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jedi@infowest.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jun 2004 19:14:38 -0000 Bill Sawyer wrote: > Jim, > > I had the same problem. I think it was a tk port, if I recall correctly. > > The only way I could fix it was to rm -drv /usr/ports & rm my refuse file, then cvsup again. After that, portsdb -Uu ran properly (though it took forever). > > I had the same problem recently since I was blocking all non-english ports in my refuse file. Just as was mentioned above, I removed it. But, I didn't bother to remove my recently cvsup'ed ports collection (sans other lang). I just edited my refuse file to allow alternate lang ports back in and re-cvsup'ed. Afterward, my portsdb -uU also succeeded. So, basically what I'm saying is that I'd try the above recommendation but without rm-ing /usr/ports. This should save some download time. Plus, if for some reason it doesn't work, you can always clean out your ports dir later. -- Kendall Gifford ======================================== WEB: http://kendall.jedis.com/ EMAIL: REPLY TO NEWSGROUP ========================================