From owner-freebsd-ports@FreeBSD.ORG Sat Apr 30 21:35:57 2005 Return-Path: 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 8536816A4CE; Sat, 30 Apr 2005 21:35:57 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 327D543D48; Sat, 30 Apr 2005 21:35:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 77A56533E6; Sat, 30 Apr 2005 14:35:56 -0700 (PDT) Date: Sat, 30 Apr 2005 14:35:56 -0700 From: Kris Kennaway To: Steven Hartland Message-ID: <20050430213556.GA51804@xor.obsecurity.org> References: <4273D21D.2189.352DF748@d.wagner.absamail.co.za> <008201c54da5$16630d60$b3db87d4@multiplay.co.uk> <009101c54da9$375f9570$b3db87d4@multiplay.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="y0ulUmNC+osPPQO6" Content-Disposition: inline In-Reply-To: <009101c54da9$375f9570$b3db87d4@multiplay.co.uk> User-Agent: Mutt/1.4.2.1i cc: ports@FreeBSD.org cc: d.wagner@absamail.co.za cc: cy@FreeBSD.org Subject: Re: FreeBSD Port: screen-4.0.2_1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Apr 2005 21:35:57 -0000 --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 30, 2005 at 06:22:38PM +0100, Steven Hartland wrote: > Doing make package I get: > =3D=3D=3D> screen-4.0.2_1 may not be packaged: Tends to loop using 100% = CPU > when used from package - perhaps it hard-codes information about the buil= d=20 > host. >=20 > So I assume that's why it was removed but tbh I haven't had this happen= =20 > since > 5.1 days and removing the package is therefore a pain and should be put > back IMO. The bug still exists as far as anyone knows. The reason you haven't seen it happen is because you're no longer using the package. Kris --y0ulUmNC+osPPQO6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCc/o8Wry0BWjoQKURArF7AJ44d8mo4g7wRcDwEvI42AyNVUlyVgCg8ubN Kb8bIU6nOIyvmANK+eb5GCI= =UOcf -----END PGP SIGNATURE----- --y0ulUmNC+osPPQO6--