From owner-freebsd-questions Wed Feb 6 18:25:19 2002 Delivered-To: freebsd-questions@freebsd.org Received: from sage-american.com (sage-american.com [216.122.141.44]) by hub.freebsd.org (Postfix) with ESMTP id 1E28C37B41F for ; Wed, 6 Feb 2002 18:25:11 -0800 (PST) Received: from SAGEONE (adsl-64-219-30-23.dsl.crchtx.swbell.net [64.219.30.23]) by sage-american.com (8.9.3/8.9.3) with SMTP id UAA23664; Wed, 6 Feb 2002 20:25:08 -0600 (CST) Message-Id: <3.0.5.32.20020206202502.01959060@mail.sage-american.com> X-Sender: jacks@mail.sage-american.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 06 Feb 2002 20:25:02 -0600 To: Joey Garcia , questions@FreeBSD.ORG From: jacks@sage-american.com Subject: Re: Strange pkg_info error message - what's wrong with it? In-Reply-To: <20020206173553.O519-100000@we-24-126-232-105.we.mediaone.n et> References: <20020206172743.I519-100000@we-24-126-232-105.we.mediaone.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Joey: See my post of a few minutes ago.... I never had any such interruption, but had the identical problem on 4 separate boxes. In my earlier post about the problem with samba, I show my solution. Delete the port and recvsup. At 05:38 PM 2.6.2002 -0800, Joey Garcia wrote: > > >Woops, forgot to mention that after the cvsup I had to rebuild autoconf. >See, the problem is that I guess it didn't completely register because it >got powered off and therefore /var/db/pkg/autoconf213 was empty and that's >why pkg_info couldn't read the +CONTENTS file. Okay, problem solved. > >On Wed, 6 Feb 2002, Joey Garcia wrote: > >> >> Okay, so I cvsup'd my ports tree and the messages went away. Interesting. >> Anyways, I think what happened was that someone in my department cut the >> power to the machine when I was building some ports and it probably >> screwed something up. I didn't realize this until I actually went to the >> machine and turned on the monitor and saw that it had just finished >> booting. I was like wtf?!? Anyways, there's no more messages. But, if it >> happens to someone then at least this will be archived to help those out >> in the future. >> >> On Wed, 6 Feb 2002, Joey Garcia wrote: >> >> > >> > Okay, so I noticed that pkg_info is giving me a weird error message. Here >> > is some output and an example of usage and the message that I get. >> > >> > [3:59pm] bear@ircla (~) # pkg_info -Ia | grep ethereal >> > pkg_info: unable to open +CONTENTS file >> > ethereal-0.9.1 An X11/GTK network analyzer/capture tool >> > >> > The second line after the actual command invocation gives a message >> > concerning the +CONTENTS file. I assumed that was the +CONTENTS file >> > located for each package in /var/db/pkg. I'm not sure why it's giving me >> > that error. >> > >> > This machine has been upgraded from 4.3-RELEASE to 4.5-RELEASE just the >> > other day. I've also taken the liberty of going into >> > /usr/src/usr.sbin/pkg_install and issuing a make install to try to >> > reinstall the pkg_* utilities. >> > >> > Not sure what other information to give you, but if you need more just ask >> > and I'll be happy to respond. >> > >> > Joseph Garcia >> > >> > >> > To Unsubscribe: send mail to majordomo@FreeBSD.org >> > with "unsubscribe freebsd-questions" in the body of the message >> > >> >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message >> > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > > Best regards, Jack L. Stone, Server Admin =================================================== Sage-American http://www.sage-american.com jacks@sage-american.com "My center is giving way, my right is in retreat; ....situation excellent! ....I shall attack!" =================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message