Date: Mon, 8 Sep 2008 18:19:03 -0400 From: Schiz0 <schiz0phrenic21@gmail.com> To: "Sean Cavanaugh" <millenia2000@hotmail.com> Cc: perikillo <perikillo@gmail.com>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Problems with portsdb -Uu on FreeBSD 6.3 Message-ID: <8d23ec860809081519l2bfb73fax8c82824c17a382bc@mail.gmail.com> In-Reply-To: <BAY126-DS7CC8BE7FC868CC542691DCA550@phx.gbl> References: <51d7a5160809081441h6f952906ibea9d236a9c271dd@mail.gmail.com> <BAY126-DS7CC8BE7FC868CC542691DCA550@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 8, 2008 at 6:12 PM, Sean Cavanaugh <millenia2000@hotmail.com> wrote: > -------------------------------------------------- > From: "perikillo" <perikillo@gmail.com> > Sent: Monday, September 08, 2008 5:41 PM > To: "FreeBSD Mailing List" <freebsd-questions@freebsd.org> > Subject: Problems with portsdb -Uu on FreeBSD 6.3 > >> Hi people. >> >> Well I have time locking for a solution for this problem I have, I have >> googling around and have not found a solution, I have 2 serves running >> FreeBSD 6.1/6.2, normally I update my ports tree each day, but I already >> stop doing that because I still cannot fix the problems with the commmand: >> >> portsdb -Uu, each time I run that command on both servers I receive this >> error: >> >> Updating the ports index ... Generating INDEX.tmp - please >> wait.."Makefile", >> line 56: Could not find bsd.port.options.mk >> make: fatal errors encountered -- cannot continue >> ===> sysutils/apcupsd failed >> *** Error code 1 > > > CVSUP your tree to straighten it out. I noticed that portsnap will not fix > damaged/missing files. Portsnap will if you do "extract". It WONT if you do "update."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8d23ec860809081519l2bfb73fax8c82824c17a382bc>