Date: Sun, 27 Jul 2003 11:23:18 -0500 From: Stephen Hilton <nospam@hiltonbsd.com> To: Kent Stewart <kstewart@owt.com> Cc: kris@obsecurity.org Subject: Re: make index / portsdb -Uu problems Message-ID: <20030727112318.7336d8ad.nospam@hiltonbsd.com> In-Reply-To: <200307270852.45421.kstewart@owt.com> References: <20030726155057.426cce7d.nospam@hiltonbsd.com> <20030727031021.GA55646@rot13.obsecurity.org> <200307270852.45421.kstewart@owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 27 Jul 2003 08:52:45 -0700 Kent Stewart <kstewart@owt.com> wrote: > On Saturday 26 July 2003 08:10 pm, Kris Kennaway wrote: > > On Sat, Jul 26, 2003 at 03:50:57PM -0500, Stephen Hilton wrote: > > > Cheers, > > > > > > > > > Anyone seeing problems with the "make index" or the "portsdb -Uu" > > > runs on 4.8-STABLE cvsupd today after 1PM CDT. > > > > > > Mine are quite borked up, and am trying to determine if the > > > problems are local to my system. > > > > > > I have posted to the ports list earlier in the day also. > > > > index is currently building successfully on a clean system. Either > > you don't have a complete or consistent ports tree, or something else > > on your system is causing the failure. > > > > That may be true on your system; however, I updated my system to 26 July > and make has numerous problems now. A system from 15-16 July has no > problems but the 26 July build only produces an INDEX with 6000 ports. > I am getting closer to a better understanding of whats causing the problem. Went to /usr/ports/print and did: # rm -rf pips* To remove all the print/pips* related ports. Now "make index" runs clean on my 4.8-STABLE system cvsup'd last night. The "portsdb -Uu" still has problems, and am trying to isolate the misbehaving ports for that also. Will report more data points when known. Regards, Stephen Hilton nospam@hiltonbsd.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030727112318.7336d8ad.nospam>