From owner-freebsd-questions@FreeBSD.ORG Wed Aug 2 13:30:02 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 37EB316A4DE for ; Wed, 2 Aug 2006 13:30:02 +0000 (UTC) (envelope-from Kevin@RawFedDogs.net) Received: from ms-smtp-01.texas.rr.com (ms-smtp-01.texas.rr.com [24.93.47.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3383143D6E for ; Wed, 2 Aug 2006 13:29:58 +0000 (GMT) (envelope-from Kevin@RawFedDogs.net) Received: from localhost.localdomain (cpe-24-243-189-26.hot.res.rr.com [24.243.189.26]) by ms-smtp-01.texas.rr.com (8.13.6/8.13.6) with ESMTP id k72DTvNF000923 for ; Wed, 2 Aug 2006 08:29:57 -0500 (CDT) Received: from Mutt by mutt-smtp-wrapper.pl 1.2 (www.zdo.com/articles/mutt-smtp-wrapper.shtml) Date: Wed, 2 Aug 2006 08:30:17 -0500 From: Kevin Monceaux To: FreeBSD-Questions@FreeBSD.org Message-ID: <20060802133017.GA3940@RawFedDogs.net> References: <20060802122218.70875.qmail@web27613.mail.ukl.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060802122218.70875.qmail@web27613.mail.ukl.yahoo.com> User-Agent: Mutt/1.5.11 X-Virus-Scanned: Symantec AntiVirus Scan Engine Cc: Subject: Re: Weird result of portupgrade -aRr concerning pkgconfig or is it pkg-config? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kevin@RawFedDogs.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Aug 2006 13:30:02 -0000 Bobby, On Wed, Aug 02, 2006 at 02:22:18PM +0200, Bobby Knight wrote: > Hello Newly installed 6.1. I recently said hello to a newly installed FreeBSD 6.1 myself. > Barely touched ports so one would expect it to work, That sounds like a reasonable expectation for FreeBSD. I'm new to FreeBSD myself. For the most part I've found it quite stable. I've been a Linux user for years(since the 1.x kernel days) and after only a few days of tinkering with FreeBSD on a test box I'm just about ready to switch my main box over to FreeBSD. > yet it fails brutally for me as a new user when I do portupgrade -arR > just to upgrade a few packages. I experienced a similar failure to the one you describe, although I didn't find it all that brutal. After a few tries I managed to get past it. > I have no clue why and what to do so I am hoping someone here knows. I don't really have a clue as to why myself but I'll tell you what worked for me. There may be a better solution to this and if so hopefully someone with more knowledge than I will point it out. To improve your chances of getting the answers you need you might want to consider paying attention to the guidelines posted occasionally, especially the part about including line breaks. Such a post can be found at: http://Lists.FreeBSD.org/pipermail/freebsd-questions/2006-July/126199.html Reformatting your post so I could reply to it took a bit of time. Since I had a similar problem I took the time to reformat your message and reply to it with the hope that it will encourage someone who might not otherwise have repiled to provide more information and a better solution to the problem. > Can't see what I have done wrong. My guess is you haven't done anything wrong. I had the same problem. > That is always cvsup ports and do a portsdb -Fu; portaudit -Fa before > upgrade as well as read UPDATING. I use portsnap myself and just installed portupgrade and portaudit yesterday. I'm still learning all the proper steps necessary to keep my system up to date. > Checking if devel/pkg-config already installed ===> pkg-config-0.20_2 > is already installed > You may wish to ``make deinstall'' and install this port again by ``make > reinstall'' to upgrade it properly. I tried a 'make deinstall' then 'make reinstall' as the error message suggested. It didn't help. Then, I tried a 'make deinstall' followed by a 'portupgrade -aRr' which appeared to get around the problem. Portupgrade installed the version of pkg-config it really wanted and upgraded everything successfully. Kevin http://www.RawFedDogs.net http://www.WacoAgilityGroup.org Bruceville, TX Si hoc legere scis nimium eruditionis habes.