snapshot is corrupt

Steve Bernacki moxiefreak at gmail.com
Sat Sep 8 09:55:43 PDT 2007


This happens to me from time to time on a few older (6.1) systems.
Typically, re-running "portsnap fetch" clears the issue.

Steve


On 9/8/07, Jeffrey Goldberg <jeffrey at goldmark.org> 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.
> $
>
>
> Thanks,
>
> -j
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
>


More information about the freebsd-questions mailing list