Portsnap serving up bad snapshots?
Amarendra Godbole
amarendra.godbole at gmail.com
Wed Sep 19 22:59:39 PDT 2007
On 9/20/07, Marcus Reid <marcus at blazingdot.com> wrote:
> 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
[...]
> Some files in the archive are valid, but many seem to be
> truncated. Is there a big problem with portsnap right now?
[...]
If your internet connection if flaky, or if you get in data through a
proxy - this problem pops up. I used to have this problem when my
internet connection was slow and flaky - once we added more bandwidth,
it has gone away completely.
-Amarendra
More information about the freebsd-ports
mailing list