From owner-freebsd-questions@FreeBSD.ORG Tue May 18 05:56:07 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 0A77516A4CE for ; Tue, 18 May 2004 05:56:06 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 04D8943D9B for ; Tue, 18 May 2004 05:55:02 -0700 (PDT) (envelope-from robin@reportlab.com) Received: (qmail 7160 invoked from network); 18 May 2004 12:54:29 -0000 Received: from unknown (HELO ?192.168.0.3?) (213.86.96.61) by relay.pair.com with SMTP; 18 May 2004 12:54:29 -0000 X-pair-Authenticated: 213.86.96.61 Message-ID: <40AA0784.2070301@chamonix.reportlab.co.uk> Date: Tue, 18 May 2004 13:54:28 +0100 From: Robin Becker User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: cvsup ports questions 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: Tue, 18 May 2004 12:56:07 -0000 I've been attempting to follow Dru Lavigne's excellent advice and clean up my ports, but no matter how careful I am, I seem to get into circles sometimes. Recently I found that package openldap-client-2.0.27_1 was causing problems. The port 'net/openldap20-client' was removed on 2004-05-03 because: "removed EOL version of OpenLDAP" Attempted removal was blocked by gnome2-2.4.0 gnomemeeting-0.98.5 Eventually I removed first gnome2-2.4.0, then gnomemeeting-0.98.5 after which openldap could be removed (even though /usr/ports/net/openldap20 was long gone). Now, however, I have to put these back by hand. This isn't too hard here, but what happens if the chain is longer. Is there an easier root with portupgrade? Another thing is, should I worry about duplicate index warnings? -- Robin Becker