On Saturday 08 September 2007 13:58:24 Jeffrey Goldberg wrote:
> I just got the following when trying a portsnap.  Any ideas?
> I really don't understand how portsnap works, so for me the error
> message isn't that useful.
>
>
> $ sudo portsnap fetch update
> Password:
> Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found.
> Fetching snapshot tag from portsnap3.FreeBSD.org... done.
> Fetching snapshot metadata... done.
> Updating from Fri Sep  7 04:51:41 CDT 2007 to Sat Sep  8 05:50:59 CDT
> 2007.
> Fetching 4 metadata patches... done.
> Applying metadata patches... done.
> Fetching 0 metadata files... done.
> Fetching 1285 patches.....
> 10....20....30....40....50....60....70....80....90....100....110....120.
> ...
> 130....140....150....160....170....180....190....200....210....220....23
> 0....240....250....260....270....280....290....300....310....320....330.
> ...
> 340....350....360....370....380....390....400....410....420....430....44
> 0....450....460....470....480....490....500....510....520....530....540.
> ...550....560....570....580....590.... done.
> Applying patches... done.
> Fetching 708 new ports or files... /usr/sbin/portsnap: cannot open
> e34b76c53bfd361a3defe2a9a884c0aa4f10da8b845ddf8e991fc419b3109f09.gz:
> No such file or directory
> snapshot is corrupt.

This is what I would do...

as root, 

cd /usr/ports/

rm -rf *  (make sure you are in /usr/ports/ when you do this)

portsnap fetch  (this will take a while)

portsnap extract

After that, you only need to do 'portsnap update' when you want to update the 
ports and it should not take too long if you have updated them recently.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to