Problem with portupgrade

[Zimmerman, Eric]

-----Original Message-----
From: owner-freebsd-stable at freebsd.org
[mailto:owner-freebsd-stable at freebsd.org] On Behalf Of Jim C. Nasby
Sent: Monday, May 23, 2005 13:50
To: stable at freebsd.org
Subject: Problem with portupgrade

After updating my ports tree I'm getting this:

decibel at flake.2[13:40]/usr/ports/sysutils/portupgrade:157>sudo
portupgrade -a
[Updating the pkgdb <format:bdb1_btree> in /var/db/pkg ... - 354
packages found (-3 +2)
(...)/usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:466: [BUG] Segmentation
fault
ruby 1.8.2 (2004-12-25) [i386-freebsd4]

I've tried manually reinstalling both ruby and portupgrade to no avail.


I hope I am not hijacking your thread but...

I recommend trying portmanager instead of portupgrade. It is MUCH
smarter, has less dependencies, and knows how to take care of things
when you upgrade a package like perl (it will reinstall all your perl
related ports automatically, etc against the new build).  Portmanager +
portsnap is great.  No need for databases or INDEX making which takes a
while, etc. Portsnap should replace cvsup in the handbook IMO. It rocks.

Here is how I update ports and check for outdated ports (in ports.sh
script):

portsnap fetch
echo "Port snapshot fetched, updating..."
portsnap update
echo "done. Outdated ports:"
# take care of cache miss on new ports
portmanager -s > /dev/null
portmanager -s | grep OLD


if there are any outdated ports, a portmanager -u will update them all,
taking care of any and all dependencies, etc. it does a bunch more stuff
too.

is anyone aware of any downsides to portmanager? Anyone had any issues?

Hope this helps someone out.