From owner-freebsd-questions@FreeBSD.ORG Tue Jul 20 17:58:36 2004 Return-Path: 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 459E516A4CE for ; Tue, 20 Jul 2004 17:58:36 +0000 (GMT) Received: from imf17aec.mail.bellsouth.net (imf17aec.mail.bellsouth.net [205.152.59.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CF3543D49 for ; Tue, 20 Jul 2004 17:58:31 +0000 (GMT) (envelope-from freebsd@usmstudent.com) Received: from [192.168.1.100] ([68.209.222.4]) by imf17aec.mail.bellsouth.netESMTP <20040720175830.EOJK1760.imf17aec.mail.bellsouth.net@[192.168.1.100]> for ; Tue, 20 Jul 2004 13:58:30 -0400 From: freebsd@usmstudent.com To: freebsd-questions@freebsd.org Date: Tue, 20 Jul 2004 12:58:24 -0500 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200407201258.24756.freebsd@usmstudent.com> Subject: @conflicts in /var/db/pkg/*/+CONTENTS X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: alias2@crotchett.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2004 17:58:36 -0000 Whenever I run pkg_info, I am receiving error messages that indicate conflicts with my packages. For example, when I run pkg_info, I get: pkg_info: read_plist: bad command '@conflicts libX11-*' grep'ing for libX11-* in /var/db/pkg shows the offending package to be XFree86. Or, more specifically: XFree86-libraries-4.3.0_7 I was getting another conflict with fontconfig, but reinstalling it with "portinstall -rP" helped. I tried reinstalling XFree86-libraries. But, this time it didn't help. Running pkgdb -F exits normally without error. But, it doesn't help resolve the conflicts. Would including "-R" as an option to portinstall help? I have seen similar problems on Google. Yet, I don't see any solutions. There are only 2 things that I can think of that would be worth mentioning that could possibly be related to the problem. First is that since I am running 4.6-RELEASE, my system may be too old to work properly with current ports. The second is that I recently moved my installation to another HD. That's been a couple of months ago and I haven't noticed any other problems with that transition. One last bit of information that might be helpful to mention is that I use portupgrade. As a possible fix, I have considered upgrading to 4.10-RELEASE. But, I'm fearful that I will end up trashing my box completely. Any suggestions? TIA, Darren