From owner-freebsd-ports@FreeBSD.ORG  Sat Sep 20 16:15:52 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9F73116A4B3; Sat, 20 Sep 2003 16:15:52 -0700 (PDT)
Received: from dragoncrest.jasnetworks.net (dragoncrest.jasnetworks.net
	[65.194.254.12])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A1CAD43F85; Sat, 20 Sep 2003 16:15:51 -0700 (PDT)
	(envelope-from dragoncrest@voyager.net)
Received: from j2v6e9.voyager.net (testbox [192.168.0.4])
	h8KIKtGb068245;	Sat, 20 Sep 2003 18:20:56 GMT
	(envelope-from dragoncrest@voyager.net)
Message-Id: <5.2.0.9.2.20030920192225.00a1dec0@pop.voyager.net>
X-Sender: dragoncrest@pop.voyager.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Sat, 20 Sep 2003 19:24:36 -0700
To: Rob Lahaye <lahaye@snu.ac.kr>, freebsd-questions@freebsd.org,
	freebsd-ports@freebsd.org
From: Dragoncrest <dragoncrest@voyager.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: Problem installing/upgrading QT3.2
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Sep 2003 23:15:52 -0000


>Bad philosophy!
>In that case, revert the Qt port back to the previous working Qt 3.1 port
>ASAP and fix it in the meantime.

 >>      Actually, he said he used the package off of the freebsd website 
to reinstall the older version and by doing that he's up and running 
again.  So he's good there.  Myself, I haven't had this issue with QT to 
date.  >> It's installed and upgraded fine for me.  But then again I've 
been lucky so far too.  No major issues at all with KDE...yet.  (*crosses 
fingers*)

         Ok, I withdraw my previous statement.  It appears I'm now having 
the same issues he is.  Decided to do a CVS update on my ports then check 
my KDE versions.  Found out I didn't have the latest version like I 
thought, so I tried updating QT as well and got the exact same issue he did 
to the letter.  So I'm guessing the port is broken somehow.  Oh well, I 
guess I wait for a patched version right along with the rest of ya.