From owner-freebsd-stable@FreeBSD.ORG Fri May 18 07:52:51 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4AE6416A403 for ; Fri, 18 May 2007 07:52:51 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 02DCB13C458 for ; Fri, 18 May 2007 07:52:50 +0000 (UTC) (envelope-from stefan.lambrev@sun-fish.com) Received: from blah.sun-fish.com (localhost [127.0.0.1]) by blah.sun-fish.com (Postfix) with ESMTP id D15581B10ED2; Fri, 18 May 2007 09:52:49 +0200 (CEST) Received: from hater.cmotd.com (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id CE3A61B10EBB; Fri, 18 May 2007 09:52:49 +0200 (CEST) Message-ID: <464D5B51.5050801@sun-fish.com> Date: Fri, 18 May 2007 10:52:49 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.0 (X11/20070425) MIME-Version: 1.0 To: KAYVEN RIESE References: <464B114C.5080703@net4.in> <44irarz7fs.fsf@be-well.ilk.org> <200705171446.33965.lists@jnielsen.net> In-Reply-To: Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP on BLAH Cc: freebsd-stable@freebsd.org Subject: Re: xfce4 broke after pkgdb -Ff X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2007 07:52:51 -0000 KAYVEN RIESE wrote: > > > On Thu, 17 May 2007, John Nielsen wrote: > >> On Thursday 17 May 2007 02:37:15 pm KAYVEN RIESE wrote: >>> On Thu, 17 May 2007, Lowell Gilbert wrote: >>>> Please don't top-post. >>>> >>>> KAYVEN RIESE writes: >>>>> so the "-r" option will be the significant difference for the >>>>> portupgrade comamnd, just verifying >>>> >>>> Yes. Otherwise, you may end up with some of the ports that depend on >>>> pango being unable to use the new version. >>>> >>>> Make sure you look through the UPDATING file to see if there are any >>>> other issues you need to take special action for at the same time. >>> >>> this guy seems to disagree >>> >>> jnielsendotnet:Try what I asked in my first reply (deleting and >>> reinstalling pango manually), and see if you can get any error messages >>> from xfce. >>> >>> If portupgrade -f is failing portupgrade -fr isn't likely to succeed >>> either. >> >> Portupgrade with the -r option is very useful, and you will probably >> want to >> use it. My point was that _before_ you try that you should figure out >> why >> portupgrade is failing to upgrade pango, and/or upgrade it manually. >> Otherwise it will just keep failing. >> >> JN >> > > i guess i can see how u guys r on the same page then. he says -r won't > help, u say it's nice. makes sense I have the feeling that you didn't post the exact error message that you get? So with or without -r is only guessing. It will be very useful to know what failed - portupgrade ot just build and the error messages of course. And if you posted the error, but nobody can see it, this is because you break the thread with subject "NIC (Network Card) is not detected by FreeBSD 6.2 into PowerEdge Blade 1955 Server" and I personally am little lost in your mails ;) There are simple rules if you want everybody to understand you: new problem - new thread, do not top post ;) and of course the most important - explain you problem better - not just "XX does not work, problem?". Explain what you did and how the OS respond, what version you use and etc. After you provide this information we'll gladly help you (if we can) :) > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Best Wishes, Stefan Lambrev ICQ# 24134177