Date: Tue, 30 Dec 2008 19:03:46 +0100 From: "Olivier SMEDTS" <olivier@gid0.org> To: "Steve Franks" <franks@rudbek.com> Cc: Max Laier <max@love2party.net>, freebsd-current@freebsd.org, cperciva@freebsd.org Subject: Re: portsnap corrupted Message-ID: <367b2c980812301003y455a49edk84e82068d33e5c7a@mail.gmail.com> In-Reply-To: <539c60b90812300959y4f01509egc97d4e5d82ded7d@mail.gmail.com> References: <200812301616.11132.max@love2party.net> <539c60b90812300959y4f01509egc97d4e5d82ded7d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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".
Cheers
--
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: olivier@gid0.org - against HTML email & vCards X
www: http://www.gid0.org - against proprietary attachments / \
"Il y a seulement 10 sortes de gens dans le monde :
ceux qui comprennent le binaire,
et ceux qui ne le comprennent pas."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?367b2c980812301003y455a49edk84e82068d33e5c7a>