Errors after upgrading to new portupgrade

William Denton wtd at pobox.com
Mon Jan 2 10:49:52 PST 2006


On 2 January 2006, Jack Raats wrote:

> /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `<<': failed to allocate memory (NoMemoryError)
>        from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `trace'
>        from /usr/local/sbin/portupgrade:723:in `do_upgrade'
>        from /usr/local/sbin/portupgrade:696:in `main'
>        from /usr/local/sbin/portupgrade:693:in `each'
>        from /usr/local/sbin/portupgrade:693:in `main'
>        from /usr/local/sbin/portupgrade:208:in `initialize'
>        from /usr/local/sbin/portupgrade:208:in `new'
>        from /usr/local/sbin/portupgrade:208:in `main'
>        from /usr/local/sbin/portupgrade:1893
>
> Anyone know how to cure this error?

I had this too, on 6.0-STABLE (to which I upgraded from 5 on Saturday 
without any trouble).  I recompiled all my ruby ports (which took a long 
time because because it kept saying the pkgdb was in the wrong format and 
would rebuild it every time I added or removed something, I guess because 
of the ruby-bdb1 and ruby-bdb4 ports going and coming), then reinstalled 
portupgrade, and that did it.

My /var/db/ports/portupgrade/options now looks like:

   # This file is auto-generated by 'make config'.
   # No user-servicable parts inside!
   # Options for portupgrade-2.0.0_1,1
   _OPTIONS_READ=portupgrade-2.0.0_1,1
   WITH_BDB4=true

This is just me stumbling around without a clue, but it worked.

Bill
-- 
William Denton : Toronto, Canada : www.miskatonic.org : www.frbr.org


More information about the freebsd-stable mailing list