Re: portsdb and cvsup
BTW, Dru was talking about ''pkgdb -fu''. Different command, and lower-case "f". And that was for when the *packages* database gets messed up. At which point you'll probably have thoughts along that line in your head ... :) I just had a look at the pkgdb manpage. My bad. It is upper-case "f". Lower-case "f" is for forcing things. Regards, Rakhesh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb and cvsup
Adam J Richardson wrote: Rakhesh Sasidharan wrote: During my first few days with FreeBSD, however, I used to run ''portsdb -Fu''. My understanding is that that would fetch the INDEX-6 and update INDEX-6.db (since I am on FreeBSD 6.x) but I don't see why I should do this coz the INDEX files are updated when I update the ports tree anyways! (If I have understood this incorrectly, someone please correct me). Hi Rakhesh, What you say about the -F and -u flags sounds right. It's my understanding that "portsdb -Fu" is only required when the ports database gets a little bit messed up and the system prompts you. It's an easy one to remember, because as Dru said in that article, you may be thinking something similar at the time. ;) Heh, that really was a good mnemonic from Dru to remember these switches. BTW, Dru was talking about ''pkgdb -fu''. Different command, and lower-case "f". And that was for when the *packages* database gets messed up. At which point you'll probably have thoughts along that line in your head ... :) After some thought, I think the "-F" switch to ''portsdb'' is useful if you want to just search for what's new etc by downloading the latest copy of the INDEX file and using that instead of downloading the ports tree changes. That way, if you are into the portupgrade tools, you can do a ''portsdb -Fu'' to get the latest INDEX files and update INDEX.db. You can search for ports using ''pkg_glob''. And you can find what's newer compared to the installed software using ''portversion''. No need to update your ports tree to do all this! Regards, Rakhesh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb and cvsup
Rakhesh Sasidharan wrote: During my first few days with FreeBSD, however, I used to run ''portsdb -Fu''. My understanding is that that would fetch the INDEX-6 and update INDEX-6.db (since I am on FreeBSD 6.x) but I don't see why I should do this coz the INDEX files are updated when I update the ports tree anyways! (If I have understood this incorrectly, someone please correct me). Hi Rakhesh, What you say about the -F and -u flags sounds right. It's my understanding that "portsdb -Fu" is only required when the ports database gets a little bit messed up and the system prompts you. It's an easy one to remember, because as Dru said in that article, you may be thinking something similar at the time. ;) Regards, Adam J Richardson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb and cvsup
Thanks for your story. The only reason we used -U was that we were not sure what they meant got special macros. The man page for portsdb status that you only use -U if you have special macros in /etc/make.conf. All we have in there is version information so I think that does not apply to use. Thanks again, Arend Rakhesh Sasidharan wrote: On Sun, 5 Aug 2007, Arend P. van der Veen wrote: The approach that I had been using was: /usr/local/bin/cvsup -L 0 /usr/sup/supfile /usr/local/sbin/portsdb -Uu This had worked great until the emacs22 update. Now portsdb crashes due to the emacs entry in /etc/make.conf. However, I see very little chatter on the lists about this. I have started to wonder if the bulk of the community may be updating their ports differently. Upon some limited research I found that I could use: /usr/local/bin/cvsup -L 0 /usr/sup/supfile /usr/local/sbin/portsdb -Fu This work fine for me. I can then use tools such as pkg_version, pkg_delete, portinstall and portupgrade without any problems. My open ended question is what does the rest of the community do to update their ports collection? I don't run portsdb at all. :) What I figured from the portsdb manpages is that if you don't run it manually then it gets run upon using one of the portupgrade tools. I don't mind the 30s or so delay that causes and so I don't run portsdb manually. During my first few days with FreeBSD, however, I used to run ''portsdb -Fu''. My understanding is that that would fetch the INDEX-6 and update INDEX-6.db (since I am on FreeBSD 6.x) but I don't see why I should do this coz the INDEX files are updated when I update the ports tree anyways! (If I have understood this incorrectly, someone please correct me). I tried ''portsdb -Uu'' just once. To see what it does. Took a long time and so I never tried it again. From the manpage I understand that it creates/ updates the INDEX files by running the ''make index'' command, but the reasoning behind that didn't make sense to me ... So that's my story. Regards, Rakhesh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb and cvsup
On Sun, 5 Aug 2007, Arend P. van der Veen wrote: The approach that I had been using was: /usr/local/bin/cvsup -L 0 /usr/sup/supfile /usr/local/sbin/portsdb -Uu This had worked great until the emacs22 update. Now portsdb crashes due to the emacs entry in /etc/make.conf. However, I see very little chatter on the lists about this. I have started to wonder if the bulk of the community may be updating their ports differently. Upon some limited research I found that I could use: /usr/local/bin/cvsup -L 0 /usr/sup/supfile /usr/local/sbin/portsdb -Fu This work fine for me. I can then use tools such as pkg_version, pkg_delete, portinstall and portupgrade without any problems. My open ended question is what does the rest of the community do to update their ports collection? I don't run portsdb at all. :) What I figured from the portsdb manpages is that if you don't run it manually then it gets run upon using one of the portupgrade tools. I don't mind the 30s or so delay that causes and so I don't run portsdb manually. During my first few days with FreeBSD, however, I used to run ''portsdb -Fu''. My understanding is that that would fetch the INDEX-6 and update INDEX-6.db (since I am on FreeBSD 6.x) but I don't see why I should do this coz the INDEX files are updated when I update the ports tree anyways! (If I have understood this incorrectly, someone please correct me). I tried ''portsdb -Uu'' just once. To see what it does. Took a long time and so I never tried it again. From the manpage I understand that it creates/ updates the INDEX files by running the ''make index'' command, but the reasoning behind that didn't make sense to me ... So that's my story. Regards, Rakhesh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portsdb and cvsup
Hi, I have recently been having trouble with running portsdb after cvsup. I am running 6.2-RELEASE-p7. The approach that I had been using was: /usr/local/bin/cvsup -L 0 /usr/sup/supfile /usr/local/sbin/portsdb -Uu This had worked great until the emacs22 update. Now portsdb crashes due to the emacs entry in /etc/make.conf. However, I see very little chatter on the lists about this. I have started to wonder if the bulk of the community may be updating their ports differently. Upon some limited research I found that I could use: /usr/local/bin/cvsup -L 0 /usr/sup/supfile /usr/local/sbin/portsdb -Fu This work fine for me. I can then use tools such as pkg_version, pkg_delete, portinstall and portupgrade without any problems. My open ended question is what does the rest of the community do to update their ports collection? Thanks, Arend ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: error: portsdb and cvsup with refuse file
Peter wrote: With 5.4 I received an error using portsdb after updating my ports tree with a refuse file. How does one deal with this? # portsdb -U Updating the ports index ... Generating INDEX.tmp - please wait..p5-Unicode-MapUTF8-1.09: "/usr/ports/japanese/p5-Jcode" non-existent -- dependency list incomplete ===> converters/p5-Unicode-MapUTF8 failed *** Error code 1 1 error Either ditch your refuse file or use 'make fetchindex' from /usr/ports. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
error: portsdb and cvsup with refuse file
With 5.4 I received an error using portsdb after updating my ports tree with a refuse file. How does one deal with this? # portsdb -U Updating the ports index ... Generating INDEX.tmp - please wait..p5-Unicode-MapUTF8-1.09: "/usr/ports/japanese/p5-Jcode" non-existent -- dependency list incomplete ===> converters/p5-Unicode-MapUTF8 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 __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
