portsnap fetch : "snapshot is corrupt"

Ben Woods woodsb02 at gmail.com
Fri May 15 14:24:15 UTC 2015

On Friday, May 15, 2015, Avinash Sonawane <rootkea at gmail.com> wrote:

> On Fri, May 15, 2015 at 7:01 AM, andrew clarke <mail at ozzmosis.com
> <javascript:;>> wrote:
> > On Thu 2015-05-14 20:13:53 UTC+0530, Avinash Sonawane (rootkea at gmail.com
> <javascript:;>)
> > I've noticed this happen in the past on the odd occasion. I ruled out
> > hardware error on my machine and put it down to some sort of
> > corruption (or more likely syncronisation problem) with the snapshot
> > server(s). If I waited a while (a few hours) then re-ran portsnap the
> > errors went away.
> Same here. Now I can fetch the portsnap without any "sync" errors.
> But from browsing the web and from the mailing list archives I found
> this same problem to be quite frequent and having the only apparent
> solution "just to wait few hours"
> Is this specific issue is bound to happen? I mean it seems as if
> community has adjusted with it. Is this "sync" issue is inherent in
> portsnap design?

 I think this issue is to do with people trying to download the new
portsnap files whilst the mirrors are still synchronizing. So perhaps it is
not a flaw of portsnap itself, but that the mirrors don't flag that a synch
is in progress and don't continue to use the old files until the synch is
fully complete.

I use subversion for synchronizing my ports tree, so I don't have this



From: Benjamin Woods
woodsb02 at gmail.com

More information about the freebsd-questions mailing list