Errors after upgrading portupgrade

[Jack Raats]

Top gives:

last pid: 28570;  load averages:  0.00,  0.00,  0.00 
up 0+02:48:39  10:16:15
94 processes:  2 running, 92 sleeping
CPU states:  0.4% user,  0.0% nice,  0.7% system,  0.0% interrupt, 98.9% 
idle
Mem: 23M Active, 40M Inact, 76M Wired, 60K Cache, 60M Buf, 353M Free
Swap: 2048M Total, 88M Used, 1960M Free, 4% Inuse

I think memory is not the problem. The errors started after the portupgrade 
to version 2.0.0,1

Jack

----- Original Message ----- 
From: "Scott Smith" <scott at lackluster.net>
To: "Jack Raats" <jack at jarasoft.net>
Cc: <freebsd-questions at freebsd.org>
Sent: Monday, January 02, 2006 9:36 AM
Subject: Re: Errors after upgrading portupgrade


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> How's the machine's memory usage?
>
> Scott
>
> Jack Raats wrote:
>> Hi,
>>
>> Running the new portupgrade 2.0.0,1 gives the following errors:
>>
>> orac# portupgrade -Na
>> [Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 13945 port 
>> entries found 
>> .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000......... 
>> ..... done]
>> ** Package origin of 'bison' has been changed: 'devel/bison' -> 
>> 'devel/bison2'
>> ** No need to upgrade 'bison-1.75_2,1' (>= bison-2.1_1). (specify -f to 
>> force)
>> /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?
>>
>> Jack
>> _______________________________________________
>> freebsd-questions at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to 
>> "freebsd-questions-unsubscribe at freebsd.org"
>
> - --
> scott at lackluster.net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
>
> iD8DBQFDuOYnKBeC2yZ3EEsRAkItAJ9y7sj6op+L8fFH8VBMNaA5Bu0FeQCfSzPE
> fz/v1M46YNomG72SmNGTSxE=
> =1N4B
> -----END PGP SIGNATURE-----
>