From owner-freebsd-questions@FreeBSD.ORG Thu Nov 8 19:37:29 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D47F16A421 for ; Thu, 8 Nov 2007 19:37:29 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id A501113C4BE for ; Thu, 8 Nov 2007 19:37:28 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.1/8.14.1) with ESMTP id lA8JbBX8070007; Thu, 8 Nov 2007 12:37:11 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.1/8.14.1/Submit) with ESMTP id lA8JbBFM070004; Thu, 8 Nov 2007 12:37:11 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Thu, 8 Nov 2007 12:37:11 -0700 (MST) From: Warren Block To: Andrew Falanga In-Reply-To: <340a29540711080658y2567679epd1e11c584d1c9ed2@mail.gmail.com> Message-ID: <20071108123459.J69893@wonkity.com> References: <340a29540711080658y2567679epd1e11c584d1c9ed2@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (wonkity.com [127.0.0.1]); Thu, 08 Nov 2007 12:37:11 -0700 (MST) Cc: User Questions Subject: Re: Botched X.org upgrade, need help X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2007 19:37:29 -0000 On Thu, 8 Nov 2007, Andrew Falanga wrote: > Well, at last I think it's botched. I really was following the directions > (I have the script file as UPDATING suggests to prove it :-), but the > upgrade didn't work as the X server failed to start after I rebooted. I'm > hoping some kind person here will know the answer before I e-mail the list > mentioned in that section of UPDATING. Anyway, that's basically, what > happened. I have kdm set to start on bootup and it complained that X failed > to start. > > When I got to the point of "portupgrade -aP" in the UPDATING section for > X.org 6.9 -> 7.2; I decided to go with that command instead of "portupgrade > -a" thinking that by now, even for amd64, the packages would be available. > Perhaps a bad assumption. Anyway, once that completed, the stats reported > by portupgrade were disconcerting but I thought that it was ok and > continued. portupgrade reported that only 2 packages were porcessed, most > were ignored with 50 some skipped and 1 failed. > > I then proceeded to the mergebase.sh script, ran that and when I was > satisfied that all was done as expected, I rebooted my machine. Well, > that's when X failed to start. So, how would I go about correcting this > problem? You'll at least have to do a portupgrade -a to get all the ports that still need to be built. -Warren Block * Rapid City, South Dakota USA