Problems with portsdb -Uu on FreeBSD 6.3

[perikillo]

http://www.freebsd.org/doc/en/books/handbook/portsnap.html

  I supposes that "portsnap extract" have to run just once, latter u have to
just run  portsnap fetch && portsnap update?

  Sean, u say that I better mix cvsup + portsnap?

  This is normal? This would not broke my tree?

   Right now I already run cvsup and is running portsdb -Uu, I will let u
know what happend, thanks!!!


On Mon, Sep 8, 2008 at 3:19 PM, Schiz0 <schiz0phrenic21 at gmail.com> wrote:

> On Mon, Sep 8, 2008 at 6:12 PM, Sean Cavanaugh <millenia2000 at hotmail.com>
> wrote:
> > --------------------------------------------------
> > From: "perikillo" <perikillo at gmail.com>
> > Sent: Monday, September 08, 2008 5:41 PM
> > To: "FreeBSD Mailing List" <freebsd-questions at 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."
>