From owner-freebsd-current@FreeBSD.ORG Wed Mar 8 16:26:26 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 BFAF416A420 for ; Wed, 8 Mar 2006 16:26:26 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-3.dlr.de (smtp-3.dlr.de [195.37.61.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 033F643D55 for ; Wed, 8 Mar 2006 16:26:25 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-3.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Wed, 8 Mar 2006 17:26:24 +0100 Date: Wed, 8 Mar 2006 17:26:24 +0100 (CET) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Steve Kargl In-Reply-To: <20060308160227.GB5810@troutmask.apl.washington.edu> Message-ID: <20060308172009.I10582@beagle.kn.op.dlr.de> References: <20060308085714.L10582@beagle.kn.op.dlr.de> <86bqwh59gn.fsf@xps.des.no> <20060308151239.D10582@beagle.kn.op.dlr.de> <20060308160227.GB5810@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 08 Mar 2006 16:26:24.0645 (UTC) FILETIME=[0AF8E350:01C642CD] Cc: 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 Reply-To: Harti Brandt 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:26:26 -0000 On Wed, 8 Mar 2006, Steve Kargl wrote: SK>On Wed, Mar 08, 2006 at 03:29:52PM +0100, Harti Brandt wrote: SK>> On Wed, 8 Mar 2006, Dag-Erling Sm?rgrav wrote: SK>> SK>> DS>Harti Brandt writes: SK>> DS>> You seem to be the only one having this problem, so this looks like SK>> DS>> a problem on your side. SK>> DS> SK>> DS>Far from it. I had the same problem, and solved it by adding a SK>> DS>NO_BSNMP knob (see attached patch). SK>> SK>> So you're the 2nd. Anyone else? I also wonder whether I overlooked a bug SK>> report from you. SK> SK>I haven't seen this particular problem, but bsnmp has broken SK>buildworld more than once due to what appears to be poorly SK>tested patches. I simply disconnect the offending part SK>of bsnmp from my builds. SK> SK>http://lists.freebsd.org/mailman/htdig/freebsd-current/2006-February/061183.html The patch was ok, just forgetting to commit one of the files was not. This was fixed very fast by ru. I usually test all patches with making a universe and building on both i386 and sparc64 and running them on both machines. There is hardly more one could do. harti