From owner-freebsd-current  Mon Jan 24  6:37: 6 2000
Delivered-To: freebsd-current@freebsd.org
Received: from m2.cs.berkeley.edu (m2.CS.Berkeley.EDU [128.32.45.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id 463B414F84; Mon, 24 Jan 2000 06:37:02 -0800 (PST)
	(envelope-from asami@cs.berkeley.edu)
Received: from silvia.hip.berkeley.edu (sji-ca7-14.ix.netcom.com [209.109.235.14])
	by m2.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id GAA77883;
	Mon, 24 Jan 2000 06:36:54 -0800 (PST)
	(envelope-from asami@cs.berkeley.edu)
Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id GAA23651; Mon, 24 Jan 2000 06:36:44 -0800 (PST)
Date: Mon, 24 Jan 2000 06:36:44 -0800 (PST)
Message-Id: <200001241436.GAA23651@silvia.hip.berkeley.edu>
X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f
To: ports@FreeBSD.org
Cc: current@FreeBSD.org
Reply-To: ports@FreeBSD.org
Subject: 4.0-release (ports) schedule
From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami)
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

Since the 4.0 release is coming up soon, I'd like to remind people to
check the build logs and fix what they can.  The latest one is in

  http://bento.FreeBSD.org/errorlogs/errorlogs/e.4.20000123/

There are over 200 broken ports.  In particular, there are a few dozen
(78 at last count) broken by the gcc upgrade (those marked by "new
compiler error").  It doesn't look good, folks.  Right now we are only
able to build packages for about 2,490 out of the almost 3,000 ports.

Also, the freeze is tentatively scheduled for 2000/01/31, the midnight
when February starts in U.S. West Coast.  That will leave one week and
18 hours.

Thanks for your help and happy port-fixing!

-PW

P.S. Please send fixes via send-pr, not a direct mail to me or the
     ports list.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message