Date: Mon, 19 Jun 2006 14:29:03 +0400 From: Sergey Matveychuk <sem@FreeBSD.org> To: Jiawei Ye <leafy7382@gmail.com> Cc: freebsd ports <freebsd-ports@freebsd.org> Subject: Re: latest portupgrade problem Message-ID: <44967C6F.3010902@FreeBSD.org> In-Reply-To: <c21e92e20606190319h3d05268awe5eac28d80baa950@mail.gmail.com> References: <c21e92e20606182055r32571f5av64d978616e812380@mail.gmail.com> <44966D63.5090804@FreeBSD.org> <c21e92e20606190239t6a89fb91h776b4a542b121766@mail.gmail.com> <44967583.2050108@FreeBSD.org> <c21e92e20606190300p11bfa752td3f5fde0867ddbbb@mail.gmail.com> <44967645.50507@FreeBSD.org> <c21e92e20606190319h3d05268awe5eac28d80baa950@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jiawei Ye wrote: > On 6/19/06, Sergey Matveychuk <sem@freebsd.org> wrote: >> What driver was in the line: >> [Rebuilding the pkgdb <format:dbm_hash> in /var/db/pkg...] >> ^^^^^^^^ here >> >> -- >> Dixi. >> Sem. > It has been dbm_hash for quite a while already. If the db was built > with a 1.85 driver, changing the driver will result in rebuilding the > db. But since I have not changed the driver for more than a month, it > should not happen at all. It should be bdb_btree if you built portupgrade WITH_BDB4 and bdb1_btree otherwise. It should fall to dbm driver if they both failed. So looks like bdb driver never works. BTW. I'll make a new port portupgrade-devel and back out portupgrade port back to 2.1.1 (most stable now and fixes all critical bugs) version. But people should help me to test the new port. -- Dixi. Sem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44967C6F.3010902>