From owner-freebsd-ports@FreeBSD.ORG  Fri Sep 21 00:11:36 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id ED6EC16A418
	for <freebsd-ports@freebsd.org>; Fri, 21 Sep 2007 00:11:36 +0000 (UTC)
	(envelope-from marcus@blazingdot.com)
Received: from marklar.blazingdot.com (marklar.blazingdot.com [207.154.84.83])
	by mx1.freebsd.org (Postfix) with SMTP id C2F6813C455
	for <freebsd-ports@freebsd.org>; Fri, 21 Sep 2007 00:11:36 +0000 (UTC)
	(envelope-from marcus@blazingdot.com)
Received: (qmail 31348 invoked by uid 503); 21 Sep 2007 00:11:36 -0000
Date: Thu, 20 Sep 2007 17:11:36 -0700
From: Marcus Reid <marcus@blazingdot.com>
To: freebsd-ports@freebsd.org
Message-ID: <20070921001136.GA30682@blazingdot.com>
References: <20070919193422.GA7169@blazingdot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070919193422.GA7169@blazingdot.com>
X-Coffee-Level: nearly-fatal
User-Agent: Mutt/1.5.6i
Subject: Re: Portsnap serving up bad snapshots?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Sep 2007 00:11:37 -0000

On Wed, Sep 19, 2007 at 12:34:22PM -0700, Marcus Reid wrote:
> Hi,
> 
> I've tried this on a couple of different machines a few times over
> the last couple of days, and keep getting the same results.  Starting
> with an empty /var/db/portsnap :
> 
>   [root@austin /var/db]# portsnap fetch
>   Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
>   Fetching public key from portsnap3.freebsd.org... done.
>   Fetching snapshot tag from portsnap3.freebsd.org... done.
>   Fetching snapshot metadata... done.
>   Fetching snapshot generated at Tue Sep 18 17:22:37 PDT 2007:
>   1d76db54d472a78981f30c134f34eea49141d183d48127100% of   49 MB   90 kBps 00m00s
>   Extracting snapshot... done.
>   Verifying snapshot integrity... gunzip: snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: unexpected end of file
>   gunzip: snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: uncompress failed
>   snapshot corrupt.

Hi Again,

Just thought I'd set the record straight..  This turned out to
be a regression in libarchive that broke bsdtar in -CURRENT.  It
has since been backed out.  There was no problem with portsnap.

Marcus