From owner-svn-ports-all@freebsd.org Sun May 6 16:28:07 2018 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39751FC00D0; Sun, 6 May 2018 16:28:07 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E1FF481AE4; Sun, 6 May 2018 16:28:06 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id C0C95BBF5; Sun, 6 May 2018 16:28:06 +0000 (UTC) Date: Sun, 6 May 2018 16:28:06 +0000 From: Alexey Dokuchaev To: Antoine Brodin Cc: Baptiste Daroussin , Kurt Jaeger , Koichiro Iwao , ports-committers , svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r469188 - head/ports-mgmt/pkg_replace Message-ID: <20180506162806.GA20668@FreeBSD.org> References: <201805061015.w46AF3HQ070595@repo.freebsd.org> <20180506102749.GA58637@FreeBSD.org> <20180506103420.GW25490@fc.opsec.eu> <20180506105012.GA39087@FreeBSD.org> <20180506151022.63wom7xgw6doi4dk@ivaldir.net> <20180506160220.GE79630@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 May 2018 16:28:07 -0000 On Sun, May 06, 2018 at 04:10:07PM +0000, Antoine Brodin wrote: > On Sun, May 6, 2018 at 4:02 PM, Alexey Dokuchaev wrote: > > ... > > OK sorry I guess that was a bit too harsh. It's just that folks recently > > seem to jump the gun and aggressively make changes, backout changes, or > > sometimes even delete ports because they don't build in poudriere and/or > > preventing it to start, without giving much of an explanation, and that's > > kind of worrisome IMHO. :-/ > > The port you are referring to prevents poudriere from starting sure, > but it also fails to build from ports. Please stop your FUD. Pardon me, FUD? You could've simply disconnected the troublesome port. You could've provided error logs, you could'be worked with yuri@ together to solve this instead of telling him "why insist?'. And this is not the first time portmgr@ is acting in this fashion (just one example[*]). :-( ./danfe [*] https://lists.freebsd.org/pipermail/svn-ports-head/2017-October/157938.html