From owner-freebsd-current@FreeBSD.ORG Sun Jan 11 09:09:18 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 526721065670 for ; Sun, 11 Jan 2009 09:09:18 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail-bw0-f20.google.com (mail-bw0-f20.google.com [209.85.218.20]) by mx1.freebsd.org (Postfix) with ESMTP id B02268FC1D for ; Sun, 11 Jan 2009 09:09:17 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: by bwz13 with SMTP id 13so4642362bwz.19 for ; Sun, 11 Jan 2009 01:09:16 -0800 (PST) Received: by 10.180.218.15 with SMTP id q15mr5889521bkg.194.1231663427057; Sun, 11 Jan 2009 00:43:47 -0800 (PST) Received: by 10.180.255.19 with HTTP; Sun, 11 Jan 2009 00:43:47 -0800 (PST) Message-ID: <1de79840901110043v44d31561vf3a0901e23a31dec@mail.gmail.com> Date: Sun, 11 Jan 2009 03:43:47 -0500 From: "Michael Proto" To: current@freebsd.org In-Reply-To: <20090111081118.GB7054@server.vk2pj.dyndns.org> MIME-Version: 1.0 References: <49695A15.8010801@psg.com> <20090111081118.GB7054@server.vk2pj.dyndns.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Randy Bush , Boris Kovalenko Subject: Re: quagga-0.99.11_1 is marked as broken: does not build. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Jan 2009 09:09:18 -0000 On Sun, Jan 11, 2009 at 3:11 AM, Peter Jeremy wrote: > On 2009-Jan-11 11:31:49 +0900, Randy Bush wrote: > >8-current amd64 a few days old > >"quagga-0.99.11_1 is marked as broken: does not build." > > This looks like fallout from the ARP-v2 patches. See the thread > "HEADSUP: arp-v2 has been committed" here in late December. > I'm not sure how difficult it will be to patch quagga. > > -- > Peter Jeremy > Please excuse any delays as the result of my ISP's inability to implement > an MTA that is either RFC2821-compliant or matches their claimed behaviour. > It looks like isc-dhcp30-server is also affected. Can't find a working dhcpd with CURRENT at the moment. -Proto