From owner-freebsd-questions@FreeBSD.ORG Sat Sep 8 16:36:46 2007 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 CCEA616A421 for ; Sat, 8 Sep 2007 16:36:46 +0000 (UTC) (envelope-from jeffrey@goldmark.org) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 9D53913C48E for ; Sat, 8 Sep 2007 16:36:46 +0000 (UTC) (envelope-from jeffrey@goldmark.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 2426628A4C; Sat, 8 Sep 2007 12:36:46 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sat, 08 Sep 2007 12:36:46 -0400 X-Sasl-enc: pivMiyB7QzLc6LOtT6dTwF+9It1kLtz1970t6n8Dm7ef 1189269405 Received: from [10.1.10.136] (n114.ewd.goldmark.org [72.64.118.114]) by mail.messagingengine.com (Postfix) with ESMTP id C2B0718DA1; Sat, 8 Sep 2007 12:36:45 -0400 (EDT) In-Reply-To: <6061fc420709080928y3a1d84f7m336cacfbfd79459e@mail.gmail.com> References: <6061fc420709080928y3a1d84f7m336cacfbfd79459e@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <89DAC94F-3F11-4338-BD53-A6B9363D5A63@goldmark.org> Content-Transfer-Encoding: 7bit From: Jeffrey Goldberg Date: Sat, 8 Sep 2007 11:36:44 -0500 To: Steve Bernacki X-Mailer: Apple Mail (2.752.2) Cc: freebsd-questions@freebsd.org Subject: Re: snapshot is corrupt 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: Sat, 08 Sep 2007 16:36:46 -0000 On Sep 8, 2007, at 11:28 AM, Steve Bernacki wrote: > This happens to me from time to time on a few older (6.1) systems. > Typically, re-running "portsnap fetch" clears the issue. I did another fetch and that did seem to solve the problem. So I didn't have to go to the more drastic solution of deleting the whole ports tree. I'm wondering if things were in an inconsistent state for all of the p5-* ports that were updated. I'm tracking RELENG_6_2 Cheers, -j