From owner-freebsd-ports@FreeBSD.ORG Wed May 7 11:40:54 2003 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 EB40937B401 for ; Wed, 7 May 2003 11:40:54 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-67-115-75-172.dsl.lsan03.pacbell.net [67.115.75.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E95643FA3 for ; Wed, 7 May 2003 11:40:54 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 1CB9F66B9B for ; Wed, 7 May 2003 11:40:54 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 00E3FFE1; Wed, 7 May 2003 11:40:53 -0700 (PDT) Date: Wed, 7 May 2003 11:40:53 -0700 From: Kris Kennaway To: ports@FreeBSD.org Message-ID: <20030507184053.GA9803@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline User-Agent: Mutt/1.4i Subject: Fixes to broken ports 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: Wed, 07 May 2003 18:40:55 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi guys, As you probably noticed I have done a sweep through the ports tree and marked BROKEN those ports that currently fail on both the 4.x and 5.0 package builds. I tried not to mark BROKEN ports that fail due to a spurious bento error, but it's possible that I might have overlooked some: if so, I apologise - just let me know and I'll remove the BROKEN tag if it was inappropriately added. I didn't check for PRs containing fixes before committing - in fact I know that a lot of the ports I marked BROKEN do have fixes in the PR database. Mark Linimon has been looking into compiling a list of PRs that fix these ports. This kind of thing is periodically necessary to clean up the ports collection and improve the interface for the end-user: trying to build a port only to discover that it fails with a mysterious error makes FreeBSD look bad. Also, by marking the port BROKEN it raises the visibility of the problem, and it encourages committers and other port users to investigate and fix the problem. In fact, in the 48 hours since I started this sweep, a number of ports broken for 6 months or more have already been fixed. If you're the maintainer of a port that was marked BROKEN, for which you have already submitted a fix, please do not take offense to my commit to your port. You've done the right thing by pre-emptively fixing the problems with your port, and it's our fault for not committing your fix before now. Just drop a note to ports@ mentioning the PR number that contains the fix, and one of our committers will commit the fix. Thanks, Kris --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+uVM1Wry0BWjoQKURAtFWAJ9PEdewToip785d9ixhfGqYLl2wdQCeOIDh aH0UpK3O243vhvJPxwktAYE= =2hWc -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--