480490500510520530540.
...550560570580590 done.
Applying patches... done.
Fetching 708 new ports or files... /usr/sbin/portsnap: cannot open
e34b76c53bfd361a3defe2a9a884c0aa4f10da8b845ddf8e991fc419b3109f09.gz:
No such file or directory
snapshot
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
On Sep 8, 2007, at 10:10 AM, Pollywog wrote:
This is what I would do...
as root,
cd /usr/ports/
rm -rf * (make sure you are in /usr/ports/ when you do this)
Safer would probably be
rm -rf /usr/ports/
mkdir /usr/ports
portsnap fetch (this will take a while)
portsnap extract
After
On Sep 8, 2007, at 11:28 AM, Steve Bernacki wrote:
This happens to me from time to time on a few older (6.1) systems.
Typically, re-running portsnap fetch clears the issue.
I did another fetch and that did seem to solve the problem. So I
didn't have to go to the more drastic solution of
patches... done.
Fetching 708 new ports or files... /usr/sbin/portsnap: cannot open
e34b76c53bfd361a3defe2a9a884c0aa4f10da8b845ddf8e991fc419b3109f09.gz:
No such file or directory
snapshot is corrupt.
$
Thanks,
-j
___
freebsd-questions@freebsd.org
