From owner-freebsd-questions@FreeBSD.ORG Tue Sep 9 12:54:59 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5C8E1065675 for ; Tue, 9 Sep 2008 12:54:59 +0000 (UTC) (envelope-from fbsd06+ZT=3f6774bc@mlists.homeunix.com) Received: from fallback-in1.mxes.net (fallback-out1.mxes.net [216.86.168.190]) by mx1.freebsd.org (Postfix) with ESMTP id 9955D8FC17 for ; Tue, 9 Sep 2008 12:54:59 +0000 (UTC) (envelope-from fbsd06+ZT=3f6774bc@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by fallback-in1.mxes.net (Postfix) with ESMTP id BAC8C16467F for ; Tue, 9 Sep 2008 08:43:36 -0400 (EDT) Received: from gumby.homeunix.com. (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 DFB8E23E3E2 for ; Tue, 9 Sep 2008 08:43:30 -0400 (EDT) Date: Tue, 9 Sep 2008 13:43:15 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20080909134315.375256b1@gumby.homeunix.com.> In-Reply-To: References: <51d7a5160809081441h6f952906ibea9d236a9c271dd@mail.gmail.com> <8d23ec860809081519l2bfb73fax8c82824c17a382bc@mail.gmail.com> <51d7a5160809081625o2856d25erf61e3c409c93ca9c@mail.gmail.com> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Problems with portsdb -Uu on FreeBSD 6.3 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: Tue, 09 Sep 2008 12:54:59 -0000 On Mon, 8 Sep 2008 19:43:14 -0400 "Sean Cavanaugh" wrote: > I've never fully trusted portsnap. I do run portsnap fetch before > every portupgrade but I always follow it up with CVSUP and I usually > find some more files that get changed anyway. "portsnap fetch" doesn't affect your ports tree at all, you need to follow it with "portsnap update". There's no sense in in routinely mixing the two tools on the same tree. If you do find that portsnap isn't updating the tree correctly then you've either found a bug or have some corrupt data somewhere.