From owner-freebsd-ports@freebsd.org Tue Mar 21 11:27:43 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37DE8D16684; Tue, 21 Mar 2017 11:27:43 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EA6D11C18; Tue, 21 Mar 2017 11:27:42 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1cqHwy-0003sf-9W; Tue, 21 Mar 2017 12:27:40 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Gleb Smirnoff" , "Baptiste Daroussin" , "Mathieu Arnold" Cc: svn-src-head@freebsd.org, "Antoine Brodin" , svn-src-all@freebsd.org, "FreeBSD Ports" Subject: Re: svn commit: r315662 - in head: contrib/bsnmp/snmp_mibII contrib/ipfilter/ipsend lib/libprocstat sys/netinet sys/sys usr.bin/netstat usr.bin/sockstat usr.bin/systat usr.sbin/tcpdrop usr.sbin/trpt References: <201703210639.v2L6dnRf055522@repo.freebsd.org> <20170321064154.GL23308@FreeBSD.org> <20170321065433.GM23308@FreeBSD.org> <20170321072219.ij2waf2rygmvezoh@ivaldir.net> <20170321072714.GN23308@FreeBSD.org> <81f57d51-8ccf-e0a7-ec9a-5ef816998e76@FreeBSD.org> Date: Tue, 21 Mar 2017 12:27:39 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Ronald Klop" Message-ID: In-Reply-To: <81f57d51-8ccf-e0a7-ec9a-5ef816998e76@FreeBSD.org> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 388a8ff653e0601f0215f26536afca72 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Mar 2017 11:27:43 -0000 On Tue, 21 Mar 2017 10:19:24 +0100, Mathieu Arnold wro= te: > Le 21/03/2017 =C3=A0 08:27, Gleb Smirnoff a =C3=A9crit : >> On Tue, Mar 21, 2017 at 08:22:19AM +0100, Baptiste Daroussin wrote: >> B> On Mon, Mar 20, 2017 at 11:54:33PM -0700, Gleb Smirnoff wrote: >> B> > On Tue, Mar 21, 2017 at 07:50:32AM +0100, Antoine Brodin wrote: >> B> > A> > This change is known to break a ton of ports. More than 1= 00 = >> if >> B> > A> > counting depends. I'm sorry for that and I already started = to = >> fix >> B> > A> > them. >> B> > A> > >> B> > A> > Please send all new breakages to me. >> B> > A> >> B> > A> Hi, >> B> > A> >> B> > A> Exp-runs should happen before breakage happens, not after. >> B> > A> If you already know that it breaks hundreds of ports, please = = >> revert >> B> > A> and request an exp-run. >> B> > >> B> > The exp-run has already been made: >> B> > >> B> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210673 >> B> > >> B> > Wasn't very helpful. >> B> > >> B> >> B> I disagree it was useful it showed you some ports that were breaki= ng = >> given there >> B> was some high level one you were expected to provide patches to fi= x = >> them. >> >> I'm working on them right now. > > You should have worked on it *before* the patch breaking everything > landed, providing patches for the ports that were reported as broken, > and repeat until all the ports that were building before were building= > again. > > You should **not** have committed the patch to the src tree before all= > those patches were created, and you should have committed all the > patches at once, preferably before committing the patch to the src tre= e. > > People should... No ports are broken on released version of FreeBSD. The broken ones are = = being fixed. And a very good improvement of code has happened. Maybe a notice in = UPDATING helps third-party people. I don't see a real problem. Only progress. Ronald.