Portsnap serving up bad snapshots?
Marcus Reid
marcus at blazingdot.com
Wed Sep 19 12:34:23 PDT 2007
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.
While it's downloading the big .tgz file, I've hardlinked it
to a different filename so that I still have a copy left over
to see what's wrong with it after portsnap deletes the original.
[root at austin /var/db/portsnap]# ls -l *.bak
-rw-r--r-- 2 root wheel 52085075 Sep 18 17:57 1d76db54d472a78981f30c134f34eea49141d183d481275cb44faae00dc65bdc.tgz.bak
[root at austin /var/db/portsnap]# gunzip -t 1d76db54d472a78981f30c134f34eea49141d183d481275cb44faae00dc65bdc.tgz.bak
[root at austin /var/db/portsnap]# echo $?
0
The sha256 of the file and the filename don't line up:
[root at austin /var/db/portsnap]# sha256 1d76db54d472a78981f30c134f34eea49141d183d481275cb44faae00dc65bdc.tgz.bak
SHA256 (1d76db54d472a78981f30c134f34eea49141d183d481275cb44faae00dc65bdc.tgz.bak) = b8fa376bb2f878f36bf46ebdba2fe267c945c67e6d3085d580adb52b5692b8e4
[root at austin /var/db/portsnap]#
Some files in the archive are valid, but many seem to be
truncated. Is there a big problem with portsnap right now?
Thanks,
Marcus
More information about the freebsd-ports
mailing list