From owner-freebsd-security Sat Apr 15 20:33:47 2000 Delivered-To: freebsd-security@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id 6BB3D37B8C9; Sat, 15 Apr 2000 20:33:42 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id HAA33994; Sun, 16 Apr 2000 07:33:35 +0400 (MSD) (envelope-from ache) Date: Sun, 16 Apr 2000 07:33:34 +0400 From: "Andrey A. Chernov" To: Robert Watson Cc: Will Andrews , security@FreeBSD.ORG, kris@FreeBSD.ORG Subject: Re: Re-enabling lynx-current again Message-ID: <20000416073334.A33963@nagual.pp.ru> References: <20000415223900.H33593@argon.blackdawn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from robert@cyrus.watson.org on Sat, Apr 15, 2000 at 11:14:05PM -0400 Organization: Biomechanoid Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 15, 2000 at 11:14:05PM -0400, Robert Watson wrote: > My understanding is that Kris has been reviewing the changes, and would > presumably be the correct person to remove the BROKEN tag. I'd recommend > leaving it there until he's had a chance to do the review (all bow down to > the Port security officer). Well, I just upgrade lynx-current port to latest version but leave FORBIDDEN status active. I hope Kris review will not take much time: what is suspected as fix was issued by Lynx maintainer at March 26 and still not reviewed. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message