Portsnap serving up bad snapshots?

[Marcus Reid]

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 at 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