Re: Problems with portsdb -Uu on FreeBSD 6.3
On Mon, 8 Sep 2008 19:43:14 -0400 Sean Cavanaugh [EMAIL PROTECTED] wrote: I've never fully trusted portsnap. I do run portsnap fetch before every portupgrade but I always follow it up with CVSUP and I usually find some more files that get changed anyway. portsnap fetch doesn't affect your ports tree at all, you need to follow it with portsnap update. There's no sense in in routinely mixing the two tools on the same tree. If you do find that portsnap isn't updating the tree correctly then you've either found a bug or have some corrupt data somewhere. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portsdb -Uu on FreeBSD 6.3
On Mon, 8 Sep 2008 17:57:16 -0700 perikillo [EMAIL PROTECTED] wrote: On Mon, Sep 8, 2008 at 5:26 PM, Michael Powell [EMAIL PROTECTED]wrote: Please don't top-post. Unless you have a specific overriding reason to do -Uu you might want to try -uF instead. It's what I use and it's always worked. In fact, this is what I do to see if I need an upgrade: csup -L 2 ports portsdb -uF pkgdb -u portversion But since I have never used portsnap don't really know anything about it. -Mike I have been trying a lot of things, I want to start again, I think I just need to delete /usr/ports? Let me read again the manual and see those Flags. I remember that the first time u run portsdb the manuals recommend to sue Uu, but let read the manual page, I will back soon!!! portsdb -F and portsdb -U, both update the index file. The first downloads it, the second creates it from scratch (which is slow). Portsnap handles this automatically, so neither will be needed. The work done by portsdb -u will be done automatically when portupgrade is next run, but it may save a little time later. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portsdb -Uu on FreeBSD 6.3
On Tue, Sep 9, 2008 at 6:13 AM, RW [EMAIL PROTECTED] wrote: On Mon, 8 Sep 2008 17:57:16 -0700 perikillo [EMAIL PROTECTED] wrote: On Mon, Sep 8, 2008 at 5:26 PM, Michael Powell [EMAIL PROTECTED]wrote: Please don't top-post. Unless you have a specific overriding reason to do -Uu you might want to try -uF instead. It's what I use and it's always worked. In fact, this is what I do to see if I need an upgrade: csup -L 2 ports portsdb -uF pkgdb -u portversion But since I have never used portsnap don't really know anything about it. -Mike I have been trying a lot of things, I want to start again, I think I just need to delete /usr/ports? Let me read again the manual and see those Flags. I remember that the first time u run portsdb the manuals recommend to sue Uu, but let read the manual page, I will back soon!!! portsdb -F and portsdb -U, both update the index file. The first downloads it, the second creates it from scratch (which is slow). Portsnap handles this automatically, so neither will be needed. The work done by portsdb -u will be done automatically when portupgrade is next run, but it may save a little time later. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] After finally realize that running portsdb -Uu each time I sync my ports is not a good way, I will follow the Michael Powell tip. Thanks all for your help, I still don't know why always appear the port apcupsd went this thing crush. Thanks all for your great help!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
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 I try to follow some sites solutions but no luck, I remove the port portupgrade and install again but again no luck, download the Index file, etc, etc, today I build a server, fresh install, update my ports with portsnap, them run the portsdb -Uu and again the same error. This could not be the sync of the server and my files, because the last time I try to sync my servers this was the same error I got today. I don't know if this is the only way we can have our ports sync: portsnap fetch portsnap update portsdb -Uu ? This is my normal commands I use to sync my ports, maybe I am wrong please confirm this if I'am wrong, but the error appear right in my server, what could I do to fix this error? I have seen other people with the same error and no solution yet. sysutils/apcupsd failed Thanks all for your time!!! FreeBSD 6.3-Release!!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portsdb -Uu on FreeBSD 6.3
-- From: perikillo [EMAIL PROTECTED] 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portsdb -Uu on FreeBSD 6.3
On Mon, Sep 8, 2008 at 6:12 PM, Sean Cavanaugh [EMAIL PROTECTED] wrote: -- From: perikillo [EMAIL PROTECTED] 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portsdb -Uu on FreeBSD 6.3
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 [EMAIL PROTECTED] wrote: On Mon, Sep 8, 2008 at 6:12 PM, Sean Cavanaugh [EMAIL PROTECTED] wrote: -- From: perikillo [EMAIL PROTECTED] 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portsdb -Uu on FreeBSD 6.3
-- From: perikillo [EMAIL PROTECTED] Sent: Monday, September 08, 2008 7:25 PM To: FreeBSD Mailing List freebsd-questions@freebsd.org Subject: Re: Problems with portsdb -Uu on FreeBSD 6.3 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!!! I've never fully trusted portsnap. I do run portsnap fetch before every portupgrade but I always follow it up with CVSUP and I usually find some more files that get changed anyway. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portsdb -Uu on FreeBSD 6.3
=# Install the BIND libs and include files # # To build sys/modules when building the world (our old way of doing things) #MODULES_WITH_WORLD=# do not build modules when building kernel # # The list of modules to build instead of all of them. #MODULES_OVERRIDE= linux ipfw # # The list of modules to never build, applied *after* MODULES_OVERRIDE. #WITHOUT_MODULES= bktr plip # # NO_MANCOMPRESS= #PRINTERDEVICE= ps BOOTWAIT=0 # COM1: = 0x3F8, COM2: = 0x2F8, COM3: = 0x3E8, COM4: = 0x2E8 #BOOT_COMCONSOLE_PORT= 0x3F8 BOOT_COMCONSOLE_SPEED= 115200 #LOADER_TFTP_SUPPORT= YES #ENABLE_SUID_K5SU= #SUP_UPDATE= # #SUP=/usr/bin/csup #SUPFLAGS= -g -L 2 #SUPHOST=cvsup.uk.FreeBSD.org #SUPFILE=/usr/share/examples/cvsup/standard-supfile #PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile #DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile #TOP_TABLE_SIZE= 101 DOC_LANG= en_US.ISO8859-1 #SENDMAIL_MC=/etc/mail/myconfig.mc #SENDMAIL_SUBMIT_MC=/etc/mail/mysubmit.mc #SENDMAIL_ADDITIONAL_MC=/etc/mail/foo.mc /etc/mail/bar.mc #SENDMAIL_CF_DIR=/usr/local/share/sendmail/cf #SENDMAIL_M4_FLAGS= #with SASLv1: # SENDMAIL_CFLAGS=-I/usr/local/include/sasl1 -DSASL # SENDMAIL_LDFLAGS=-L/usr/local/lib # SENDMAIL_LDADD=-lsasl # #with SASLv2: # SENDMAIL_CFLAGS=-I/usr/local/include -DSASL=2 # SENDMAIL_LDFLAGS=-L/usr/local/lib # SENDMAIL_LDADD=-lsasl2 #SENDMAIL_CFLAGS= #SENDMAIL_LDFLAGS= #SENDMAIL_LDADD= #SENDMAIL_DPADD= #SENDMAIL_SET_USER_ID= #SENDMAIL_MAP_PERMS= NO_WPA_SUPPLICANT_EAPOL=true # added by use.perl 2008-09-06 19:36:04 PERL_VER=5.8.8 PERL_VERSION=5.8.8 This could be a bug or what? What else I could do? Thanks for your support!!! On Mon, Sep 8, 2008 at 4:43 PM, Sean Cavanaugh [EMAIL PROTECTED]wrote: -- From: perikillo [EMAIL PROTECTED] Sent: Monday, September 08, 2008 7:25 PM To: FreeBSD Mailing List freebsd-questions@freebsd.org Subject: Re: Problems with portsdb -Uu on FreeBSD 6.3 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!!! I've never fully trusted portsnap. I do run portsnap fetch before every portupgrade but I always follow it up with CVSUP and I usually find some more files that get changed anyway. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portsdb -Uu on FreeBSD 6.3
perikillo wrote: 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!!! [snip] Unless you have a specific overriding reason to do -Uu you might want to try -uF instead. It's what I use and it's always worked. In fact, this is what I do to see if I need an upgrade: csup -L 2 ports portsdb -uF pkgdb -u portversion But since I have never used portsnap don't really know anything about it. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with portsdb -Uu on FreeBSD 6.3
I have been trying a lot of things, I want to start again, I think I just need to delete /usr/ports? Let me read again the manual and see those Flags. I remember that the first time u run portsdb the manuals recommend to sue Uu, but let read the manual page, I will back soon!!! Thanks all for your support!!! On Mon, Sep 8, 2008 at 5:26 PM, Michael Powell [EMAIL PROTECTED]wrote: perikillo wrote: 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!!! [snip] Unless you have a specific overriding reason to do -Uu you might want to try -uF instead. It's what I use and it's always worked. In fact, this is what I do to see if I need an upgrade: csup -L 2 ports portsdb -uF pkgdb -u portversion But since I have never used portsnap don't really know anything about it. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu hung
David Abrahams [EMAIL PROTECTED] writes: I seem to be having the same problem described in http://www.freebsdforums.org/forums/showthread.php?t=22211, with no system calls shown by truss. My instinct is that it's unlikely to be related, even if the symptoms look similar. Unfortunately, the fix of upgrading perl from 5.6 to 5.8 doesn't apply to me: my version of Perl is already at 5.8.8, and probably was from the moment FreeBSD was installed. I'm relatively new at all this. Can someone help me set things right again? It's only happening with -a? Will it upgrade individual ports okay? Does it suck up CPU while it's hung? Have you upgraded portupgrade to 2.2.2? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu hung
Are you *sure* it's hung? -U does a make index in /usr/ports which takes *forever* as it has to run a make command in *every single port*. If you've just updated your ports tree with cvsup then consider running make fetchindex from /usr/ports which just grabs the latest pre-built version and then just doing portsdb -u, though anything that needs the .db file to be up-to-date will do this automatically. --Alex PS The thread you reference seems to be about portupgrade -a which is confusing since your subject line says portsdb -Uu. Though both part of portupgrade, the similarity ends there. Like Lowell said: Does it suck up CPU while it's hung? What does top show for CPU usage? You will probably not see any process hogging the cpu as, like I said, it's one short make after another after another after another ... repeat until sick. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu hung
Alex Zbyslaw wrote: Are you *sure* it's hung? -U does a make index in /usr/ports which takes *forever* as it has to run a make command in *every single port*. If you've just updated your ports tree with cvsup then consider running make fetchindex from /usr/ports which just grabs the latest pre-built version and then just doing portsdb -u, though anything that needs the .db file to be up-to-date will do this automatically. Just seen that portsdb -F will fetch the index and the man page even recommends running portsdb -Fu (not -Uu) after a cvsup. If -Fu still hangs for you, then you really do have a problem. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu hung
Lowell Gilbert [EMAIL PROTECTED] writes: David Abrahams [EMAIL PROTECTED] writes: I seem to be having the same problem described in http://www.freebsdforums.org/forums/showthread.php?t=22211, with no system calls shown by truss. My instinct is that it's unlikely to be related, even if the symptoms look similar. Unfortunately, the fix of upgrading perl from 5.6 to 5.8 doesn't apply to me: my version of Perl is already at 5.8.8, and probably was from the moment FreeBSD was installed. I'm relatively new at all this. Can someone help me set things right again? It's only happening with -a? Will it upgrade individual ports okay? Does it suck up CPU while it's hung? Have you upgraded portupgrade to 2.2.2? It eventually finished after seeming to make no progress and not showing up in top for the longest time. Sorry for the false (?) alarm. -- Dave Abrahams Boost Consulting www.boost-consulting.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -Uu hung
I seem to be having the same problem described in http://www.freebsdforums.org/forums/showthread.php?t=22211, with no system calls shown by truss. Unfortunately, the fix of upgrading perl from 5.6 to 5.8 doesn't apply to me: my version of Perl is already at 5.8.8, and probably was from the moment FreeBSD was installed. I'm relatively new at all this. Can someone help me set things right again? TIA, -- Dave Abrahams Boost Consulting www.boost-consulting.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -Uu
I am using portsnap fetch portsnap update to sync my ports tree on FreeBSd 6.1...it seems it maintains an index when I run update. I am used to using: portsversion and portsupdate to upgrade ports...in this method I have also used portsdb -Uu to rebuild an index anytime prior to running these commands...yes portsdb takes a while and I've always wondered if this is necessary prior to running any of these commands.. So my question is: Is the index being maintained by portsnap the same or a replacement to that used by portupgrade? Do I have to maintain both sets of indexes in order to use portsupdate?? What do other people do? thanks, ke han ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu
ke han wrote: I am using portsnap fetch portsnap update to sync my ports tree on FreeBSd 6.1...it seems it maintains an index when I run update. Yes. I am used to using: portsversion and portsupdate to upgrade ports...in this method I have also used portsdb -Uu to rebuild an index anytime prior to running these commands...yes portsdb takes a while and I've always wondered if this is necessary prior to running any of these commands.. portsdb -Uu does two things: 1. It rebuilds the ports INDEX. This is done by portsdb -U and takes a long time. 2. It rebuilds the ports INDEX.db database. This is done by portsdb -u, takes only a few seconds, and is done automatically when you run portupgrade if the database is out of date. So my question is: Is the index being maintained by portsnap the same or a replacement to that used by portupgrade? Do I have to maintain both sets of indexes in order to use portsupdate?? The ports INDEX file generated by portsdb -U is the same file as portsnap generates. Since the INDEX.db database is generated automatically, this means there is no need to run portsdb between running portsnap and running portupgrade. My standard ports update/upgrade procedure is: portsnap fetch portsnap update pkg_version -vIL= # this is equivalent to portversion -vL= portupgrade -a Colin Percival ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu
On Thu, Sep 14, 2006 at 11:58:46PM -0700, Colin Percival wrote: ke han wrote: I am using portsnap fetch portsnap update to sync my ports tree on FreeBSd 6.1...it seems it maintains an index when I run update. Yes. I am used to using: portsversion and portsupdate to upgrade ports...in this method I have also used portsdb -Uu to rebuild an index anytime prior to running these commands...yes portsdb takes a while and I've always wondered if this is necessary prior to running any of these commands.. portsdb -Uu does two things: 1. It rebuilds the ports INDEX. This is done by portsdb -U and takes a long time. 2. It rebuilds the ports INDEX.db database. This is done by portsdb -u, takes only a few seconds, and is done automatically when you run portupgrade if the database is out of date. So my question is: Is the index being maintained by portsnap the same or a replacement to that used by portupgrade? Do I have to maintain both sets of indexes in order to use portsupdate?? The ports INDEX file generated by portsdb -U is the same file as portsnap generates. Since the INDEX.db database is generated automatically, this means there is no need to run portsdb between running portsnap and running portupgrade. My standard ports update/upgrade procedure is: portsnap fetch portsnap update pkg_version -vIL= # this is equivalent to portversion -vL= portupgrade -a When I installed portsnap with 'portsnap fetch extract' and then ran portupgrade -fa (this was during an update from 6.x to 7.x), it replaced the index with the one from 'make fetchindex'. Colin Percival ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] pgp7uA9adYyeW.pgp Description: PGP signature
portsdb -Uu broken on AMD64 system
Hi folks, how are you all doing? My AMD64 system running FreeBSD 6.1 gave me a very strange error when trying to update my ports. I used the cvsup -g -L -2 command and everything went smooth, but after I did the portsdb -Uu command this is what I get: portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..1 open conditional: at line 1477 (evaluated to true) make: fatal errors encountered -- cannot continue === arabic/ae_fonts_mono failed *** Error code 1 1 open conditional: at line 22 (evaluated to true) make: fatal errors encountered -- cannot continue === accessibility/at-spi failed *** Error code 1 2 errors Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the ports-all collection, and have no refuse files.) If that is the case, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, your architecture, your environment, and your /etc/make.conf settings, especially compiler flags and WITH/WITHOUT settings). Note: the latest pre-generated version of INDEX may be fetched automatically with make fetchindex. *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error I already tried the make fetchindex but that gives the same error. My make.conf looks like: # added by use.perl 2006-02-28 15:03:26 PERL_VER=5.8.8 PERL_VERSION=5.8.8 The last time I had troubles is when I tried to compile the port scilab and it complained about my tk installation. I left it like that. Hope somebody can help. Here's my uname -a : FreeBSD zouk.tiscali.nl 6.1-RELEASE-p2 FreeBSD 6.1-RELEASE-p2 #6: Mon Jun 26 21:04:39 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL amd64 __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu broken on AMD64 system
This has already been fixed. Please re-cvsup and try again. mcl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu broken on AMD64 system
Awesomeeverything works fine again! You are getting faster and faster at these forums as time progresses:-) Just today I presented a plan at the company where I'm employed to use a open source BI tool and emphasized that the support from the community is excellent!! FreeBSD is NO EXCEPTION!!! Thanks --- Mark Linimon [EMAIL PROTECTED] wrote: This has already been fixed. Please re-cvsup and try again. mcl __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
I want to ask you: how long does it take you to cvsup your ports, run 'portsdb -Uu', and finish with 'portversion -l '? To run 'portsnap fetch update', then 'portversion -v | grep needs', it took less then 55 seconds and I was off upgrading ports. The procedure I used had no errors. I think it takes about 40 minutes to run portsdb -Uu on my normal P4 desktop, and several hours inside a virtual machine. My old P3 laptop took 2 hours. Portsnap took about 1 minute, it was very fast. The procedure I used had no errors. Everyone that knows what they are doing never seem to have a problem. Generally people say, I just did a 'portsnap -AbCdDeF' and it worked great!, but then it turns out that command was one of many that preceeded and followed it, which they neglected to mention. Both ways of upgrading work. Neither way will tell you about the conflict between pilot-link and libmal. You're going to have to find out about during an upgrade or, or wait and read about it on the list. So you can't be talking about that as a problem with portsnap. Just what was the problem you had with portsnap? I believe I had a stale dependency with imagemagic that I chose to force to continue. That was on a brand new install, and it happend twice (I tried reinstalling). Maybe I can try to recreate it in a VMWare virtual machine so I can reproduce it. I think I also got the ruby error, if that was the one that happend about 1 year ago. I remember doing an upgrade which broke the system, so I reinstalled it a few days later. Also, is it not possible to make a system that does not have conflicts? Maybe OS's are simply too complex. It would seem like there should be a way to kick off a global update and rebuild that started with the core pieces first, and then moved up the dependency tree level-by-level. Something that was 100% guaranteed to work, and took 1 command. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
Xn Nooby wrote: I want to ask you: how long does it take you to cvsup your ports, run 'portsdb -Uu', and finish with 'portversion -l '? To run 'portsnap fetch update', then 'portversion -v | grep needs', it took less then 55 seconds and I was off upgrading ports. The procedure I used had no errors. I think it takes about 40 minutes to run portsdb -Uu on my normal P4 desktop, and several hours inside a virtual machine. My old P3 laptop took 2 hours. Portsnap took about 1 minute, it was very fast. The procedure I used had no errors. Everyone that knows what they are doing never seem to have a problem. Generally people say, I just did a 'portsnap -AbCdDeF' and it worked great!, but then it turns out that command was one of many that preceeded and followed it, which they neglected to mention. Both ways of upgrading work. Neither way will tell you about the conflict between pilot-link and libmal. You're going to have to find out about during an upgrade or, or wait and read about it on the list. So you can't be talking about that as a problem with portsnap. Just what was the problem you had with portsnap? I believe I had a stale dependency with imagemagic that I chose to force to continue. That was on a brand new install, and it happend twice (I tried reinstalling). Maybe I can try to recreate it in a VMWare virtual machine so I can reproduce it. I think I also got the ruby error, if that was the one that happend about 1 year ago. I remember doing an upgrade which broke the system, so I reinstalled it a few days later. Also, is it not possible to make a system that does not have conflicts? Maybe OS's are simply too complex. It would seem like there should be a way to kick off a global update and rebuild that started with the core pieces first, and then moved up the dependency tree level-by-level. Something that was 100% guaranteed to work, and took 1 command. You could try portmanager 'sysutils/portmanager'. The command: portmanager -u -f -l -y will rebuild all of the installed ports in a logical manner as well as creating a log file for the user to examine if necessary. I would recommend cleaning out /usr/ports/distfiles and then running: portsclean -C -D -DD -L -P -PP prior to running that command. This will ensure that all the crud from previous installations will be removed ensuring a clean start. Just my 2ยข. -- Gerard Seibert [EMAIL PROTECTED] Man invented language to satisfy his deep need to complain. Lily Tomlin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
Xn Nooby writes: Everyone that knows what they are doing never seem to have a problem. Respectfully, rubbish. I use portupgrade; where it seems applicable I am careful to mention one ought to read the manual completely, and to state my experiences where it has clearly and without provocation Done the Wrong Thing. Similar behavior can be observed in other posters, with a statistical bias toward the more technically experienced. (Your mileage may vary.) Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
On 2/5/06, Robert Huff [EMAIL PROTECTED] wrote: Xn Nooby writes: Everyone that knows what they are doing never seem to have a problem. Respectfully, rubbish. I use portupgrade; where it seems applicable I am careful to mention one ought to read the manual completely, and to state my experiences where it has clearly and without provocation Done the Wrong Thing. Similar behavior can be observed in other posters, with a statistical bias toward the more technically experienced. (Your mileage may vary.) Okay. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
portmanager -u -f -l -y will rebuild all of the installed ports in a logical manner as well as creating a log file for the user to examine if necessary. I will try that, thx! I will also look in to: portmanager portsclean portsnap portversion (any others?) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
On 2/4/06, Xn Nooby [EMAIL PROTECTED] wrote:
It just does, after you cvsup new ports cd into /usr/ports and type
make fetchindex. what way is the old foolproof way?
Here is how I update my system (without using a 'make fetchindex')
cvsup -g -L 2 /root/stable-supfile
less UPDATING
make buildworld
make buildkernel
make installkernel
shutdown now
cd /usr/src
make installworld
mergemaster
shutdown -r now
portsdb -Uu
portversion -l
portupgrade -arR
reboot
It takes forever, but it works everytime. Everything else I've ever tried
has always had some kind of error, and I never know what they mean or what I
should do.
Maybe by never doing a fetchindex, I've never really updated my system, and
thats why its never had a problem, lol. That would be embarassing.
No, If I remember right (someone step in if I'm wrong) make fetchindex
is what you would get if you ran portsdb -Uu.
By the looks of it when you cvsup you get everything (src-all,
ports-all, etc) all at once. I think it might be better if you split
that into two sup-files where you would have one for the system,
src-all, and the other one for ports. This way you don't have to
rebuild the system every time you update your ports, this also works
the other way around. Once a branch is cut and declared -STABLE the
libraries used to make your programs work are rarely changed, If it
does change they will tell you in /usr/src/UPDATING. For the sake of
troubleshooting it helps if you don't change everything all at once.
This is what I, generally, do when updating ports:
1. cvsup -g -L 2 ~/ports-supfile
2. cd /usr/ports; make fetchindex
3. more UPDATING
4. pkg_version | grep
5. nice +20 portupgrade -rRW pkgname_glob
Repeat steps 4 and 5 until done.
6. portsclean -CDD (optional)
On my home system I typically do this once a week starting with step 1
on Saturday and then upgrading the ports at my leisure over the course
of the week. Right now I have 'portsclean -C; nice +20 portupgrade
-rfWw expat*' running in the background, why you ask? The reason is
in /usr/ports/UPDATING, you must always read this file before you
upgrade your ports. And the way I clean, or don't clean, ports
probably looks erratic but I have my reasons, they are mostly just to
save time.
One thing I have noticed, and stopped doing, is changing the default
values for CFLAGS and CXXFLAGS via /etc/make.conf. It's easy to screw
up the stability of your system if you set them and then use automated
tools such as portupgrade. Also of note is not setting CPUTYPE too
high in make.conf, I have a p4 but I set it to p2. You can set
individual build options for each port in pkg-tools.conf located in
/usr/local/etc but I like to set them in make.conf because the build
options are set in stone then, make will always use these options
regardless of how or who built the port. You can do this with a simple
.if .endif block, two examples from one of my 5.4 servers are below:
.if ${.CURDIR:M*/lang/php4}
WITHOUT_MYSQL=yes WITH_POSTGRESQL=yes WITHOUT_MCAL=yes
.endif
.if ${.CURDIR:M*/net/samba3}
WITH_SAM_PGSQL=yes WITH_SYSLOG=yes WITH_ACL_SUPPORT=yes WITH_QUOTAS=yes
.endif
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
Denny White wrote: Today Xn Nooby spake forth boldly: It just does, after you cvsup new ports cd into /usr/ports and type make fetchindex. what way is the old foolproof way? Here is how I update my system (without using a 'make fetchindex') cvsup -g -L 2 /root/stable-supfile less UPDATING make buildworld make buildkernel make installkernel shutdown now cd /usr/src make installworld mergemaster shutdown -r now portsdb -Uu portversion -l portupgrade -arR reboot It takes forever, but it works everytime. Everything else I've ever tried has always had some kind of error, and I never know what they mean or what I should do. Maybe by never doing a fetchindex, I've never really updated my system, and thats why its never had a problem, lol. That would be embarassing. ___ Try portsdb -uUF I'm beginning to think it should be, try reading the manpage, where portsdb suggests that unless you define special macros in /etc/make.conf and the dependency of some ports are changed, `portsdb -Fu` is your best option (fetch the pre-built INDEX and then make index.db locally). The reason `portsdb -Uu` takes so long is that it has a lot of work to do on a very large file tree. Oh, and I love Nikolas's nice +20 portupgrade, but only if it is scripted over the weekend or something. I'll have to try it. Kevin Kinsey -- [Prime Minister Joseph] Chamberlain loves the working man, he loves to see him work. -- Winston Churchill ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
Nikolas Britton writes: 4. pkg_version | grep Consider instead: portsversion -l to which I usually append: | sendmail huff in case I want to do the upgrade later. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Today Xn Nooby spake forth boldly: It just does, after you cvsup new ports cd into /usr/ports and type make fetchindex. what way is the old foolproof way? Here is how I update my system (without using a 'make fetchindex') cvsup -g -L 2 /root/stable-supfile less UPDATING make buildworld make buildkernel make installkernel shutdown now cd /usr/src make installworld mergemaster shutdown -r now portsdb -Uu portversion -l portupgrade -arR reboot It takes forever, but it works everytime. Everything else I've ever tried has always had some kind of error, and I never know what they mean or what I should do. Maybe by never doing a fetchindex, I've never really updated my system, and thats why its never had a problem, lol. That would be embarassing. ___ Try portsdb -uUF Please do not CC me. Already subscribed to mailing list. GnuPG key : 0x1644E79A | http://wwwkeys.nl.pgp.net Fingerprint: D0A9 AD44 1F10 E09E 0E67 EC25 CB44 F2E5 1644 E79A -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (OpenBSD) iD8DBQFD5Hbsy0Ty5RZE55oRAlr9AJ0XLqkm4vTDasR1PDRSCbl9e2+VKACfU4XQ oHFZVw5HuVkkrhs6Yuy7S1s= =NXHH -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
Nikolas Britton [EMAIL PROTECTED] writes: No, If I remember right (someone step in if I'm wrong) make fetchindex is what you would get if you ran portsdb -Uu. Assuming nothing has been checked in between (1) the building of the index on the server (which you get from fetchindex), and (2) the last snapshot of the ports tree that your cvsup server has taken. In general, these will not be exactly the same, but close enough that the difference hardly ever matters. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
On 04 Feb 2006 16:12:29 -0500, Lowell Gilbert [EMAIL PROTECTED] wrote: Nikolas Britton [EMAIL PROTECTED] writes: No, If I remember right (someone step in if I'm wrong) make fetchindex is what you would get if you ran portsdb -Uu. Assuming nothing has been checked in between (1) the building of the index on the server (which you get from fetchindex), and (2) the last snapshot of the ports tree that your cvsup server has taken. In general, these will not be exactly the same, but close enough that the difference hardly ever matters. portsdb -Uu runs make index which is some disastrously slow text processing (can make replace groff and sed and awk? should it?). portsnap is the white belt you can type. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
By the looks of it when you cvsup you get everything (src-all, ports-all, etc) all at once. I think it might be better if you split that into two sup-files where you would have one for the system, src-all, and the other one for ports. This way you don't have to rebuild the system every time you update your ports, this also works the other way around. Once a branch is cut and declared -STABLE the libraries used to make your programs work are rarely changed, If it does change they will tell you in /usr/src/UPDATING. For the sake of troubleshooting it helps if you don't change everything all at once. I thought that maybe by changing everything at once, I would avoid mismatched libraries. Someone should write a book on all this stuff, and explain it thoroughly, with various case examples. When I use the old slow way, I never get an error - when I use portsnap, I do. This makes me inclined to never use portsnap, regardless of how fast it is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
On Saturday 04 February 2006 16:56, Xn Nooby wrote: By the looks of it when you cvsup you get everything (src-all, ports-all, etc) all at once. I think it might be better if you split that into two sup-files where you would have one for the system, src-all, and the other one for ports. This way you don't have to rebuild the system every time you update your ports, this also works the other way around. Once a branch is cut and declared -STABLE the libraries used to make your programs work are rarely changed, If it does change they will tell you in /usr/src/UPDATING. For the sake of troubleshooting it helps if you don't change everything all at once. I thought that maybe by changing everything at once, I would avoid mismatched libraries. Someone should write a book on all this stuff, and explain it thoroughly, with various case examples. When I use the old slow way, I never get an error - when I use portsnap, I do. This makes me inclined to never use portsnap, regardless of how fast it is. ___ Xn, it appears to me that you are doing a lot off work for not much gain. There's no reason to do a buildworld sequence everytime you upgrade the ports tree. There's no reason to do a massive portupgrade just because you did a buildworld sequence. I you are running a release version (the same goes for a security release), the only time you should have to do a buildworld sequence is if there's been a security update, and that's pretty much it. If you're running a stable version, you may run a buildworld sequence more often, but not necessarily. Now, if you want to run portsdb -Uu, that's up to you; but by the time you get done with the sequence you use for updating your ports tree and get into upgrading with portugrade -arR, I'll be done and using the system. Portsnap doesn't have errors. 'Make fetch index' doesn't have errors. Not too long ago, portsdb had a problem with ruby and a great cry went up in userland. And much advise was given by the users who didn't have the problem to the users who did, most of it false. A few good workarounds came out of it though. I want to ask you: how long does it take you to cvsup your ports, run 'portsdb -Uu', and finish with 'portversion -l '? To run 'portsnap fetch update', then 'portversion -v | grep needs', it took less then 55 seconds and I was off upgrading ports. The procedure I used had no errors. Both ways of upgrading work. Neither way will tell you about the conflict between pilot-link and libmal. You're going to have to find out about during an upgrade or, or wait and read about it on the list. So you can't be talking about that as a problem with portsnap. Just what was the problem you had with portsnap? Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
On 2/1/06, Xn Nooby [EMAIL PROTECTED] wrote: Since I've gone back to the old foolproof way of updating my system, I'm doing a portsdb -Uu again - which has always taken forever to run on my various machines. Is there a way to speed it up (without replacing it), or has anyone looked at it to see if it needs rewriting? I worked at a place where a monthly mainframe job ran for 24 hours, and the whole plant had to shutdown while it ran (which wasnt too big a deal since it was on Sunday). When the job started taking 36 hours to run and the original programmer was too busy to fix it, they brought in a consultant to help. He re-wrote the job so it ran in 15 minutes. The original programmer was fired two days later. Since then, I've always been suspicous of jobs that run for long periods of time. It just does, after you cvsup new ports cd into /usr/ports and type make fetchindex. what way is the old foolproof way? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why does portsdb -Uu run so long?
It just does, after you cvsup new ports cd into /usr/ports and type make fetchindex. what way is the old foolproof way? Here is how I update my system (without using a 'make fetchindex') cvsup -g -L 2 /root/stable-supfile less UPDATING make buildworld make buildkernel make installkernel shutdown now cd /usr/src make installworld mergemaster shutdown -r now portsdb -Uu portversion -l portupgrade -arR reboot It takes forever, but it works everytime. Everything else I've ever tried has always had some kind of error, and I never know what they mean or what I should do. Maybe by never doing a fetchindex, I've never really updated my system, and thats why its never had a problem, lol. That would be embarassing. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Why does portsdb -Uu run so long?
Since I've gone back to the old foolproof way of updating my system, I'm doing a portsdb -Uu again - which has always taken forever to run on my various machines. Is there a way to speed it up (without replacing it), or has anyone looked at it to see if it needs rewriting? I worked at a place where a monthly mainframe job ran for 24 hours, and the whole plant had to shutdown while it ran (which wasnt too big a deal since it was on Sunday). When the job started taking 36 hours to run and the original programmer was too busy to fix it, they brought in a consultant to help. He re-wrote the job so it ran in 15 minutes. The original programmer was fired two days later. Since then, I've always been suspicous of jobs that run for long periods of time. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/usr/local/bin/pg_config: not found Error msg Running Portsdb -Uu
Hi folks, Just cvsup'd my system (5.4-RELEASE FreeBSD 5.4-RELEASE #0:) and rec'd the following error msg: ==[EMAIL PROTECTED]:/var/db portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait../usr/local/bin/pg_config: not found Makefile, line 47: warning: /usr/local/bin/pg_config --includedir returned non-zero status /usr/local/bin/pg_config: not found Makefile, line 48: warning: /usr/local/bin/pg_config --libdir returned non-zero status Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.6 Done. done Duplicate entries appear often but I'm not familiar with the Makefile warnings. Would appreciate any assistance in determining first steps for resolving them. Already researched Google -FreeBSD and the mailing list archive for the most recent 25 questions. Thnx, Bob Perry ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error message while running 'portsdb -Uu'
On Mon, Oct 24, 2005 at 08:27:21PM -0400, Gerard Seibert wrote: I just updated my ports using cvsup and then proceeded to run 'portsdb -Uu' to generate the index file. Upon completion, it produced this error message: Updating the ports index ... Generating INDEX.tmp - please wait..jot: infinite sequences cannot be bounded Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot: infinite sequences cannot be bounded /usr/ports/editors/vim-lite/../vim/Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot: infinite sequences cannot be bounded /usr/ports/editors/vim6+ruby/../vim/Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.6 Warning: Duplicate INDEX entry: mod_frontpage2-5.0.2.2635 Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 Done. I have never seen that one before. What does it mean, and what should I do to correct it, it anything? cvsup again, and in general, read discussion on ports@ before sending duplicate reports :) Kris pgpAgS7lTvPf8.pgp Description: PGP signature
Re[2]: Error message while running 'portsdb -Uu'
On Tuesday, October 25, 2005 2:03:43 PM, Kris Kennaway [EMAIL PROTECTED] Subject: Re: Error message while running 'portsdb -Uu' Wrote these words of wisdom: On Mon, Oct 24, 2005 at 08:27:21PM -0400, Gerard Seibert wrote: I just updated my ports using cvsup and then proceeded to run 'portsdb -Uu' to generate the index file. Upon completion, it produced this error message: Updating the ports index ... Generating INDEX.tmp - please wait..jot: infinite sequences cannot be bounded Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot: infinite sequences cannot be bounded /usr/ports/editors/vim-lite/../vim/Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot: infinite sequences cannot be bounded /usr/ports/editors/vim6+ruby/../vim/Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.6 Warning: Duplicate INDEX entry: mod_frontpage2-5.0.2.2635 Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 Done. I have never seen that one before. What does it mean, and what should I do to correct it, it anything? cvsup again, and in general, read discussion on ports@ before sending duplicate reports :) Kris * REPLY SEPARATOR * On 10/11/2005 5:29:42 PM, Gerard Replied: Excuse me, but what 'duplicate reports' are you referring to? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error message while running 'portsdb -Uu'
On Tue, Oct 25, 2005 at 02:35:54PM -0400, Gerard Seibert wrote: On Tuesday, October 25, 2005 2:03:43 PM, Kris Kennaway [EMAIL PROTECTED] Subject: Re: Error message while running 'portsdb -Uu' Wrote these words of wisdom: On Mon, Oct 24, 2005 at 08:27:21PM -0400, Gerard Seibert wrote: I just updated my ports using cvsup and then proceeded to run 'portsdb -Uu' to generate the index file. Upon completion, it produced this error message: Updating the ports index ... Generating INDEX.tmp - please wait..jot: infinite sequences cannot be bounded Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot: infinite sequences cannot be bounded /usr/ports/editors/vim-lite/../vim/Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot: infinite sequences cannot be bounded /usr/ports/editors/vim6+ruby/../vim/Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.6 Warning: Duplicate INDEX entry: mod_frontpage2-5.0.2.2635 Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 Done. I have never seen that one before. What does it mean, and what should I do to correct it, it anything? cvsup again, and in general, read discussion on ports@ before sending duplicate reports :) Kris * REPLY SEPARATOR * On 10/11/2005 5:29:42 PM, Gerard Replied: Excuse me, but what 'duplicate reports' are you referring to? Others reporting the same problem, which was introduced a day or so ago and then fixed. Kris pgpVQtodAfSIm.pgp Description: PGP signature
Re[2]: Error message while running 'portsdb -Uu'
On Tuesday, October 25, 2005 2:59:24 PM, Kris Kennaway [EMAIL PROTECTED] Subject: Re: Error message while running 'portsdb -Uu' Wrote these words of wisdom: On Tue, Oct 25, 2005 at 02:35:54PM -0400, Gerard Seibert wrote: On Tuesday, October 25, 2005 2:03:43 PM, Kris Kennaway [EMAIL PROTECTED] Subject: Re: Error message while running 'portsdb -Uu' Wrote these words of wisdom: On Mon, Oct 24, 2005 at 08:27:21PM -0400, Gerard Seibert wrote: I just updated my ports using cvsup and then proceeded to run 'portsdb -Uu' to generate the index file. Upon completion, it produced this error message: Updating the ports index ... Generating INDEX.tmp - please wait..jot: infinite sequences cannot be bounded Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot: infinite sequences cannot be bounded /usr/ports/editors/vim-lite/../vim/Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot: infinite sequences cannot be bounded /usr/ports/editors/vim6+ruby/../vim/Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.6 Warning: Duplicate INDEX entry: mod_frontpage2-5.0.2.2635 Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 Done. I have never seen that one before. What does it mean, and what should I do to correct it, it anything? cvsup again, and in general, read discussion on ports@ before sending duplicate reports :) Kris * REPLY SEPARATOR * On 10/11/2005 5:29:42 PM, Gerard Replied: Excuse me, but what 'duplicate reports' are you referring to? Others reporting the same problem, which was introduced a day or so ago and then fixed. Kris * REPLY SEPARATOR * On 10/11/2005 5:29:42 PM, Gerard Replied: Sorry! I do not have the time to read every post, although I do try to. I must have missed those. :( -- The word spine is of course an anagram of the word penis. This is true in almost fifty percent of the languages of the Galaxy and many people have attempted to explain why. Usually the explanations get bogged down in silly ones about stand erect. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error message while running 'portsdb -Uu'
On Tuesday, October 25, 2005 2:59:24 PM, Kris Kennaway kris at obsecurity.org
Wrote these words of wisdom:
On Tue, Oct 25, 2005 at 02:35:54PM -0400, Gerard Seibert wrote:
On Tuesday, October 25, 2005 2:03:43 PM, Kris Kennaway kris at
obsecurity.org
Subject: Re: Error message while running 'portsdb -Uu'
Wrote these words of wisdom:
On Mon, Oct 24, 2005 at 08:27:21PM -0400, Gerard Seibert wrote:
I just updated my ports using cvsup and then proceeded to run 'portsdb
-Uu' to generate the index file. Upon completion, it produced this error
message:
Updating the ports index ... Generating INDEX.tmp - please wait..jot:
infinite sequences cannot be bounded Makefile, line 19: warning:
/usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot:
infinite sequences cannot be bounded
/usr/ports/editors/vim-lite/../vim/Makefile, line 19: warning:
/usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot:
infinite sequences cannot be bounded
/usr/ports/editors/vim6+ruby/../vim/Makefile, line 19: warning:
/usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status
Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.6
Warning: Duplicate INDEX entry: mod_frontpage2-5.0.2.2635
Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4
Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5
Done.
I have never seen that one before. What does it mean, and what should I
do to correct it, it anything?
cvsup again, and in general, read discussion on ports@ before sending
duplicate reports :)
Kris
I updated today with portsnap, and I'm seeing a different problem-- at
least, it appears to me to be of a much different nature:
# portsdb -uU
Updating the ports index ... Generating INDEX.tmp - please wait..
Makefile, line 30: warning: String comparison operator should be
either == or !=
Makefile, line 30: Malformed conditional (defined(PHP_VERS)
${PHP_VERS} 436)
Makefile, line 30: Need an operator
Makefile, line 32: if-less endif
Makefile, line 32: Need an operator
make: fatal errors encountered -- cannot continue
=== net/pear-Net_DNSBL failed
*** Error code 1
1 error
I haven't seen anything on -questions or -ports recently reporting
these errors. Is this related?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error message while running 'portsdb -Uu'
On Tue, Oct 25, 2005 at 08:43:34PM -0400, John DeStefano wrote:
On Tuesday, October 25, 2005 2:59:24 PM, Kris Kennaway kris at
obsecurity.org
Wrote these words of wisdom:
On Tue, Oct 25, 2005 at 02:35:54PM -0400, Gerard Seibert wrote:
On Tuesday, October 25, 2005 2:03:43 PM, Kris Kennaway kris at
obsecurity.org
Subject: Re: Error message while running 'portsdb -Uu'
Wrote these words of wisdom:
On Mon, Oct 24, 2005 at 08:27:21PM -0400, Gerard Seibert wrote:
I just updated my ports using cvsup and then proceeded to run 'portsdb
-Uu' to generate the index file. Upon completion, it produced this
error
message:
Updating the ports index ... Generating INDEX.tmp - please wait..jot:
infinite sequences cannot be bounded Makefile, line 19: warning:
/usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status
jot:
infinite sequences cannot be bounded
/usr/ports/editors/vim-lite/../vim/Makefile, line 19: warning:
/usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status
jot:
infinite sequences cannot be bounded
/usr/ports/editors/vim6+ruby/../vim/Makefile, line 19: warning:
/usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status
Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.6
Warning: Duplicate INDEX entry: mod_frontpage2-5.0.2.2635
Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4
Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5
Done.
I have never seen that one before. What does it mean, and what should
I
do to correct it, it anything?
cvsup again, and in general, read discussion on ports@ before sending
duplicate reports :)
Kris
I updated today with portsnap, and I'm seeing a different problem-- at
least, it appears to me to be of a much different nature:
# portsdb -uU
Updating the ports index ... Generating INDEX.tmp - please wait..
Makefile, line 30: warning: String comparison operator should be
either == or !=
Makefile, line 30: Malformed conditional (defined(PHP_VERS)
${PHP_VERS} 436)
Makefile, line 30: Need an operator
Makefile, line 32: if-less endif
Makefile, line 32: Need an operator
make: fatal errors encountered -- cannot continue
=== net/pear-Net_DNSBL failed
*** Error code 1
1 error
I haven't seen anything on -questions or -ports recently reporting
these errors. Is this related?
Doesn't seem to be. Do you define PHP_VERS by hand?
Kris
pgpwOC6pUHp8s.pgp
Description: PGP signature
Error message while running 'portsdb -Uu'
I just updated my ports using cvsup and then proceeded to run 'portsdb -Uu' to generate the index file. Upon completion, it produced this error message: Updating the ports index ... Generating INDEX.tmp - please wait..jot: infinite sequences cannot be bounded Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot: infinite sequences cannot be bounded /usr/ports/editors/vim-lite/../vim/Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status jot: infinite sequences cannot be bounded /usr/ports/editors/vim6+ruby/../vim/Makefile, line 19: warning: /usr/bin/jot -s -w 6.4.%03d 0 1 0 returned non-zero status Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.6 Warning: Duplicate INDEX entry: mod_frontpage2-5.0.2.2635 Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 Done. I have never seen that one before. What does it mean, and what should I do to correct it, it anything? -- Gerard Seibert [EMAIL PROTECTED] Berra's Law: You can observe a lot just by watching. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu duplicate entry warnings
Kris Kennaway wrote: On Tue, Aug 23, 2005 at 08:07:13AM -0400, bob self wrote: I've been told that these messages are not a problem. But I do think that they are warnings. How can I get rid of these warnings? You don't, they're not a problem. If you really don't want to see them, I recommend closing your eyes while running the command :-). Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.2 Warning: Duplicate INDEX entry: mod_frontpage2-5.0.2.2635 Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 I get these after running 'portsdb -Uu I've searched the archives but haven't found the solution. For (t)csh: alias portsdb 'portsdb \!:* | egrep -v Warning: Duplicate INDEX' (that's then ' at the end) For (ba)sh I think it's: alias portsdb='portsdb $@ 21 | egrep -v Warning: Duplicate INDEX' This is the power of Unix. Use it. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -Uu duplicate entry warnings
I've been told that these messages are not a problem. But I do think that they are warnings. How can I get rid of these warnings? Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.2 Warning: Duplicate INDEX entry: mod_frontpage2-5.0.2.2635 Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 I get these after running 'portsdb -Uu I've searched the archives but haven't found the solution. Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu duplicate entry warnings
On Tue, Aug 23, 2005 at 08:07:13AM -0400, bob self wrote: I've been told that these messages are not a problem. But I do think that they are warnings. How can I get rid of these warnings? You don't, they're not a problem. If you really don't want to see them, I recommend closing your eyes while running the command :-). Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.2 Warning: Duplicate INDEX entry: mod_frontpage2-5.0.2.2635 Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.4 Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 I get these after running 'portsdb -Uu I've searched the archives but haven't found the solution. Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] pgpchNMzRiyAL.pgp Description: PGP signature
Re: FreeBSD dieing, now has died doing portsdb -uU
On Tue, Jun 21, 2005 at 11:04:44PM -0400, Matt Juszczak wrote: Hi all, In relation to my previous post(s) (I no longer know the subject line), my freebsd mail server died again, this time while I was doinga portsdb -uU ... it got halfway through and crapped out. Check your hardware for overheating, power-supply problems and flakey memory chips. -- Jonathan Chen [EMAIL PROTECTED] -- You can get farther with a kind word and a gun than you can with a kind word alone - Al Capone ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD dieing, now has died doing portsdb -uU
Jonathan Chen wrote: On Tue, Jun 21, 2005 at 11:04:44PM -0400, Matt Juszczak wrote: Hi all, In relation to my previous post(s) (I no longer know the subject line), my freebsd mail server died again, this time while I was doinga portsdb -uU ... it got halfway through and crapped out. Check your hardware for overheating, power-supply problems and flakey memory chips. Agreed - we may indeed find out he's running an AMD. Can we say HOT?! -- Best regards, Chris The man who has no more problems is out of the game. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD dieing, now has died doing portsdb -uU
Chris wrote: Jonathan Chen wrote: On Tue, Jun 21, 2005 at 11:04:44PM -0400, Matt Juszczak wrote: Hi all, In relation to my previous post(s) (I no longer know the subject line), my freebsd mail server died again, this time while I was doinga portsdb -uU ... it got halfway through and crapped out. Check your hardware for overheating, power-supply problems and flakey memory chips. Agreed - we may indeed find out he's running an AMD. Can we say HOT?! Have a look at http://www.silentpcreview.com/article169-page2.html (Heat and Power section). Kind of disagrees with you... --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD dieing, now has died doing portsdb -uU
Hi all, In relation to my previous post(s) (I no longer know the subject line), my freebsd mail server died again, this time while I was doinga portsdb -uU ... it got halfway through and crapped out. Any ideas would help as we're kind of in the middle of a mail transfer, Regards, Matt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -uU error
Anybody else seeing this error? portsdb -uU Updating the ports index ... Generating INDEX.tmp - please wait..Variable PKGNAMESUFFIX is recursive. === x11-wm/fvwm2 failed *** Error code 1 1 error -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU error
On 6/10/05, Steven Friedrich [EMAIL PROTECTED] wrote: Anybody else seeing this error? portsdb -uU Updating the ports index ... Generating INDEX.tmp - please wait..Variable PKGNAMESUFFIX is recursive. === x11-wm/fvwm2 failed *** Error code 1 1 error -- i386 FreeBSD 4.11-STABLE Yes, I've had the same error, but not specifically x11-wm/fvwm2 failed, and on 5.4-RELEASE. cvsup your ports again, then try portsdb -uU again. You could also portsdb -uF instead - that will fetch the index from freebsd.org, instead of building it locally. I think that might require that you cvsup ports-all, with no exclusions. -- Mark Jones (Sorry if you got this twice, Steven, forgot to send it to the list the first time.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU error
On Fri, Jun 10, 2005 at 10:06:09AM -0500, Mark Jones wrote: On 6/10/05, Steven Friedrich [EMAIL PROTECTED] wrote: Anybody else seeing this error? portsdb -uU Updating the ports index ... Generating INDEX.tmp - please wait..Variable PKGNAMESUFFIX is recursive. === x11-wm/fvwm2 failed *** Error code 1 1 error -- i386 FreeBSD 4.11-STABLE Yes, I've had the same error, but not specifically x11-wm/fvwm2 failed, and on 5.4-RELEASE. The same error, except it's completely different? :) The real same error has been reported and discussed on freebsd-ports, so you should review the discussion there. Kris pgpxvBK1BJmFj.pgp Description: PGP signature
portsdb -uU error (I also need some tips)
Hello! There's been a lot of mess in my ports lately. I want to get rid of this: pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded Which pops up every time I install/deinstall a port or package. I have done a 'pkgdb -F' which seemed to work. Upon 'portsdb -uU' I get: # Updating the ports index ... Generating INDEX.tmp - please wait..cannot create /tmp/index.UHO8TTKq/INDEX.tmp.desc.german: No such file or directory *** Error code 2 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the ports-all collection, and have no refuse files.) If that is the case, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, your architecture, your environment, and your /etc/make.conf settings, especially compiler flags and WITH/WITHOUT settings). Note: the latest pre-generated version of INDEX may be fetched automatically with make fetchindex. *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. No such file or directory - /tmp/INDEX8274.0 portsdb: index chmod error # So what is this? Also, can anybody tell me if these commands are all I need to do a full cleanup and upgrade of my ports? This is my /root/make.PORTS: # cvsup -g -L 2 /etc/cvsupfile pkgdb -F portupgrade -ra portsdb -uU portupgrade -ra pkgdb -F # Thank you all so much! All the best, -- Fafa -- ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU error (I also need some tips)
On 03/13/05 12:09:24, Fafa Diliha Romanova wrote: Hello! There's been a lot of mess in my ports lately. I want to get rid of this: pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded Which pops up every time I install/deinstall a port or package. I have done a 'pkgdb -F' which seemed to work. Upon 'portsdb -uU' I get: It looks like a problem with /var/db/pkg. You have time to wipe /var/db/pkg and remove all ports? Try portmanager before you wipe your ports and db. Have you cd /usr/ports mkae fetchindex? Stop in /usr/ports. No such file or directory - /tmp/INDEX8274.0 portsdb: index chmod error chmod error? Are you root or what? # So what is this? Also, can anybody tell me if these commands are all I need to do a full cleanup and upgrade of my ports? This is my /root/make.PORTS: # cvsup -g -L 2 /etc/cvsupfile pkgdb -F portupgrade -ra portsdb -uU portupgrade -ra pkgdb -F Don't do pkgdb unattended, you may need to answer questions. You could skip all this index stuff if you use portmanager. But you need /var/db/pkg in good condition to use pormanager, I think? # Thank you all so much! All the best, -- Fafa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU error (I also need some tips)
Fafa Diliha Romanova wrote: Hello! There's been a lot of mess in my ports lately. I want to get rid of this: pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded Which pops up every time I install/deinstall a port or package. I have done a 'pkgdb -F' which seemed to work. Upon 'portsdb -uU' I get: # Updating the ports index ... Generating INDEX.tmp - please wait..cannot create /tmp/index.UHO8TTKq/INDEX.tmp.desc.german: No such file or directory *** Error code 2 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the ports-all collection, and have no refuse files.) If that is the case, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, your architecture, your environment, and your /etc/make.conf settings, especially compiler flags and WITH/WITHOUT settings). Note: the latest pre-generated version of INDEX may be fetched automatically with make fetchindex. *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. No such file or directory - /tmp/INDEX8274.0 portsdb: index chmod error # So what is this? Also, can anybody tell me if these commands are all I need to do a full cleanup and upgrade of my ports? This is my /root/make.PORTS: # cvsup -g -L 2 /etc/cvsupfile pkgdb -F portupgrade -ra portsdb -uU portupgrade -ra pkgdb -F # Thank you all so much! All the best, -- Fafa This may not fix all of your problems, but doing a cd /usr/ports make fetchindex is much faster and less problematic than portsdb -uU ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU error (I also need some tips)
On Sunday 13 March 2005 11:01 am, Jason Henson wrote: On 03/13/05 12:09:24, Fafa Diliha Romanova wrote: Hello! There's been a lot of mess in my ports lately. I want to get rid of this: pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded Which pops up every time I install/deinstall a port or package. I have done a 'pkgdb -F' which seemed to work. Upon 'portsdb -uU' I get: It looks like a problem with /var/db/pkg. You have time to wipe /var/db/pkg and remove all ports? Try portmanager before you wipe your ports and db. Have you cd /usr/ports mkae fetchindex? Stop in /usr/ports. No such file or directory - /tmp/INDEX8274.0 portsdb: index chmod error chmod error? Are you root or what? # So what is this? Also, can anybody tell me if these commands are all I need to do a full cleanup and upgrade of my ports? This is my /root/make.PORTS: # cvsup -g -L 2 /etc/cvsupfile pkgdb -F portupgrade -ra portsdb -uU portupgrade -ra pkgdb -F Don't do pkgdb unattended, you may need to answer questions. You could skip all this index stuff if you use portmanager. But you need /var/db/pkg in good condition to use pormanager, I think? portmanager doesn't use /var/db/pkg/pkgdb.db, I think that is what you are refering to. It should be able to fix this person's problem like you suggested though. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU error (I also need some tips)
Hey! I haven't tried fetchindex or portmanager. I'll try them now. As for the make.PORTS, I run them inside screen, so incase I need to answer something, it won't continue untill I do. But do you guys have a suggestion to how a more efficient make.PORTS could look like? Now I'll include cd /usr/ports make fetchindex into it but how about the order and amount of instances of each command etc? Thanks. - Original Message - From: Jeff Hinrichs [EMAIL PROTECTED] To: Fafa Diliha Romanova [EMAIL PROTECTED] Subject: Re: portsdb -uU error (I also need some tips) Date: Sun, 13 Mar 2005 12:55:25 -0600 Fafa Diliha Romanova wrote: Hello! There's been a lot of mess in my ports lately. I want to get rid of this: pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded Which pops up every time I install/deinstall a port or package. I have done a 'pkgdb -F' which seemed to work. Upon 'portsdb -uU' I get: # Updating the ports index ... Generating INDEX.tmp - please wait..cannot create /tmp/index.UHO8TTKq/INDEX.tmp.desc.german: No such file or directory *** Error code 2 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the ports-all collection, and have no refuse files.) If that is the case, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, your architecture, your environment, and your /etc/make.conf settings, especially compiler flags and WITH/WITHOUT settings). Note: the latest pre-generated version of INDEX may be fetched automatically with make fetchindex. *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. No such file or directory - /tmp/INDEX8274.0 portsdb: index chmod error # So what is this? Also, can anybody tell me if these commands are all I need to do a full cleanup and upgrade of my ports? This is my /root/make.PORTS: # cvsup -g -L 2 /etc/cvsupfile pkgdb -F portupgrade -ra portsdb -uU portupgrade -ra pkgdb -F # Thank you all so much! All the best, -- Fafa This may not fix all of your problems, but doing a cd /usr/ports make fetchindex is much faster and less problematic than portsdb -uU -- ___ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU error (I also need some tips)
On Sunday 13 March 2005 11:59 am, Fafa Diliha Romanova wrote: Hey! I haven't tried fetchindex or portmanager. I'll try them now. As for the make.PORTS, I run them inside screen, so incase I need to answer something, it won't continue untill I do. But do you guys have a suggestion to how a more efficient make.PORTS could look like? Now I'll include cd /usr/ports make fetchindex into it but how about the order and amount of instances of each command etc? Thanks. portmanager doesn't need fetchindex, but if you want to make the readme.html's or do things like make search= in /usr/ports then make fetchindex is a good idea. You are going to loose the index every time you cvsup so here is how I would set up a script to automate things as much as possible: cd /usr/ports make update (this assumes you have /etc/make.conf setup for cvsup) make fetchindex portmanager -u - Original Message - From: Jeff Hinrichs [EMAIL PROTECTED] To: Fafa Diliha Romanova [EMAIL PROTECTED] Subject: Re: portsdb -uU error (I also need some tips) Date: Sun, 13 Mar 2005 12:55:25 -0600 Fafa Diliha Romanova wrote: Hello! There's been a lot of mess in my ports lately. I want to get rid of this: pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded pkg_delete: package bsdpan-libwww-perl-5.800 has no origin recorded Which pops up every time I install/deinstall a port or package. I have done a 'pkgdb -F' which seemed to work. Upon 'portsdb -uU' I get: # Updating the ports index ... Generating INDEX.tmp - please wait..cannot create /tmp/index.UHO8TTKq/INDEX.tmp.desc.german: No such file or directory *** Error code 2 1 error * *** Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the ports-all collection, and have no refuse files.) If that is the case, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, your architecture, your environment, and your /etc/make.conf settings, especially compiler flags and WITH/WITHOUT settings). Note: the latest pre-generated version of INDEX may be fetched automatically with make fetchindex. * *** *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. No such file or directory - /tmp/INDEX8274.0 portsdb: index chmod error # So what is this? Also, can anybody tell me if these commands are all I need to do a full cleanup and upgrade of my ports? This is my /root/make.PORTS: # cvsup -g -L 2 /etc/cvsupfile pkgdb -F portupgrade -ra portsdb -uU portupgrade -ra pkgdb -F # Thank you all so much! All the best, -- Fafa This may not fix all of your problems, but doing a cd /usr/ports make fetchindex is much faster and less problematic than portsdb -uU ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu - Stop.
On Mon, Feb 28, 2005 at 01:35:28PM -0500, Lowell Gilbert wrote: # portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..apsfilter-7.2.6 : /usr/ports/print/acroread5 non-existent -- dependency list incomplete === print/apsfilter failed *** Error code 1 1 error The current version of the apsfilter port should be looking at /usr/ports/print/acroread instead of .../acroread5. ... The makefile you have in /usr/ports/print/apsfilter is at least a week or two out of date, so double-check against the problems in this message. Hi, Thanks much for the hint! I waited for a day, cvsup-ed the ports-tree again, then re-build apsfilter - and the problem is gone :-). Best regards, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -Uu - Stop.
Hi, today I cvsup-ed one of my 5.3 systems by using the same procedure as many times before: cvsup -g -L 2 ./ports-supfile pkgdb -F portsdb -Uu The first two steps (cvsup, pkgdb) went OK without error, but during portsdb -Uu I get an error as follows: # portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..apsfilter-7.2.6 : /usr/ports/print/acroread5 non-existent -- dependency list incomplete === print/apsfilter failed *** Error code 1 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the ports-all collection, and have no refuse files.) If that is the case, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, your architecture, your environment, and your /etc/make.conf settings, especially compiler flags and WITH/WITHOUT settings). Note: the latest pre-generated version of INDEX may be fetched automatically with make fetchindex. *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error What can I do against this error? Thanks much in advance for any clue, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu - Stop.
Ewald Jenisch wrote: Hi, today I cvsup-ed one of my 5.3 systems by using the same procedure as many times before: cvsup -g -L 2 ./ports-supfile pkgdb -F portsdb -Uu The first two steps (cvsup, pkgdb) went OK without error, but during portsdb -Uu I get an error as follows: # portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..apsfilter-7.2.6 : /usr/ports/print/acroread5 non-existent -- dependency list incomplete === print/apsfilter failed *** Error code 1 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the ports-all collection, and have no refuse files.) If that is the case, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, your architecture, your environment, and your /etc/make.conf settings, especially compiler flags and WITH/WITHOUT settings). Note: the latest pre-generated version of INDEX may be fetched automatically with make fetchindex. *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error What can I do against this error? Thanks much in advance for any clue, -ewald You may do: cd /usr/ports make fetchindex to fetch index-file. You not must generate this file yourself and wasting your time and CPU-resourses. -- Alexey Karguine ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu - Stop.
On Mon, Feb 28, 2005 at 07:54:05PM +0300, Alexey Karguine wrote: You may do: cd /usr/ports make fetchindex to fetch index-file. You not must generate this file yourself and wasting your time and CPU-resourses. Hi Alexey, Thanks for the hint - it did the trick. However I still wonder why portsdb -Uu suddenly dies with this error after running for months without any problem... -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu - Stop.
Ewald Jenisch [EMAIL PROTECTED] writes: today I cvsup-ed one of my 5.3 systems by using the same procedure as many times before: cvsup -g -L 2 ./ports-supfile pkgdb -F portsdb -Uu The first two steps (cvsup, pkgdb) went OK without error, but during portsdb -Uu I get an error as follows: # portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..apsfilter-7.2.6 : /usr/ports/print/acroread5 non-existent -- dependency list incomplete === print/apsfilter failed *** Error code 1 1 error The current version of the apsfilter port should be looking at /usr/ports/print/acroread instead of .../acroread5. Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the ports-all collection, and have no refuse files.) If that is the case, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, your architecture, your environment, and your /etc/make.conf settings, especially compiler flags and WITH/WITHOUT settings). The makefile you have in /usr/ports/print/apsfilter is at least a week or two out of date, so double-check against the problems in this message. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU fails
Vonleigh Simmons [EMAIL PROTECTED] writes: Have you got a refuse file? Don't. No. Are you doing the cvsup on the ports-all collection, with a cvs tag of '.'? If not, do. Yes and yes. Have you got enough bandwidth to comfortably remove the whole multimedia directory and cvsup again? The problem you're hitting it that you are *not* getting the whole ports collection. You need to figure out why that is; I am not seeing the same symptoms. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU fails
Figure out why /usr/ports/multimedia/libtheora is non-existent, and fix it. As another part of the message warned you, building an INDEX requires a *full* ports collection, so if you are missing some it will fail. I don't have that folder. I'm not sure why I don't, I haven't changed everything, and have it so that it does cvsup daily, one day it just started failing. What can I do to force it to resync properly? Vonleigh Simmons http://illusionart.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU fails
Vonleigh Simmons [EMAIL PROTECTED] writes: Figure out why /usr/ports/multimedia/libtheora is non-existent, and fix it. As another part of the message warned you, building an INDEX requires a *full* ports collection, so if you are missing some it will fail. I don't have that folder. I'm not sure why I don't, I haven't changed everything, and have it so that it does cvsup daily, one day it just started failing. What can I do to force it to resync properly? Have you got a refuse file? Don't. Are you doing the cvsup on the ports-all collection, with a cvs tag of '.'? If not, do. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU fails
Have you got a refuse file? Don't. No. Are you doing the cvsup on the ports-all collection, with a cvs tag of '.'? If not, do. Yes and yes. Vonleigh Simmons http://illusionart.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -uU fails
While running portsdb -uU I get the following error: Updating the ports index ... Generating INDEX.tmp - please wait..icecast2-2.2.0,1: /usr/ports/multimedia/libtheora non-existent -- dependency list incomplete === audio/icecast2 failed *** Error code 1 1 error This is on FreeBSD 5.3 stable after a recent cvsup. Any help fixing this matter is appreciated. Vonleigh Simmons http://illusionart.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU fails
On Friday 04 February 2005 02:04 am, Vonleigh Simmons wrote: While running portsdb -uU I get the following error: Updating the ports index ... Generating INDEX.tmp - please wait..icecast2-2.2.0,1: /usr/ports/multimedia/libtheora non-existent -- dependency list incomplete === audio/icecast2 failed *** Error code 1 1 error This is on FreeBSD 5.3 stable after a recent cvsup. Any help fixing this matter is appreciated. When this happens, the easy answer is to user make fetchindex and then only do a portsdb -u. I am not seeing any messages about INDEX dying in ports@ and that usually means you are refusing something that another port needs. The only choice then is to use fetchindex. Kent Vonleigh Simmons http://illusionart.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU fails
When this happens, the easy answer is to user make fetchindex and then only do a portsdb -u. That worked fine. I'm confused though, am I not supposed to use the -U flag at all? Because after running those two I tried -Uu again and I got the same error. If I'm not supposed to use -U, has it been replaced by something or is it not necessary? Vonleigh Simmons http://illusionart.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU fails
Vonleigh Simmons [EMAIL PROTECTED] writes: While running portsdb -uU I get the following error: Updating the ports index ... Generating INDEX.tmp - please wait..icecast2-2.2.0,1: /usr/ports/multimedia/libtheora non-existent -- dependency list incomplete === audio/icecast2 failed *** Error code 1 1 error This is on FreeBSD 5.3 stable after a recent cvsup. Any help fixing this matter is appreciated. Figure out why /usr/ports/multimedia/libtheora is non-existent, and fix it. As another part of the message warned you, building an INDEX requires a *full* ports collection, so if you are missing some it will fail. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU fails
On Fri, 4 Feb 2005 03:34:43 -0800 Vonleigh Simmons [EMAIL PROTECTED] wrote: When this happens, the easy answer is to user make fetchindex and then only do a portsdb -u. That worked fine. I'm confused though, am I not supposed to use the -U flag at all? Because after running those two I tried -Uu again and I got the same error. If I'm not supposed to use -U, has it been replaced by something or is it not necessary? *** Well i have ran into the same situation.I just added f for force and afterwards i updated everything that could be upgraded. So i most of the times use portsdb -Ufu and portupgrade -afrR or -arR serie/(meta-)app.This seems to work for me.Strange though because portsdb -Uu seemed to work for me until lately. Peter Harmsen Vonleigh Simmons http://illusionart.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
'portsdb -Uu' vs 'make fetchindex' vs 'make index'
I am not sure if I quite understand this entire ports updating scenario correctly. I I run the command: 'cvsup ports-supfile', I then need to run either 'portsdb -Uu' or 'make index'. I also have the option of running 'make fetchindex' in place of either of those two proceeding commands. Is that correct? I would assume, that I should run the 'make fetchindex' command immediately after running the 'cvsup' command. Does anyone have any suggestions as to a better way to accomplish this feat? Thanks! Gerard Seibert [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 'portsdb -Uu' vs 'make fetchindex' vs 'make index'
On Tue, Dec 21, 2004 at 05:34:06AM -0500, Gerard Seibert wrote: I am not sure if I quite understand this entire ports updating scenario correctly. I I run the command: 'cvsup ports-supfile', I then need to run either 'portsdb -Uu' or 'make index'. I also have the option of running 'make fetchindex' in place of either of those two proceeding commands. Is that correct? Yes, basically. Running portsdb -U will make an index. If you run portsdb -Uu you don't have to make index as an additional step. Additionally, portsdb -u will automatically be run when it needs to be run, but you can run it manually as well. One of the fastest ways to update your tree and index is to cvsup, then cd /usr/ports make fetchindex. You can run portsdb -u if you want, but you don't have to. It might help catch dependency problems if you do, however. I would assume, that I should run the 'make fetchindex' command immediately after running the 'cvsup' command. Yes, you can do that, as I mentioned above. Does anyone have any suggestions as to a better way to accomplish this feat? Test out different ways of updating, to find out which ones you want to use - for instance you can also use sysutils/p5-FreeBSD-Portindex - and then write scripts to accomplish it, and/or set it up as a cron job. - jt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with 'portsdb -uU' and ld-elf.so...
I guess that's the fix. Everything seemed to go just fine. Everything has been rebuilt (except OO, and a sun-jdk... but I think I installed them as packages anyway). So I guess I'll be doing something like the following to upgrade my ports from now on: # cvsup -g -L 2 /root/ports-supfile # /usr/ports/make fetchindex # portsdb -u # pkgdb -F # portupgrade -a If this looks incorrect please let me know. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks for everyone's assistance. Looks great, I install cvsup woith the gui so I don't need to add the -g -L 2. Also Jonathan Franks, you aren't the actor from star trek are you? I just had to ask! ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Trouble with 'portsdb -uU' and ld-elf.so...
Hello,
I'm having trouble with 'portsdb -uU'
It worked exactly twice on my machine. I was using the following
commands to upgrade all my ports:
# cvsup -g -L 2 /root/ports-supfile
# portsdb -uU
# pkgdb -F
# portupupgrade -a
worked fine first two times. Now.. my cvsup works fine. but when I
'portsdb -uU', it runs for a while and then I get something like:
K_1_2 Segmentation fault (core dumped) JAVA_PORT_LINUX_IBM_JDK_1_3 |
/usr/bin/awk '{ print $1 }' returned non-zero status
=== java/javamail failed
*** Error code 1
2 errors
/libexec/ld-elf.so.1: rm: Shared object has no run-time symbol table
*** Error code 1
Stop in /usr/ports.
*** Error code 1
Stop in /usr/ports.
failed to generate INDEX!
fangorn#
// Note that if I do a ls immediately afterwards i get
fangorn# ls
/libexec/ld-elf.so.1: ls: Shared object has no run-time symbol table.
Now mind you I may have broken my ports tree at some point. I'm
relatively new to FreeBSD... and before I began using portupgrade... I
was manually upgrading a handful of ports (make install.. deinstall...
reinstall type stuff... downloading port folder manually).. and I think
a placed a few in 'new' directories in my ports tree. So I do not know
if that would 'break' my ports tree or not. But thought it was worth
mentioning.
Other things worth mentioning:
- I have a very slight customized kernel config file. Added support for
ath, removed some processor support (486/586), added splash screen.
- I have NEVER cvsupped my kernel src... only the ports tree.
- Other than changing the kernel config file and buildkernel/install
kernel... I have done nothing such as buildworld.
- No other problems on my machine.
# unanme -a
FreeBSD fangorn.nxdomain.org 5.3-RELEASE FreeBSD 5.3-RELEASE #1: Thu Nov
11 09:39:38 CST 2004 [EMAIL PROTECTED]:
/usr/obj/usr/src/sys/INSPIRON5100 i386
Have I broken something? Am I going about upgrading ports the wrong
way? If I have broken my ports tree is it possible to recreate it
correctly? Maybe delete it and reinstall off CD then cvsup it?
Thanks
--
Regards,
Eric
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with 'portsdb -uU' and ld-elf.so...
Eric Schuele wrote:
Hello,
I'm having trouble with 'portsdb -uU'
It worked exactly twice on my machine. I was using the following
commands to upgrade all my ports:
# cvsup -g -L 2 /root/ports-supfile
# portsdb -uU
# pkgdb -F
# portupupgrade -a
worked fine first two times. Now.. my cvsup works fine. but when I
'portsdb -uU', it runs for a while and then I get something like:
K_1_2 Segmentation fault (core dumped) JAVA_PORT_LINUX_IBM_JDK_1_3 |
/usr/bin/awk '{ print $1 }' returned non-zero status
=== java/javamail failed
*** Error code 1
2 errors
/libexec/ld-elf.so.1: rm: Shared object has no run-time symbol table
*** Error code 1
Stop in /usr/ports.
*** Error code 1
Stop in /usr/ports.
failed to generate INDEX!
fangorn#
// Note that if I do a ls immediately afterwards i get
fangorn# ls
/libexec/ld-elf.so.1: ls: Shared object has no run-time symbol table.
Now mind you I may have broken my ports tree at some point. I'm
relatively new to FreeBSD... and before I began using portupgrade... I
was manually upgrading a handful of ports (make install.. deinstall...
reinstall type stuff... downloading port folder manually).. and I
think a placed a few in 'new' directories in my ports tree. So I do
not know if that would 'break' my ports tree or not. But thought it
was worth mentioning.
Other things worth mentioning:
- I have a very slight customized kernel config file. Added support
for ath, removed some processor support (486/586), added splash screen.
- I have NEVER cvsupped my kernel src... only the ports tree.
- Other than changing the kernel config file and buildkernel/install
kernel... I have done nothing such as buildworld.
- No other problems on my machine.
# unanme -a
FreeBSD fangorn.nxdomain.org 5.3-RELEASE FreeBSD 5.3-RELEASE #1: Thu
Nov 11 09:39:38 CST 2004 [EMAIL PROTECTED]:
/usr/obj/usr/src/sys/INSPIRON5100 i386
Have I broken something? Am I going about upgrading ports the wrong
way? If I have broken my ports tree is it possible to recreate it
correctly? Maybe delete it and reinstall off CD then cvsup it?
Thanks
Something bad is going on, but you should read stuff like
/usr/ports/UPDATING. What is likely our problem is the change that was
made to the way cvsup handles the index file now. It doesn't update it
automatically anymore. You have to do something like make fetchindex.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with 'portsdb -uU' and ld-elf.so...
On Thursday 16 December 2004 08:07 am, Eric Schuele wrote:
Hello,
I'm having trouble with 'portsdb -uU'
It worked exactly twice on my machine. I was using the following
commands to upgrade all my ports:
# cvsup -g -L 2 /root/ports-supfile
# portsdb -uU
# pkgdb -F
# portupupgrade -a
worked fine first two times. Now.. my cvsup works fine. but when I
'portsdb -uU', it runs for a while and then I get something like:
K_1_2 Segmentation fault (core dumped) JAVA_PORT_LINUX_IBM_JDK_1_3 |
/usr/bin/awk '{ print $1 }' returned non-zero status
=== java/javamail failed
*** Error code 1
2 errors
/libexec/ld-elf.so.1: rm: Shared object has no run-time symbol table
*** Error code 1
Stop in /usr/ports.
*** Error code 1
Stop in /usr/ports.
failed to generate INDEX!
fangorn#
// Note that if I do a ls immediately afterwards i get
fangorn# ls
/libexec/ld-elf.so.1: ls: Shared object has no run-time symbol table.
Now mind you I may have broken my ports tree at some point. I'm
relatively new to FreeBSD... and before I began using portupgrade...
I was manually upgrading a handful of ports (make install..
deinstall... reinstall type stuff... downloading port folder
manually).. and I think a placed a few in 'new' directories in my
ports tree. So I do not know if that would 'break' my ports tree or
not. But thought it was worth mentioning.
Other things worth mentioning:
- I have a very slight customized kernel config file. Added support
for ath, removed some processor support (486/586), added splash
screen. - I have NEVER cvsupped my kernel src... only the ports tree.
- Other than changing the kernel config file and buildkernel/install
kernel... I have done nothing such as buildworld.
- No other problems on my machine.
# unanme -a
FreeBSD fangorn.nxdomain.org 5.3-RELEASE FreeBSD 5.3-RELEASE #1: Thu
Nov 11 09:39:38 CST 2004 [EMAIL PROTECTED]:
/usr/obj/usr/src/sys/INSPIRON5100 i386
Have I broken something? Am I going about upgrading ports the wrong
way? If I have broken my ports tree is it possible to recreate
it correctly? Maybe delete it and reinstall off CD then cvsup it?
Before you go deleting your entire port tree try the following:
1. install /usr/ports/sysutils/portmanager
2. To see the status of installed ports:
portmanager -s
3. To upgrade installed ports
portmanager -u
Note: portmanager does not depend on INDEX, INDEX-5 etc...
-Mike
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with 'portsdb -uU' and ld-elf.so...
On Thu, Dec 16, 2004 at 10:07:19AM -0600, Eric Schuele wrote:
Hello,
I'm having trouble with 'portsdb -uU'
It worked exactly twice on my machine. I was using the following
commands to upgrade all my ports:
# cvsup -g -L 2 /root/ports-supfile
# portsdb -uU
# pkgdb -F
# portupupgrade -a
worked fine first two times. Now.. my cvsup works fine. but when I
'portsdb -uU', it runs for a while and then I get something like:
K_1_2 Segmentation fault (core dumped) JAVA_PORT_LINUX_IBM_JDK_1_3 |
/usr/bin/awk '{ print $1 }' returned non-zero status
=== java/javamail failed
*** Error code 1
2 errors
/libexec/ld-elf.so.1: rm: Shared object has no run-time symbol table
Here is my guess, and I emphasize that it is a guess:
http://fireflynetworks.net/pipermail/rtg/2004-December/001375.html
is a page I found by using Google to search for:
Shared object has no run-time symbol table
Now mind you I may have broken my ports tree at some point.
This appears to be the case:
I'm
relatively new to FreeBSD... and before I began using portupgrade... I
was manually upgrading a handful of ports (make install.. deinstall...
reinstall type stuff... downloading port folder manually)..
I suggest reinstalling the ports you deinstalled, if you haven't
already done so...
and I think
a placed a few in 'new' directories in my ports tree. So I do not know
if that would 'break' my ports tree or not. But thought it was worth
mentioning.
I can't quite parse this because it appears to me that you've left out
a word or two.
Other things worth mentioning:
- I have a very slight customized kernel config file. Added support for
ath, removed some processor support (486/586), added splash screen.
I don't think this is relevant.
- I have NEVER cvsupped my kernel src... only the ports tree.
And here it is: go and update your source, including the ports tree,
after you have reinstalled the ports you deinstalled. Make sure that
the world is correctly installed; then go and try the portupgrade
bits, one port at a time.
I have done nothing such as buildworld.
Go and do buildworld, then portupgrade.
Have I broken something? Am I going about upgrading ports the wrong
way?
Yes, it appears that you have broken something.
If I have broken my ports tree is it possible to recreate it
correctly? Maybe delete it and reinstall off CD then cvsup it?
No, you don't need to do a complete reinstall, IMO; you do need to
update your source, perhaps even desperately.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with 'portsdb -uU' and ld-elf.so...
Joe Altman wrote:
On Thu, Dec 16, 2004 at 10:07:19AM -0600, Eric Schuele wrote:
Hello,
I'm having trouble with 'portsdb -uU'
It worked exactly twice on my machine. I was using the following
commands to upgrade all my ports:
# cvsup -g -L 2 /root/ports-supfile
# portsdb -uU
# pkgdb -F
# portupupgrade -a
worked fine first two times. Now.. my cvsup works fine. but when I
'portsdb -uU', it runs for a while and then I get something like:
K_1_2 Segmentation fault (core dumped) JAVA_PORT_LINUX_IBM_JDK_1_3 |
/usr/bin/awk '{ print $1 }' returned non-zero status
=== java/javamail failed
*** Error code 1
2 errors
/libexec/ld-elf.so.1: rm: Shared object has no run-time symbol table
Here is my guess, and I emphasize that it is a guess:
http://fireflynetworks.net/pipermail/rtg/2004-December/001375.html
is a page I found by using Google to search for:
Shared object has no run-time symbol table
Now mind you I may have broken my ports tree at some point.
This appears to be the case:
I'm
relatively new to FreeBSD... and before I began using portupgrade... I
was manually upgrading a handful of ports (make install.. deinstall...
reinstall type stuff... downloading port folder manually)..
I suggest reinstalling the ports you deinstalled, if you haven't
already done so...
and I think
a placed a few in 'new' directories in my ports tree. So I do not know
if that would 'break' my ports tree or not. But thought it was worth
mentioning.
I can't quite parse this because it appears to me that you've left out
a word or two.
Other things worth mentioning:
- I have a very slight customized kernel config file. Added support for
ath, removed some processor support (486/586), added splash screen.
I don't think this is relevant.
- I have NEVER cvsupped my kernel src... only the ports tree.
And here it is: go and update your source, including the ports tree,
after you have reinstalled the ports you deinstalled. Make sure that
the world is correctly installed; then go and try the portupgrade
bits, one port at a time.
I have done nothing such as buildworld.
Go and do buildworld, then portupgrade.
Have I broken something? Am I going about upgrading ports the wrong
way?
Yes, it appears that you have broken something.
If I have broken my ports tree is it possible to recreate it
correctly? Maybe delete it and reinstall off CD then cvsup it?
No, you don't need to do a complete reinstall, IMO; you do need to
update your source, perhaps even desperately.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
From what I've heard, portsdb -Uu is not preferred in 5.3, rather one
should do make fetchindex in /usr/ports then run portsdb -u afterwards.
I've only HEARD that this is correct, but it worked for me. so make
of it what you will
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with 'portsdb -uU' and ld-elf.so...
On Thu, Dec 16, 2004 at 09:30:43PM -0500, Jonathan Franks wrote:
Joe Altman wrote:
On Thu, Dec 16, 2004 at 10:07:19AM -0600, Eric Schuele wrote:
K_1_2 Segmentation fault (core dumped) JAVA_PORT_LINUX_IBM_JDK_1_3 |
/usr/bin/awk '{ print $1 }' returned non-zero status
=== java/javamail failed
*** Error code 1
2 errors
/libexec/ld-elf.so.1: rm: Shared object has no run-time symbol table
From what I've heard, portsdb -Uu is not preferred in 5.3, rather one
should do make fetchindex in /usr/ports then run portsdb -u afterwards.
I've only HEARD that this is correct, but it worked for me. so make
of it what you will
I've used it on my 5.3 box; it seems fine. My experience doesn't mean
you are wrong.
Anyway, to my eye, it's not portsdb that is failing; in the first
example, it's awk:
K_1_2 Segmentation fault (core dumped) JAVA_PORT_LINUX_IBM_JDK_1_3
/usr/bin/awk '{ print $1 }' returned non-zero status
It just happens to be failing within portsdb, at that point.
His second example had to do with running ls; that also failed, with
the same message:
Shared object has no run-time symbol table
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with 'portsdb -uU' and ld-elf.so...
Joe Altman wrote: On Thu, Dec 16, 2004 at 10:07:19AM -0600, Eric Schuele wrote: snip and I think a placed a few in 'new' directories in my ports tree. So I do not know if that would 'break' my ports tree or not. But thought it was worth mentioning. I can't quite parse this because it appears to me that you've left out a word or two. snip Sorry. I meant that I had placed a few ports in 'new' directories. By that I meant: - I went to the FreeBSD Ports site - found a port I wanted to upgrade (firefox or fluxbox for example) - 'make deinstall'ed the one that was installed. - Copied the directory on the site to a folder within the ports tree with a similar but different name. - and then did a 'make install clean' Then I was enlightened to the fact that this was... not the way to do things. So on to portupgrades I went. First one or two went without a hitch. -- Regards, Eric ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with 'portsdb -uU' and ld-elf.so...
Jonathan Franks wrote: Joe Altman wrote: On Thu, Dec 16, 2004 at 10:07:19AM -0600, Eric Schuele wrote: snip lots If I have broken my ports tree is it possible to recreate it correctly? Maybe delete it and reinstall off CD then cvsup it? No, you don't need to do a complete reinstall, IMO; you do need to update your source, perhaps even desperately. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] From what I've heard, portsdb -Uu is not preferred in 5.3, rather one should do make fetchindex in /usr/ports then run portsdb -u afterwards. I've only HEARD that this is correct, but it worked for me. so make of it what you will ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ahh yes.. I've run across a msg or two mentioning this... but that was before I was trying to solve this problem so I was not paying close attention at the time. I just tried it. I did a fresh cvsup, then the 'make fetchindex' (which pulled something out of the ether)... and then a 'portsdb -u'. The portsdb finished almost immediately and provided no output!? good? bad? dunno. So I moved on to 'pkgdb -F' which went well. I am currently watching the portupgrade do its thing. It takes a while because I have OpenOffice installed. I'll post back with my results. Thanks for the assistance. -- Regards, Eric ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Trouble with 'portsdb -uU' and ld-elf.so...
Jonathan Franks wrote: Joe Altman wrote: On Thu, Dec 16, 2004 at 10:07:19AM -0600, Eric Schuele wrote: snip No, you don't need to do a complete reinstall, IMO; you do need to update your source, perhaps even desperately. I will do a update of my sources and build world asap. I was simply under the impression that I could safely upgrade only the ports. So that's how I got started down this. And then when things went bad I wanted to fix it before I tried upgrading anything else and possibly compunding things. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] From what I've heard, portsdb -Uu is not preferred in 5.3, rather one should do make fetchindex in /usr/ports then run portsdb -u afterwards. I've only HEARD that this is correct, but it worked for me. so make of it what you will I guess that's the fix. Everything seemed to go just fine. Everything has been rebuilt (except OO, and a sun-jdk... but I think I installed them as packages anyway). So I guess I'll be doing something like the following to upgrade my ports from now on: # cvsup -g -L 2 /root/ports-supfile # /usr/ports/make fetchindex # portsdb -u # pkgdb -F # portupgrade -a If this looks incorrect please let me know. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks for everyone's assistance. -- Regards, Eric ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -Uu Segmentation fault
Hello, This is on a Pentium-II running FreeBSD 4.10R, portupgrade-20040701_3, ruby-1.8.2.p2_1, and ruby18-bdb1-0.2.2. Here is what I did: $ pkgdb -F $ cvsup ports-supfile $ portsdb -Uu And here is the output I get from portsdb: Updating the ports index ... Generating INDEX.tmp - please wait.. Done. done [Updating the portsdb format:bdb1_btree in /usr/ports ... - 11939 port entries found .1000.2000.3000.4000.5000 .6000.7000.8000../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Segmentation fault ruby 1.8.2 (2004-07-29) [i386-freebsd4] Abort trap (core dumped) I did a google search, and found a bunch of people had a similar problem (Bus Error, not Segmentation fault) in early September, but I didn't notice what (portupgrade/ruby/the ports tree) was actually the problem. What really stumps me is that I have 2 other servers that have the same version of FreeBSD, Ruby and Portupgrade installed that work fine. Any help would be much appreciated. Thank You, Tabor Kelly ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu Segmentation fault
Tabor Kelly wrote: This has been discussed DOZENS of times on this list including TODAY. What do you think the archives are for?! Sorry, I will look harder. Like I said, I found a lot of people having the problem (in the archives), I didn't find anyone explaining what causes the problem or how to fix it. Again, Sorry. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -uU cause the server hanging up
kinux [EMAIL PROTECTED] writes: i am tried to cvsup my ports then portsdb -uU found portsdb update take a lot of CPU resource (above 80%), then i just make the server hanging up, does it can limit the resource usage for portsdb update? Maybe nice(1) is what you are looking for? -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -uU cause the server hanging up
hi all, i am tried to cvsup my ports then portsdb -uU found portsdb update take a lot of CPU resource (above 80%), then i just make the server hanging up, does it can limit the resource usage for portsdb update? Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu error
On Mon, Jul 05, 2004 at 08:55:32AM +, Ariane Ron Joordens wrote: Hi everyone, I have just cvsupped successfully and tried to run portsdb -Uu. I received the following error: _ freebsd# portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..fr-mozilla-flp-1.7: /usr/ports/www/mozilla-gtk2 non-existent -- dependency list incomplete === french/mozilla-flp failed *** Error code 1 1 error Looks like you have mozilla-gtk2 installed, but this port was recently removed. www/mozex/Makefile.xpi does some slightly over-clever gymnastics that detect this, which causes the breakage. Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection (INDEX builds are not supported with partial or out-of-date ports collections). If so, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, environment and /etc/make.conf settings). Note that you didn't quite follow these instructions. Kris pgpgjxnOfZ8kA.pgp Description: PGP signature
Re: portsdb -Uu error
well looks like u don't have the whole /usr/ports .. plz re-run cvsup over ports .. to update everything and try to install again - Original Message - From: Ariane Ron Joordens [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 05, 2004 1:55 AM Subject: portsdb -Uu error Hi everyone, I have just cvsupped successfully and tried to run portsdb -Uu. I received the following error: _ freebsd# portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..fr-mozilla-flp-1.7: /usr/ports/www/mozilla-gtk2 non-existent -- dependency list incomplete === french/mozilla-flp failed *** Error code 1 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection (INDEX builds are not supported with partial or out-of-date ports collections). If so, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, environment and /etc/make.conf settings). *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error __ I have FreeBSD 4.10, I cvsup to RELENG_4_10 and refuse nothing. freebsd# uname -a FreeBSD freebsd.home.com 4.10-RELEASE FreeBSD 4.10-RELEASE #0: Fri May 28 21:00:30 GMT 2004 This is my cvs-supfile: _ # $FreeBSD: src/share/examples/cvsup/cvs-supfile,v 1.26.2.11 2003/09/12 19:01:13 ceri Exp $ *default host=cvsup.au.FreeBSD.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default tag=RELENG_4_10 *default release=cvs *default delete use-rel-suffix *default compress src-all ports-all tag=. doc-all tag=. ___ This is my /etc/make.conf file: _ #make.conf file contains options for rebuilding the system and ports from source #Copied from tutorial: Turn FreeBSD into a Multimedia Workstation by Dru Lavigne # CPUTYPE=p3 CFLAGS= -O -pipe CXXFLAGS+= -funroll-loops COPTFLAGS= -O -pipe # #To avoid building various parts of the base system: NO_BIND= true # do not build BIND NO_FORTRAN= true # do not build g77 and related libraries NO_I4B= true # do not build isdn4bsd package NOPROFILE= true # Avoid compiling profiled libraries NOUUCP= true # do not build uucp related programs DOC_LANG= en_US.ISO8859-1 # USA_RESIDENT= YES __ Does anyone know if this is a problem with french/mozilla-flp or a problem with my setup? Do you need more info? Thanks for your help. Ron Please CC me as I am not subscribed to the list on this address ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -Uu error
Hi everyone, I have just cvsupped successfully and tried to run portsdb -Uu. I received the following error: _ freebsd# portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..fr-mozilla-flp-1.7: /usr/ports/www/mozilla-gtk2 non-existent -- dependency list incomplete === french/mozilla-flp failed *** Error code 1 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection (INDEX builds are not supported with partial or out-of-date ports collections). If so, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, environment and /etc/make.conf settings). *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error __ I have FreeBSD 4.10, I cvsup to RELENG_4_10 and refuse nothing. freebsd# uname -a FreeBSD freebsd.home.com 4.10-RELEASE FreeBSD 4.10-RELEASE #0: Fri May 28 21:00:30 GMT 2004 This is my cvs-supfile: _ # $FreeBSD: src/share/examples/cvsup/cvs-supfile,v 1.26.2.11 2003/09/12 19:01:13 ceri Exp $ *default host=cvsup.au.FreeBSD.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default tag=RELENG_4_10 *default release=cvs *default delete use-rel-suffix *default compress src-all ports-all tag=. doc-all tag=. ___ This is my /etc/make.conf file: _ #make.conf file contains options for rebuilding the system and ports from source #Copied from tutorial: Turn FreeBSD into a Multimedia Workstation by Dru Lavigne # CPUTYPE=p3 CFLAGS= -O -pipe CXXFLAGS+= -funroll-loops COPTFLAGS= -O -pipe # #To avoid building various parts of the base system: NO_BIND=true# do not build BIND NO_FORTRAN= true# do not build g77 and related libraries NO_I4B= true# do not build isdn4bsd package NOPROFILE= true# Avoid compiling profiled libraries NOUUCP= true# do not build uucp related programs DOC_LANG= en_US.ISO8859-1 # USA_RESIDENT= YES __ Does anyone know if this is a problem with french/mozilla-flp or a problem with my setup? Do you need more info? Thanks for your help. Ron Please CC me as I am not subscribed to the list on this address ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -Uu error
This looks to be a fairly straightforward error: begin error message fishcat# portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait..drweb_postfix-4.29.12f: /usr/ports/security/drwebd non-existent -- dependency list incomplete === security/drweb-postfix failed *** Error code 1 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection (INDEX builds are not supported with partial or out-of-date ports collections). If so, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, environment and /etc/make.conf settings). Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error end error message bash-2.05b$ pwd /usr/ports/security bash-2.05b$ ls | more [...] dropbear drweb drweb-postfix drweb-qmail drweb-sendmail dsniff [...] As the portsdb -Uu error message states, /usr/ports/security/drwebd is non-existent (at least following a cvsup of the ports tree today, I am not sure if it was there before) and so the portsdb -Uu run fails with the error message shown above. My FreeBSD version is RELENG_4 (FreeBSD-STABLE). What is the fix for this please? Waiting until a new cvsup corrects the error above, or...? -- Anthony Edwards [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu error
On Tuesday 29 June 2004 09:11 am, Anthony Edwards wrote:
This looks to be a fairly straightforward error:
begin error message
fishcat# portsdb -Uu
Updating the ports index ... Generating INDEX.tmp - please
wait..drweb_postfix-4.29.12f: /usr/ports/security/drwebd
non-existent -- dependency list incomplete
=== security/drweb-postfix failed
*** Error code 1
1 error
Before reporting this error, verify that you are running a supported
version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you
have a complete and up-to-date ports collection (INDEX builds are
not supported with partial or out-of-date ports collections). If
so, then report the failure to [EMAIL PROTECTED] together with
relevant details of your ports configuration (including FreeBSD
version, environment and /etc/make.conf settings).
Stop in /usr/ports.
failed to generate INDEX!
portsdb: index generation error
end error message
bash-2.05b$ pwd
/usr/ports/security
bash-2.05b$ ls | more
[...]
dropbear
drweb
drweb-postfix
drweb-qmail
drweb-sendmail
dsniff
[...]
As the portsdb -Uu error message states, /usr/ports/security/drwebd
is non-existent (at least following a cvsup of the ports tree today,
I am not sure if it was there before) and so the portsdb -Uu run
fails with the error message shown above.
My FreeBSD version is RELENG_4 (FreeBSD-STABLE).
What is the fix for this please? Waiting until a new cvsup corrects
the error above, or...?
If you follow ports, I was told you also should also follow cvs-all. It
was fixed about an hour ago. So, it should have made it to your
favorite cvsup-mirror.
A faster fix is to edit the drweb_postfix make file and change the
drwebd entry on the PORTSDIR entry to just drweb.
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 -Uu error
On Tue, Jun 29, 2004 at 09:30:25AM -0700, Kent Stewart wrote: If you follow ports, I was told you also should also follow cvs-all. It was fixed about an hour ago. So, it should have made it to your favorite cvsup-mirror. Indeed yes, now resolved. I have also subscribed to cvs-all in order to track such things in the future. -- Anthony Edwards [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu trouble in www/mod_auth_check
On Wed, 16 Jun 2004 10:46:01 -0500 Guillermo Garc_a-Rojas [EMAIL PROTECTED] wrote: Ooops! Today the problem disapeared itself. I didn't anything else to fix it. Same problem. I was using a refuse file. So I stop using it and the problem disapeared. On Wed, 16 Jun 2004 19:02:55 +0400, Alexey Karguine [EMAIL PROTECTED] wrote: Hello! I have FreeBSD 4.10 machine. Every night this machine sinchronizes the ports-tree using cvsup by the cron and runs 'portsdb -Uu'. One week ago i recieved this letter from the cron daemon: -- cut -- Updating the ports index ... Generating INDEX.tmp - please wait..mod_auth_pwcheck-1.1: /usr/ports//apache13 non-existent -- dependency list incomplete === www/mod_auth_pwcheck failed *** Error code 1 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection (INDEX builds are not supported with partial or out-of-date ports collections). If so, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, environment and /etc/make.conf settings). *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error -- cut -- I tried to 'portupgrade -f portupgrade' and to manually cvsuping ports-tree. That steps didn't give any results. What can I do to fix this problem. Thanks! P.S. Sorry for my english, I'm not real englishman. =) --bm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] --bm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
portsdb -Uu trouble in www/mod_auth_check
Hello! I have FreeBSD 4.10 machine. Every night this machine sinchronizes the ports-tree using cvsup by the cron and runs 'portsdb -Uu'. One week ago i recieved this letter from the cron daemon: -- cut -- Updating the ports index ... Generating INDEX.tmp - please wait..mod_auth_pwcheck-1.1: /usr/ports//apache13 non-existent -- dependency list incomplete === www/mod_auth_pwcheck failed *** Error code 1 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection (INDEX builds are not supported with partial or out-of-date ports collections). If so, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, environment and /etc/make.conf settings). *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error -- cut -- I tried to 'portupgrade -f portupgrade' and to manually cvsuping ports-tree. That steps didn't give any results. What can I do to fix this problem. Thanks! P.S. Sorry for my english, I'm not real englishman. =) --bm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
