Re: portsdb issues
On Mon, 2004-03-08 at 15:54, Kris Kennaway wrote: make describe complains on each of them. Post the errors if you want us to be able to analyze things. Well, after doing a make describe in /usr/ports, it barfs with: ---8--- === databases/mytop mytop-1.4|/usr/ports/databases/mytop|/usr/local|A top clone for MySQL|/usr/ports/databases/mytop/pkg-descr|[EMAIL PROTECTED]|databases||/usr/ports/databases/p5-DBD-mysql /usr/ports/devel/p5-Term-ANSIColor /usr/ports/devel/p5-Term-ReadKey /usr/ports/devel/p5-Time-HiRes|http://jeremy.zawodny.com/mysql/mytop/ === databases/namazu2 *** Error code 1 Stop in /usr/ports/databases. *** Error code 1 Stop in /usr/ports. ---8--- As soon as I delete /usr/ports/database/namazu2, and run make describe again, it gets farther. I tried to assemble a list on my laptop recently, and so far I had on it: ---8--- rm -rf /usr/ports/devel/sparc-rtems-gdb rm -rf /usr/ports/databases/namazu2 rm -rf /usr/ports/net/samba-devel rm -rf /usr/ports/www/mozilla-bonobo rm -rf /usr/ports/devel/linux-glib2 rm -rf /usr/ports/devel/linux-libglade rm -rf /usr/ports/devel/qt-designer rm -rf /usr/ports/devel/ruby-gconf2 rm -rf /usr/ports/devel/ruby-glib2 rm -rf /usr/ports/devel/ruby-gnomevfs rm -rf /usr/ports/devel/ruby-libglade rm -rf /usr/ports/devel/ruby-libglade2 rm -rf /usr/ports/misc/bookcase rm -rf /usr/ports/*/k* rm -rf /usr/ports/sysutils/filelight rm -rf /usr/ports/textproc/cbedic rm -rf /usr/ports/textproc/linux-expat rm -rf /usr/ports/textproc/linux-libxml rm -rf /usr/ports/www/quanta rm -rf /usr/ports/audio/arts rm -rf /usr/ports/audio/amarok rm -rf /usr/ports/deskutils/basket rm -rf /usr/ports/deskutils/dragstack rm -rf /usr/ports/deskutils/superkaramba rm -rf /usr/ports/games/easysok rm -rf /usr/ports/games/atlantikdesigner rm -rf /usr/ports/games/six rm -rf /usr/ports/games/spacehulk rm -rf /usr/ports/games/taxipilot rm -rf /usr/ports/graphics/pixieplus rm -rf /usr/ports/graphics/showimg rm -rf /usr/ports/math/algae rm -rf /usr/ports/math/fung-calc rm -rf /usr/ports/multimedia/hayes rm -rf /usr/ports/editors/vimpart rm -rf /usr/ports/misc/renamedlgplugins rm -rf /usr/ports/multimedia/noatun-plugins ---8--- I believe that recently broken too with other ports coming out. BTW: All on 4.8-RELEASE-p15 if that matters. It might..that version is no longer officially supported by the ports collection (see http://www.freebsd.org), and there was a change to make(1) before 4.9 that corrected a parse error in certain makefile syntax. Over time ports have started to rely on this bugfix. Okay, I tried upgrading to 4.9 (p4 I believe), and run it again. Same problem, so I don't think it depends on the BSD version. I'm clueless... all I can think of is to systematically remove broken ports and to run make index on that reduced set. Since upgrading to 4.9 doesn't help, I have no clue what to try next. Any pointers as what to try are appreciated. I should have a bit more time the next couple weeks to dig into this. Thanks, Frank -- Warning at the Gates of Bill: Abandon hope, all ye who press ENTER here... signature.asc Description: This is a digitally signed message part
Re: portsdb issues
On Mon, Mar 29, 2004 at 05:56:13PM -0600, Frank Knobbe wrote: On Mon, 2004-03-08 at 15:54, Kris Kennaway wrote: make describe complains on each of them. Post the errors if you want us to be able to analyze things. Well, after doing a make describe in /usr/ports, it barfs with: ---8--- === databases/mytop mytop-1.4|/usr/ports/databases/mytop|/usr/local|A top clone for MySQL|/usr/ports/databases/mytop/pkg-descr|[EMAIL PROTECTED]|databases||/usr/ports/databases/p5-DBD-mysql /usr/ports/devel/p5-Term-ANSIColor /usr/ports/devel/p5-Term-ReadKey /usr/ports/devel/p5-Time-HiRes|http://jeremy.zawodny.com/mysql/mytop/ === databases/namazu2 *** Error code 1 Stop in /usr/ports/databases. *** Error code 1 I can't see anything in this or some of the other ports you mentioned that might cause problems. My best guess is that something is still non-standard about your system, but I can't do better than that. If you can dig around with 'make -d' (see the make manpage) to try to find what is causing the error, that might shed some more light on the problem. Kris pgp0.pgp Description: PGP signature
NOPORTDOCS breaks index builds (Re: portsdb issues / make index failure -- SOLVED)
On Mon, Mar 29, 2004 at 10:58:15PM -0600, Frank Knobbe wrote: I finally found the problem to the make index problem I was having. The issue was that make index barfs with: Warning: Duplicate INDEX entry: *** Error code 1 Warning: Duplicate INDEX entry: make describe barfs with: === databases/namazu2 *** Error code 1 Stop in /usr/ports/databases. *** Error code 1 Stop in /usr/ports. Right.. The problem turned out to be the NOPORTDOCS flag in my /etc/make.conf. With that flag present (hoping not to waste space on port documentation), the make index build fails since... uhm... sometime beginning of February. OK, it's now clear why this is failing (unassociated shell command in the namazu2 makefile). Clearly this is something we need to work on fixing - good work tracking it down. Kris pgp0.pgp Description: PGP signature
Re: portsdb issues
On Sat, 2004-03-06 at 17:00, Shaun T. Erickson wrote: I waited a bit, then ran cvsup on the ports, once more, and this time there was more to download, including a new INDEX-5 file. I ran portsdb -Uu once more, and it worked perfectly. I guess my ports tree was out of sync somehow. Whoa... if that was out of sync, then cvsup2 is _still_ out of sync. I'm running make describe to find the broken ports. So far I found: /usr/ports/devel/sparc-rtems-gdb /usr/ports/databases/namazu2 /usr/ports/net/samba-devel /usr/ports/www/mozilla-bonobo /usr/ports/converters/ktextdecode /usr/ports/devel/kdesdk3 /usr/ports/devel/kdevelop /usr/ports/devel/linux-glib2 /usr/ports/devel/linux-libglade /usr/ports/devel/qt-designer /usr/ports/devel/ruby-gconf2 /usr/ports/devel/ruby-glib2 /usr/ports/devel/ruby-gnomevfs /usr/ports/devel/ruby-libglade /usr/ports/devel/ruby-libglade2 /usr/ports/lang/klogoturtle /usr/ports/ftp/kbear /usr/ports/mail/kshowmail /usr/ports/misc/bookcase /usr/ports/misc/katalog /usr/ports/misc/kde3-i18n-af make describe complains on each of them. I have already dumped the ports tree and cvsup'ed it completely fresh. (First cvsup yesterday afternoon, last cvsup today around noon.) Is there something wrong with cvsup2 perhaps? BTW: All on 4.8-RELEASE-p15 if that matters. I never had that many issues with the ports in the past. It all started recently when sparc-rtems-gdb and namazu2 went belly up. Regards, Frank signature.asc Description: This is a digitally signed message part
Re: portsdb issues
On Mon, Mar 08, 2004 at 02:49:04PM -0600, Frank Knobbe wrote: On Sat, 2004-03-06 at 17:00, Shaun T. Erickson wrote: I waited a bit, then ran cvsup on the ports, once more, and this time there was more to download, including a new INDEX-5 file. I ran portsdb -Uu once more, and it worked perfectly. I guess my ports tree was out of sync somehow. make describe complains on each of them. Post the errors if you want us to be able to analyze things. BTW: All on 4.8-RELEASE-p15 if that matters. It might..that version is no longer officially supported by the ports collection (see http://www.freebsd.org), and there was a change to make(1) before 4.9 that corrected a parse error in certain makefile syntax. Over time ports have started to rely on this bugfix. Kris pgp0.pgp Description: PGP signature
Re: portsdb issues
On Saturday 06 March 2004 01:00 pm, Shaun T. Erickson wrote: When I run portsdb -Uu on my 5.2.1-RELEASE-p1 system, I get: Updating the ports index ... Generating INDEX.tmp - please wait.. followed by over 10,000 entries similar to this: make_index: gnomemag-0.10.7: no entry for /usr/ports/textproc/libxml2 followed by: Warning: Duplicate INDEX entry: Done. done [Updating the portsdb format:bdb1_btree in /usr/ports ... - 3795 port entries found /usr/ports/INDEX-5:1:Port info line must consist of 10 fields. /usr/ports/INDEX-5:2:Port info line must consist of 10 fields. /usr/ports/INDEX-5:3:Port info line must consist of 10 fields. /usr/ports/INDEX-5:4:Port info line must consist of 10 fields. /usr/ports/INDEX-5:5:Port info line must consist of 10 fields. .1000.2000.3000... . done] There was only one duplicate entry reported. So, how do I get my system back into a happy state? There was a problem like this a couple of days ago but I haven't seen any problem generating INDEX today. I would re-cvsup and see if it goes away. FWIW, I have a chron job that updates my ports at 4 everyday. I didn't have any problem at 4am on my 4-stable system. I wasn't booted to 5-current on opal. I am trying that now. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb issues
Kent Stewart wrote: There was a problem like this a couple of days ago but I haven't seen any problem generating INDEX today. I would re-cvsup and see if it goes away. I have been diligently keeping my system cvsup'd every day. It dawned on me that I haven't been running portsdb -Uu after every cvsup though, so I ran it, and that's what I got. So what do I do now? -ste ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb issues
On Saturday 06 March 2004 01:43 pm, Shaun T. Erickson wrote: Kent Stewart wrote: There was a problem like this a couple of days ago but I haven't seen any problem generating INDEX today. I would re-cvsup and see if it goes away. I have been diligently keeping my system cvsup'd every day. It dawned on me that I haven't been running portsdb -Uu after every cvsup though, so I ran it, and that's what I got. So what do I do now? Did you recvsup and then run portsdb -uU? My 5-current system has been generating INDEX for more than 5 minutes. When all of these messages show up, they usually start appearing by now. A complete make index takes about 20 minutes on opal. Portsdb -U uses make index. What does a uname -a produce? There was a thing with jails and I don't have a jail setup on any of my machines. What I get with a recent cvsup of ports-all is Generating INDEX-5 - please wait.. Done. [Updating the portsdb format:bdb1_btree in /usr/ports ... - 10497 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1 . done] Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb issues
Kent Stewart wrote: Did you recvsup ... Apparently I'm new enough to FreeBSD that I don't understand you. I ran cvsup on my docs, my system source and my ports, and ran portsdb -Uu afterwards. When I run them again, there is nothing to download. That tells me I have everything. I guess I don't know what you want me to do. -ste ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb issues
On Saturday 06 March 2004 01:56 pm, Shaun T. Erickson wrote: Kent Stewart wrote: Did you recvsup ... Apparently I'm new enough to FreeBSD that I don't understand you. I ran cvsup on my docs, my system source and my ports, and ran portsdb -Uu afterwards. When I run them again, there is nothing to download. That tells me I have everything. I guess I don't know what you want me to do. When you ran cvsup on ports-all and there was't anything to download, you had done the re-cvsup. I did a cvsup of ports-all just before I did the make index. I have a script that does the cvsup and generate the indexes. I make fewer mistakes that way. How do you run cvsup? What do you use on the command line. For example, I use cvsup -g -L 2 ports-supfile You might also change the mirror in your cvsup file. For example, I have *default host=cvsup11.FreeBSD.org *default base=/usr *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix Occasionally, a mirror will get stuck for one reason or another. The only way you can find out is if you have problems, change the mirror to something like cvsup16, and the problem goes away. If you do this and still have problems, you should probably move your problem to [EMAIL PROTECTED] There are more things that you can do but they get messy :). The mirrors mostly update on the hour. Cvsuping less than an hour apart may be using the same old data. You need to wait until 15-20 minutes after the hour for the mirror to be updated. I mirror most of the data and it takes around 8 minutes for a mirror update to finish. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb issues
Kent Stewart wrote: The mirrors mostly update on the hour. Cvsuping less than an hour apart may be using the same old data. You need to wait until 15-20 minutes after the hour for the mirror to be updated. I mirror most of the data and it takes around 8 minutes for a mirror update to finish. I waited a bit, then ran cvsup on the ports, once more, and this time there was more to download, including a new INDEX-5 file. I ran portsdb -Uu once more, and it worked perfectly. I guess my ports tree was out of sync somehow. Thanks for the suggestions! :) -ste ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
