From owner-freebsd-questions@FreeBSD.ORG Sat Sep 8 15:10:57 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 4AD9A16A418 for ; Sat, 8 Sep 2007 15:10:57 +0000 (UTC) (envelope-from lists-fbsd@shadypond.com) Received: from mx-outbound01.easydns.com (mailout.easydns.com [205.210.42.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2157E13C465 for ; Sat, 8 Sep 2007 15:10:57 +0000 (UTC) (envelope-from lists-fbsd@shadypond.com) Received: from slider.shadypond.com (69-12-173-117.static.humboldt1.com [69.12.173.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx-outbound01.easydns.com (Postfix) with ESMTP id C69AC7F85 for ; Sat, 8 Sep 2007 11:10:54 -0400 (EDT) Received: from slider.shadypond.com (slider.shadypond.com [192.168.1.11]) by slider.shadypond.com (postoffice) with ESMTP id 45025B67B1 for ; Sat, 8 Sep 2007 15:10:42 +0000 (UTC) From: Pollywog To: freebsd-questions@freebsd.org Date: Sat, 8 Sep 2007 15:10:41 +0000 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709081510.41633.lists-fbsd@shadypond.com> 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 15:10:57 -0000 On Saturday 08 September 2007 13:58:24 Jeffrey Goldberg wrote: > I just got the following when trying a portsnap. Any ideas? > I really don't understand how portsnap works, so for me the error > message isn't that useful. > > > $ sudo portsnap fetch update > Password: > Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found. > Fetching snapshot tag from portsnap3.FreeBSD.org... done. > Fetching snapshot metadata... done. > Updating from Fri Sep 7 04:51:41 CDT 2007 to Sat Sep 8 05:50:59 CDT > 2007. > Fetching 4 metadata patches... done. > Applying metadata patches... done. > Fetching 0 metadata files... done. > Fetching 1285 patches..... > 10....20....30....40....50....60....70....80....90....100....110....120. > ... > 130....140....150....160....170....180....190....200....210....220....23 > 0....240....250....260....270....280....290....300....310....320....330. > ... > 340....350....360....370....380....390....400....410....420....430....44 > 0....450....460....470....480....490....500....510....520....530....540. > ...550....560....570....580....590.... done. > Applying patches... done. > Fetching 708 new ports or files... /usr/sbin/portsnap: cannot open > e34b76c53bfd361a3defe2a9a884c0aa4f10da8b845ddf8e991fc419b3109f09.gz: > No such file or directory > snapshot is corrupt. This is what I would do... as root, cd /usr/ports/ rm -rf * (make sure you are in /usr/ports/ when you do this) portsnap fetch (this will take a while) portsnap extract After that, you only need to do 'portsnap update' when you want to update the ports and it should not take too long if you have updated them recently.