From owner-freebsd-ports Tue Jun 13 7:23:50 2000 Delivered-To: freebsd-ports@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 821C337BE64; Tue, 13 Jun 2000 07:23:30 -0700 (PDT) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from [128.130.111.10] (nunki [128.130.111.10]) by vexpert.dbai.tuwien.ac.at (8.9.3/8.9.3) with ESMTP id QAA12251; Tue, 13 Jun 2000 16:23:28 +0200 (MET DST) Date: Tue, 13 Jun 2000 16:23:26 +0200 (MET DST) From: Gerald Pfeifer To: freebsd-hackers@freebsd.org Cc: ports@freebsd.org, "Jordan K. Hubbard" Subject: Re: -STABLE (was: ncurses.h and #define trace _nc_trace) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ Jordan, I'm Cc:ing you as release engineer as -STABLE has been partially broken for nearly three weeks now. ] On Sat, 3 Jun 2000, Gerald Pfeifer wrote: > This causes clear breakage in -STABLE and lots of wasted time for users > of the Wine port and myself (answering support requests), for example. I reported that problem to -hackers on May 26th. On June 6th I filled it as PR misc/19077 with highest priority and even included a patch. Neither my concerns about the MFC happening before the original patch got installed in -CURRENT nor the problem per se have been addressed. From the mails I get as the (new) maintainer of the Wine port I see that lots of people loose lots of time due this bug in -STABLE and -CURRENT. Is there a way to a) escalate such issues that at least -STABLE gets fixed ASAP? b) mark a port to notify users not to try using it on -STABLE and -CURRENT? Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message