Date: Wed, 4 Jan 2006 13:24:42 -0300 From: Fernan Aguero <fernan@iib.unsam.edu.ar> To: FreeBSD Questions <freebsd-questions@freebsd.org> Cc: eoghan <freebsd@redry.net>, Mark Ovens <marko@freebsd.org>, Colin Percival <cperciva@freebsd.org>, Kent Stewart <kstewart@owt.com> Subject: Re: pkgdb format Message-ID: <43B3F22D.5070601@freebsd.org> In-Reply-To: <43B3EEF9.3010004@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
+-----[ | | I had exactly the same problem during portupgrading after a 5.4->6.0 | base system upgrade until I did a `portupgrade -fR portupgrade`, at | which point it stopped (and has been fine ever since). I have no idea | what the problem is or why this would fix it, but you might like to | try this and see if it helps. | | Colin Percival | +-----] Just to add to the thread, though a little bit late. I had also the same problem, during a 'portupgrade -af' after upgrading to 6.0. So I stopped the process, removed the pkgdb.db file, and started it again. The pkgdb.db file got rebuild the first time, and then everything worked right until portupgrade reinstalled databases/ruby-bdb1. From this point on, the rebuilding of pkgdb.db started, alternating between bdm_hash and dbd1_btree, as described before in this thread. Anyway, I just wanted to add that I've been unable to find documentation on the format of the pkgdb.db file ... 'man -k pkgdb' turns up pkgdb(1), but there is nothing there regarding the alternative formats (hash/btree) or how to set them explicitly. Fernan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43B3F22D.5070601>