From owner-freebsd-ports@FreeBSD.ORG Thu Feb 1 18:47:46 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0DAB316A403 for ; Thu, 1 Feb 2007 18:47:46 +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 80CFD13C491 for ; Thu, 1 Feb 2007 18:47:45 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from [87.240.16.199] (helo=[192.168.0.4]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1HCgxu-000G0k-3P; Thu, 01 Feb 2007 21:47:22 +0300 Message-ID: <45C235A3.7060901@FreeBSD.org> Date: Thu, 01 Feb 2007 21:46:59 +0300 From: Sergey Matveychuk User-Agent: Thunderbird 1.5.0.9 (X11/20070124) MIME-Version: 1.0 To: Laganakos Vassilis References: <45C12797.7090707@hs-heilbronn.de> <200702010145.55226.molnarcs@gmail.com> <20070201135225.GA29750@pythagoras.physics.upatras.gr> In-Reply-To: <20070201135225.GA29750@pythagoras.physics.upatras.gr> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: Csaba Molnar , freebsd-ports@freebsd.org Subject: Re: portupgrade-2.2.2_1,2 corrupts portsdb 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: Thu, 01 Feb 2007 18:47:46 -0000 Have you updated portupgrade to the last one (2.2.2_3,2)? Do it please. Laganakos Vassilis wrote: > Hi, > > Done that too (pkgdb -fu) , but didn't work for me... :( > I use FreeBSD6-stable > > Vassilis > > On Thu, Feb 01, 2007 at 01:45:55AM +0100, Csaba Molnar wrote: >> 2007. February 1. 00.34 d?tummal Joachim Bethke ezt ?rta: >>> Hallo, >>> >>> I get the same error on two machines too. Have someone a practical idea >>> how to fix it. >>> >>> Joachim >> >> I deleted /var/db/pkg/pkgdb.db, then rebuilt it with pkgdb -u I think, and >> that seems to have worked. >> >> While I was updating ports before this error showed up, the options screen for >> portupgrade showed up - and option WITH_BDB4 was unchecked. I changed that >> (so portupgrade was now built with bdb4) - and the problems began right after >> this update. -- Dixi. Sem.