From owner-freebsd-current@FreeBSD.ORG Wed Mar 8 16:02:32 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA0AB16A420; Wed, 8 Mar 2006 16:02:32 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D58243D49; Wed, 8 Mar 2006 16:02:30 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id k28G2Ruw006371; Wed, 8 Mar 2006 08:02:28 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id k28G2RVR006370; Wed, 8 Mar 2006 08:02:27 -0800 (PST) (envelope-from sgk) Date: Wed, 8 Mar 2006 08:02:27 -0800 From: Steve Kargl To: Harti Brandt Message-ID: <20060308160227.GB5810@troutmask.apl.washington.edu> References: <20060308085714.L10582@beagle.kn.op.dlr.de> <86bqwh59gn.fsf@xps.des.no> <20060308151239.D10582@beagle.kn.op.dlr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060308151239.D10582@beagle.kn.op.dlr.de> User-Agent: Mutt/1.4.2.1i Cc: deischen@freebsd.org, Dag-Erling Sm?rgrav , current@freebsd.org Subject: Re: When will bsnmp stop breaking -current builds 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: Wed, 08 Mar 2006 16:02:32 -0000 On Wed, Mar 08, 2006 at 03:29:52PM +0100, Harti Brandt wrote: > On Wed, 8 Mar 2006, Dag-Erling Sm?rgrav wrote: > > DS>Harti Brandt writes: > DS>> You seem to be the only one having this problem, so this looks like > DS>> a problem on your side. > DS> > DS>Far from it. I had the same problem, and solved it by adding a > DS>NO_BSNMP knob (see attached patch). > > So you're the 2nd. Anyone else? I also wonder whether I overlooked a bug > report from you. I haven't seen this particular problem, but bsnmp has broken buildworld more than once due to what appears to be poorly tested patches. I simply disconnect the offending part of bsnmp from my builds. http://lists.freebsd.org/mailman/htdig/freebsd-current/2006-February/061183.html -- Steve