Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 18 Mar 2003 09:56:40 -0600
From:      Mike Meyer <mwm-dated-1048435001.8a3948@mired.org>
To:        Brian McCann <bjm1287@ritvax.isc.rit.edu>
Cc:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Stuck with pkg_info
Message-ID:  <15991.16824.813784.495793@guru.mired.org>
In-Reply-To: <000601c2ed05$92be0020$2f811581@garfield>
References:  <000601c2ed05$92be0020$2f811581@garfield>

next in thread | previous in thread | raw e-mail | index | archive | help
In <000601c2ed05$92be0020$2f811581@garfield>, Brian McCann <bjm1287@ritvax.isc.rit.edu> typed:
> It's been a bad week.  Here's today's problem.  I just tried running
> pkg_info after updating my ports collection and I get the error
> "pkg_info: read_plist: bad command '@ckmment
> MD5:e612f324240eea2f88d666ee1325ea7c' ".  I tried removing the pkgdb.db
> file in /var/db/pkg and rebuilding it using pkgdb -u, but that didn't
> fix it.  Anyone have any other suggestions?

pkgdb.db is created and maintated by the portupgrade tools. pkg_info
isn't part of those, and doesn't use pkgdb.db.

Your problem is that one or more packages has a typo in the +CONTENTS,
saying @ckmment instead of @comment. You can find the this by doing:

# cd /var/db/pkg
# grep -l ckmment */+CONTENTS

That will list the broken file. You can then fix it with ed, vi or
your favorite editor.

If lots of files have that problem, then you have a serious problem,
because one or more of the tools you are using to install ports is
probably corrupt. The fix to that is probably to upgrade your system.

	<mike
-- 
Mike Meyer <mwm@mired.org>		http://www.mired.org/consulting.html
Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15991.16824.813784.495793>