From owner-freebsd-ports@FreeBSD.ORG Sat Jul 1 09:28:20 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6505316A40F for ; Sat, 1 Jul 2006 09:28:20 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from mail.ciam.ru (ns.ciam.ru [213.247.195.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0279C43D45 for ; Sat, 1 Jul 2006 09:28:19 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from [87.240.16.199] (helo=[192.168.0.3]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1Fwbly-000Fsr-88; Sat, 01 Jul 2006 13:28:18 +0400 Message-ID: <44A6403D.8010204@FreeBSD.org> Date: Sat, 01 Jul 2006 13:28:29 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 1.5 (X11/20060115) MIME-Version: 1.0 To: Matthias Andree References: <44A568A9.3030206@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: HEADS-UP: portupgrade and pkgdb.db failures X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Jul 2006 09:28:20 -0000 Matthias Andree wrote: > Sergey Matveychuk writes: > >> Please note: >> If you got problem with pkgdb.db (and INDEX.db) file afrer upgrade >> portupgrade, remove it (them) and restart portupgrade. >> (It was described in man page.) > > For those wondering, these are /var/db/pkg/pkgdb.db and > /usr/ports/INDEX.db, INDEX-5.db or INDEX-6.db. Yes, I meant INDEX*.db > >> It's possible you'll get *.db brackage. It'll happen if you selected >> WITH_BDB4 option and thought you have *.db in bdb2+ format. But it was >> wrong, you had bases in dbd format. Now it's fixed and you'll have > > Is that bdb 1.85 format you're referring to? No. Only if you have defined WITH_BDB4. > >> honest bdb format, but you should remove databases files first. > > Would it be possible, reasonable and not too much effort to use the > db_dump185* and db_load* utilities of the corresponding database library > to automatically convert the database to the newer format in > postinstall? (Can the proper Berkeley DB library version be queried > from the ruby database code at all?) > I don't know bdb files format. I think sleepycat provide some convertors, but it's not a point. Real problem is old versions of portupgrade fall back to dbd driver (not Berkley DB) if no bdb1 driver was found. So bdb2+ never used even if you have it installed. So if you get *.db file error it means you have dbd files instead of bdb2+. -- Dixi. Sem.