Re: portsnap corrupted

On 2008.12.30 16:16:10 +0100, Max Laier wrote:

> long story short: a clean "portsnap fetch && portsnap extract" doesn't extract 
> all ports that should be there according to cvsweb and others.
> 
> I noticed via x11/listres, but there are plenty others - see attached (grep -v 
> -1 ^/ > porterror).

Hey,

I just tried using -d and -p to portsnap to fetch a new dir and
everything worked fine.  Do you have log from portsnap fetch?

fetch part:

Looking up eu.portsnap.FreeBSD.org mirrors... 3 mirrors found.
Fetching public key from portsnap4.FreeBSD.org... done.
Fetching snapshot tag from portsnap4.FreeBSD.org... done.
Fetching snapshot metadata... done.
Fetching snapshot generated at Tue Dec 30 01:13:52 CET 2008:
d13209cad4efce194cf08b26861074625f898e356cd485100% of   54 MB  425 kBps 00m00s
Extracting snapshot... done.
Verifying snapshot integrity... done.
Fetching snapshot tag from portsnap4.FreeBSD.org... done.
Fetching snapshot metadata... done.
Updating from Tue Dec 30 01:13:52 CET 2008 to Tue Dec 30 19:20:10 CET 2008.
Fetching 3 metadata patches.. done.
Applying metadata patches... done.
Fetching 0 metadata files... done.
Fetching 39 patches.....10....20....30.... done.
Applying patches... done.
Fetching 1 new ports or files... done.

And the extract:

Script started on Tue Dec 30 21:28:38 2008
[simon_at_eddie:~] portsnap -d /c/tmp/p/db -p /c/tmp/p/ports extract
/c/tmp/p/ports/.cvsignore
--
/c/tmp/p/ports/x11/zenity/
Building new INDEX files... done.

-- 
Simon L. Nielsen
portsnap co-admin