Weird output from portupgrade at the end of upgrading ruby

Booker Apelin eulogio.apelin at lava.net
Fri Feb 4 13:03:10 PST 2005


I just recently did a portupgrade of Ruby and got some weird output at the
end of the upgrade, shown below. I had ruby-1.8.2.p2_1 installed and
upgraded to ruby-1.8.2_1. I'm running 4.9-RELEASE-p11 with portupgrade
version portupgrade-20040701_3. (I still need to upgrade portupgrade, it's
lower in the portmanager -s list).

So that being said, the new version of ruby seems to be installed but this
output at the end is very strange. Should I check on anything? Everything
seems ok.

===>  Cleaning for ruby-1.8.2_1
--->  Cleaning out obsolete shared libraries
ruby18 in free(): warning: page is already free
[Updating the pkgdb <format:bdb1_btree> in /var/db/pkg ... - 76 packages
found (-0 +1) .ruby18 in free(): warning: chunk is already free
ruby18 in free(): warning: chunk is already free
ruby18 in free(): warning: page is already free
ruby18 in free(): warning: chunk is already free
ruby18 in free(): warning: page is already free
ruby18 in free(): warning: page is already free
ruby18 in free(): warning: chunk is already free
ruby18 in free(): warning: chunk is already free
ruby18 in free(): warning: page is already free
ruby18 in free(): warning: page is already free
ruby18 in free(): warning: chunk is already free
ruby18 in free(): warning: page is already free
ruby18 in free(): warning: chunk is already free
ruby18 in free(): warning: chunk is already free
ruby18 in free(): warning: page is already free
ruby18 in free(): warning: page is already free
ruby18 in free(): warning: chunk is already free
...over a hundred lines of this repeat until I get back to a unix prompt.

Booker



More information about the freebsd-ports mailing list