Date: Tue, 7 Oct 2008 14:59:45 -0700 From: "Steve Franks" <stevefranks@ieee.org> To: RW <fbsd06@mlists.homeunix.com> Cc: freebsd-questions@freebsd.org Subject: Re: how to break portsnap Message-ID: <539c60b90810071459t17b4cd65qc6865472317cfd29@mail.gmail.com> In-Reply-To: <20081007221731.40cbf5d6@gumby.homeunix.com.> References: <539c60b90810071356g1d07d339yeaa5bc6f20b14109@mail.gmail.com> <20081007221731.40cbf5d6@gumby.homeunix.com.>
next in thread | previous in thread | raw e-mail | index | archive | help
Aaaaaagh! I thought the snapshot was the thing being downloaded! Here I was double-checking my key and the like. I sort of would've expected the process to include overwriting everything local with the new stuff. My mistake, obviously. Sometimes one does need the obvious pointed out to them, thanks. Steve On Tue, Oct 7, 2008 at 2:17 PM, RW <fbsd06@mlists.homeunix.com> wrote: > On Tue, 7 Oct 2008 13:56:37 -0700 > "Steve Franks" <stevefranks@ieee.org> wrote: > >> I've googled high & low but I cannot find much other that "this cannot >> happen" replies. I've got a dual boot to amd64 and i386. The amd64 >> hasn't been able to portsnap fetch or cron since march. The i386 I >> just installed, and it portsnap's fine, so it's not a firewall or >> related issue. I've checked my key and it looks ok. What am I >> missing? >> >>... >> Fetching 13708 new ports or files... /usr/sbin/portsnap: cannot open >> e53d7ea3f6fbc2e6a87a1f194ea623fc6b27c74d9aecfd61e0d765e86d861ad5.gz: >> No such file or directory >> snapshot is corrupt. > > It's pretty self-explanatory, the snapshot is corrupt. > > delete /var/db/portsnap/* and then start-again by do a "fetch" and > "extract". > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?539c60b90810071459t17b4cd65qc6865472317cfd29>