missing ports; portsdb problem
I'm missing a few ports collections such as Japanese and Russian. Now when I try to run portsdb -Uu after CVSUPing the ports collection I get an error of a missing japanese port. The strange thing is that my cvsupfile is set to fetch ports-all. Why is it not pulling in the missing ports? I don't have a refuse file set. __ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: missing ports; portsdb problem
Jim, I had the same problem. I think it was a tk port, if I recall correctly. The only way I could fix it was to rm -drv /usr/ports rm my refuse file, then cvsup again. After that, portsdb -Uu ran properly (though it took forever). Bill Sawyer Information Systems Six Flags St. Louis (636) 938-5300 x. 231 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: missing ports; portsdb problem
Bill Sawyer wrote: Jim, I had the same problem. I think it was a tk port, if I recall correctly. The only way I could fix it was to rm -drv /usr/ports rm my refuse file, then cvsup again. After that, portsdb -Uu ran properly (though it took forever). I had the same problem recently since I was blocking all non-english ports in my refuse file. Just as was mentioned above, I removed it. But, I didn't bother to remove my recently cvsup'ed ports collection (sans other lang). I just edited my refuse file to allow alternate lang ports back in and re-cvsup'ed. Afterward, my portsdb -uU also succeeded. So, basically what I'm saying is that I'd try the above recommendation but without rm-ing /usr/ports. This should save some download time. Plus, if for some reason it doesn't work, you can always clean out your ports dir later. -- Kendall Gifford WEB: http://kendall.jedis.com/ EMAIL: REPLY TO NEWSGROUP ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
missing ports; portsdb problem
On Mon, 21 Jun 2004 13:14:44 -0600 Kendall Gifford [EMAIL PROTECTED] wrote: Bill Sawyer wrote: Jim, I had the same problem. I think it was a tk port, if I recall correctly. The only way I could fix it was to rm -drv /usr/ports rm my refuse file, then cvsup again. After that, portsdb -Uu ran properly (though it took forever). I had the same problem recently since I was blocking all non-english ports in my refuse file. Just as was mentioned above, I removed it. Jim, You mentioned that you didn't have a refuse file. You might want to double check that /usr/local/etc/cvsup/sup/refuse or [other_default_base_specified_by_your_ports_supfile]/sup/refuse does indeed not exist. find / -name refuse -print#also a handy way, providing your user has the perms to read the dirs where refuse might be lurking. But, I didn't bother to remove my recently cvsup'ed ports collection (sans other lang). I just edited my refuse file to allow alternate lang ports back in and re-cvsup'ed. Afterward, my portsdb -uU also succeeded. Yeah. Something changed a couple of weeks ago. This solution worked for me too. Good luck, epi So, basically what I'm saying is that I'd try the above recommendation but without rm-ing /usr/ports. This should save some download time. Plus, if for some reason it doesn't work, you can always clean out your ports dir later. -- Kendall Gifford WEB: http://kendall.jedis.com/ EMAIL: REPLY TO NEWSGROUP ___ [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]
Re: missing ports; portsdb problem
Jim, You mentioned that you didn't have a refuse file. You might want to double check that /usr/local/etc/cvsup/sup/refuse or [other_default_base_specified_by_your_ports_supfile]/sup/refuse does indeed not exist. find / -name refuse -print#also a handy way, providing your user has the perms to read the dirs where refuse might be lurking. But, I didn't bother to remove my recently cvsup'ed ports collection (sans other lang). I just edited my refuse file to allow alternate lang ports back in and re-cvsup'ed. Afterward, my portsdb -uU also succeeded. Yeah. Something changed a couple of weeks ago. This solution worked for me too. Good luck, epi Hm. Well, I did have both /usr/src/refuse /usr/sup/refuse and they both had other languages in them. I don't remember adding them but that's not saying much ;) I'll try removing those files and do another run at updating the ports. Thanks for the help. Jim __ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
