Janine C.Buorditez wrote:
When I had problems, the pkgdb -F would die and the port with the problem was in the list were it died. Portupgrade, for example, used to use pkg_tarup and it would cause problems when you tried to portupgrade itself. I think you are seeing is something like that. You have an installed port that is not in the current INDEX lists. I thought at some point that "pkgdb -fu" was supposed to fix that.How do I find out which port that is?
Some of this was easier to fix by pkg_delete portupgrade and its dependancies and installing from scratch. I think the cutoff was something like 0805. If you had a version before that, you reinstalled portupgrade from scratch. That was quite awhile ago and someone just woke me up by calling me on the telephone after 3 hours of sleep.
Kent
Thanks. --janine On Fri, 22 Nov 2002 05:53:05 -0800 Kent Stewart <[EMAIL PROTECTED]> wrote:Janine C.Buorditez wrote:Hi. This message comes no matter what I do with portupgrade: [Updating the pkgdb <format:bdb1_btree> in /var/db/pkg ... - 230 packages found (-7 +1) (...)/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:375: [BUG] Segmentation fault ruby 1.6.7 (2002-05-23) [i386-freebsd4] Abort (core dumped) Please help?
You probably have a port in your port list that has been removed and will have to manually remove it.
Kent
--
Kent Stewart
Richland, WA
http://users.owt.com/kstewart/index.html
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message .
-- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
