From owner-freebsd-questions@FreeBSD.ORG Sat Sep 20 18:14:58 2003 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 A6EAE16A4BF; Sat, 20 Sep 2003 18:14:58 -0700 (PDT) Received: from mandarin.fruitsalad.org (pc117.net160.koping.net [81.16.160.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6F1543FF3; Sat, 20 Sep 2003 18:14:45 -0700 (PDT) (envelope-from lauri@fruitsalad.org) Received: from kurant.internal.hasta.se ([192.168.15.5]) by mandarin.fruitsalad.org with esmtp (Exim 4.14) id 1A0soG-000EOe-T4; Sun, 21 Sep 2003 03:14:44 +0200 Received: from kurant.internal.hasta.se (localhost [127.0.0.1]) h8L1EE1I033439; Sun, 21 Sep 2003 03:14:14 +0200 (CEST) (envelope-from lauri@kurant.internal.hasta.se) Received: from localhost (localhost [[UNIX: localhost]]) by kurant.internal.hasta.se (8.12.9/8.12.9/Submit) id h8L1EEgs033438; Sun, 21 Sep 2003 03:14:14 +0200 (CEST) From: Lauri Watts To: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Date: Sun, 21 Sep 2003 03:14:06 +0200 User-Agent: KMail/1.5.9 References: <5.2.0.9.2.20030920192225.00a1dec0@pop.voyager.net> In-Reply-To: <5.2.0.9.2.20030920192225.00a1dec0@pop.voyager.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200309210314.14041.lauri@kde.org> Subject: Re: Problem installing/upgrading QT3.2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: lauri@kde.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 01:14:58 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 21 September 2003 04.24, Dragoncrest wrote: > >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 d= id > 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. Patch may be a while forthcoming, Qt seems to think your machines are runn= ing=20 windows during the install, when they perfectly well figured out they weren= 't=20 during the build. In any case, it appears that the fix at this point is simply uninstall any= =20 existing Qt version, and install the new one. Packages are available for=20 4-STABLE and 5.1-RELEASE, instructions at the second address in my .sig Regards, =2D --=20 Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/ =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/bPtk/gUyA7PWnacRAueHAKCUTS0mmSwmVXvQbecHXHS9GQSVzgCfUmVz iV/DOVMwybhHolBUjgd/F40=3D =3DkTi5 =2D----END PGP SIGNATURE-----