Date: Tue, 30 Dec 2008 19:12:26 +0100 From: Max Laier <max@love2party.net> To: "Olivier SMEDTS" <olivier@gid0.org> Cc: Steve Franks <franks@rudbek.com>, freebsd-current@freebsd.org, cperciva@freebsd.org Subject: Re: portsnap corrupted Message-ID: <200812301912.27330.max@love2party.net> In-Reply-To: <367b2c980812301003y455a49edk84e82068d33e5c7a@mail.gmail.com> References: <200812301616.11132.max@love2party.net> <539c60b90812300959y4f01509egc97d4e5d82ded7d@mail.gmail.com> <367b2c980812301003y455a49edk84e82068d33e5c7a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 30 December 2008 19:03:46 Olivier SMEDTS wrote: > 2008/12/30 Steve Franks <franks@rudbek.com>: > > On Tue, Dec 30, 2008 at 8:16 AM, Max Laier <max@love2party.net> wrote: > >> Hi, > >> > >> long story short: a clean "portsnap fetch && portsnap extract" doesn't > >> extract all ports that should be there according to cvsweb and others. > > > > This seems a common question. I'm the last one who got help on it. > > Basically, in my mind the error sounds like there's a problem with the > > server, but it's really on your machine. What you need to do is find > > the file where portsnap fetch downloads the ports tarball, and delete > > it, then start over. It's somewhere under /var - google for my last > > thread, and you'll find the reply of the good gentleman who helped me > > if you can't grep the exact path. > > When I want to start over a fresh db (because portsnap keeps a lot of > files since the first snapshot), I just "rm -rf /var/db/portsnap/*" > then "portsnap fetch extract". Been there, done that ... that's why I said a *clean* portsnap fetch - on different boxes, too. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200812301912.27330.max>