portsdb -u & ruby core dumps

[Karl Heller]

   I just noticed that portsdb -Uu core dumps on me.  There seems to be  
something wrong with the Index file that is build by -U.  If I remove  
the INDEX* files and re-download them via cvsup, portsdb -u works.   
However, if I run -U to rebuild the index then -u to make the DB I get:

(heller at rns:[11:19am]-147-) /usr3/FreeBSD/ports## portsdb -U
Updating the ports index ... Generating INDEX.tmp - please  
wait..Warning: Duplicate INDEX entry: freeciv-gtk2-1.14.1
Warning: Duplicate INDEX entry: fvwm-imlib-2.4.18
  Done.
done
(heller at rns:[11:39am]-148-) /usr3/FreeBSD/ports## dir INDEX*
-rw-r--r--  1 root  wheel   5955064 Sep  3 11:39 INDEX
-rw-r--r--  1 root  wheel   4947853 Mar 15 18:20 INDEX-5
-rw-r--r--  1 root  wheel  10724352 Sep  3 11:16 INDEX.db
(heller at rns:[11:41am]-149-) /usr3/FreeBSD/ports## portsdb -u
[Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 11726  
port entries found  
.........1000.........2000.........3000.........4000.........5000....... 
..6000.........7000.........8000..../usr/local/lib/ruby/site_ruby/1.8/ 
portsdb.rb:587: [BUG] Bus Error
ruby 1.8.2 (2004-07-29) [i386-freebsd4]

Abort (core dumped)

I actually did a make install of ruby 1.8.2 thinking there was a  
problem with it.

this is 4.10-Stable from July.  I do pull the entire ports tree.

I just checked my cron logs from yesterday and the build was fine...
[Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 11718  
port entries
  found  
.........1000.........2000.........3000.........4000.........5000....... 
.
.6000.........7000.........8000.........9000.........10000.........11000 
.......
..... done]

So, is this related to the ports freeze for 5.3?

Karl



"The number of people that can reason well, is much smaller than those  
that can reason badly.  If reasoning were like hauling rocks then  
several reasoners might be better than one.  But reasoning isn't like  
hauling rocks." - Galileo