portindex causes ruby to dump core

Radek Kozlowski radek at raadradd.com
Mon Jul 5 15:27:41 PDT 2004


On both of my two 4.10 boxes (one -RELEASE and one -STABLE) 
/usr/ports/INDEX generated by portindex causes trouble to 
portupgrade/portversion. I had no trouble with portindex on my -CURRENT 
laptop, so I'm not sure whether it depends on what ports are installed 
or the system version (or both). Below is the output:

root at biggie:/usr/sup# portindex
[snip]
Saving status data ...  ok!
Expanding dependences ...  done
Building /usr/ports/INDEX
Duplicate entry freeciv-gtk-1.14.1 in both /usr/ports/games/freeciv and 
/usr/ports/games/freeciv-gtk
11189 total entries
1 duplicated entries discarded
0 ports with unresolved depends kept
root at biggie:/usr/sup# portversion -vl "<"
[Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 11189 port 
entries found 
.........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000....../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: 
[BUG] Segmentation fault
ruby 1.8.1 (2004-05-02) [i386-freebsd4]

Abort (core dumped)
root at biggie:/usr/sup#

If I create INDEX using portsdb -U the problem goes away.

-Radek



More information about the freebsd-ports mailing list