From owner-freebsd-questions@FreeBSD.ORG Sun Jul 2 21:23:09 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04D9D16A403 for ; Sun, 2 Jul 2006 21:23:09 +0000 (UTC) (envelope-from stapleton.41@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BCF3444CD for ; Sun, 2 Jul 2006 21:23:07 +0000 (GMT) (envelope-from stapleton.41@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so1448217uge for ; Sun, 02 Jul 2006 14:23:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jApgxRJjXNS0OOYkdo5gBUjXp9kejINovIzCch2KMOXOtA/Aya9bpnWZQKTafhjOJiHeMWyrhFEDJLCFv7yXh2SAUUgNf6a/0c1M5HGyBswFbrZjmeWl0ffDu+Cvi2E6mWThRAU3vrzE6F6vlbFkbUw6jO30k+7tqxu/vDTQhYo= Received: by 10.66.220.17 with SMTP id s17mr5114843ugg; Sun, 02 Jul 2006 14:23:06 -0700 (PDT) Received: by 10.67.86.1 with HTTP; Sun, 2 Jul 2006 14:23:06 -0700 (PDT) Message-ID: <80f4f2b20607021423h3de5f063raf7ea0f2843c3399@mail.gmail.com> Date: Sun, 2 Jul 2006 17:23:06 -0400 From: "Jim Stapleton" To: freebsd-questions@freebsd.org In-Reply-To: <20060702183358.GD12262@tigger.digitaltorque.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060702183123.GC12262@tigger.digitaltorque.ca> <20060702183358.GD12262@tigger.digitaltorque.ca> Subject: Re: cannot upgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 21:23:09 -0000 I would guess that means the file was corrupted somehow, though I don't know how. At any rate, I don't know how to fix that, and not loose the stored information. On 7/2/06, Michael P. Soulier wrote: > On 02/07/06 Michael P. Soulier said: > > > Cannot update the pkgdb!]: Cannot update the pkgdb!] > > /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:444:in `__system': Command > > failed [exit code 1]: /usr/local/sbin/pkgdb -aFQ (CommandFailedError) > > from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:467:in `__sudo' > > from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:473:in `xsystem!' > > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:960:in `autofix!' > > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:956:in `autofix' > > from /usr/local/sbin/portupgrade:475:in `main' > > from /usr/local/sbin/portupgrade:714:in `main' > > from /usr/local/lib/ruby/1.8/optparse.rb:815:in `initialize' > > from /usr/local/sbin/portupgrade:209:in `main' > > from /usr/local/sbin/portupgrade:1951 > > [root@espresso ~]# pkgdb -F > ---> Checking the package registry database > [Updating the pkgdb in /var/db/pkg ... > /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid argument; > rebuild needed] [Rebuilding the pkgdb in /var/db/pkg ... > /var/db/pkg/pkgdb.db: unexpected file type or format -- Invalid argument: > Cannot update the pkgdb!]: Cannot update the pkgdb!] > > This doesn't look good. > > Mike > > -- > Michael P. Soulier > "Any intelligent fool can make things bigger and more complex... It > takes a touch of genius - and a lot of courage to move in the opposite > direction." --Albert Einstein > > >