On 26 Dec 2002 at 13:39, Kent Stewart boldly uttered: > On Thursday 26 December 2002 01:32 pm, Philip J. Koenig wrote: > > When running "portsdb -uU" as recommended in the Portupgrade > > documentation I'm currently getting some errors, and not sure if I > > have to do something about them or what I should do. Couldn't find > > any suggestions in the Portsdb manpage. > > Until just recently "make index" was broken and the only choice was > using -uU. There was a ~2 day band where "make index" was really > broken. > > For some time now, the only way to get a full list of ports is to do a > "make index" from /usr/ports. You make get a duplicate port message but > it works. The -U options fills screens with messages as it encounters > ports that it can't deal with.
Running "make index" fills the screen with lots more error messages than "portsdb -Uu".. :-) Mostly "..no entry for.." messages, some "..Duplicate INDEX entry:.." messages. Continued below. On 26 Dec 2002 at 21:37, Stacey Roberts boldly uttered: > portsdb -U is broken / has been broken for ages. Use the following > sequence instead: > make index > pkgdb -Fv > portsdb -u When running "pkgdb -Fv" after "make index", I now get: > /usr/ports/INDEX:1:Port info line must consist of 10 fields. [repeats 3 times] > > Skip this for now? [yes] Not sure what I should do here. "Make Index" has created a mis- formatted INDEX file? Sigh. [other error msgs snipped] > > make_index: no entry for: /usr/ports/x11-toolkits/itk > > make_index: no entry for: /usr/local > > Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f > > > > Re-cvsup your ports tree and see if this still happens. I just cvsup'd it yesterday, this was the prerequisite to trying to update portupgrade and the rest of the ports. FYI - if I'm not mistaken, "cvsup-without-gui-16.1f" shares the same code as the "with gui" cvsup port, but with a different build option. -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
