From nobody Mon Jan 22 04:55:50 2024 X-Original-To: dev-commits-ports-all@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TJHwk4JGXz5732B; Mon, 22 Jan 2024 04:55:50 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TJHwk3c9sz54lG; Mon, 22 Jan 2024 04:55:50 +0000 (UTC) (envelope-from danfe@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705899350; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=LPb2fO6oD2YrFbYxdrt+Iv7ouhmFzLuG+54Z3AjbkIg=; b=HGqqTjsGq7buILs4VTkt5Gm4lS1w69HJ3noVZZgRyF/CfxXKWoGGNy0PLHWf5GNF9y7NmB Nq+AJ0B1VKouSoEupJiDgOi3omR30VlUbHxvJmRAhfWa1cNSNdR7MoFqV0g+5PcyW3PzXM GMpAfQNdyGujRgmlGpbPn84Q97iEpkwB27xKDWupa+6dmSysBXkEbG7Y4lfLtbuXF0ccXz p6rWlYClBodzhLh8AQduTWKqGApVK5cmGMDjnwJzXkZ7KnTx2p/thXJJ0az0RTcyAnNFPX Dz4uwZ7BH3ycFLAjYeJKtlxixcnqNWj6A4cJBX+6HpyCedtmKeRJIYCjRVPEWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1705899350; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=LPb2fO6oD2YrFbYxdrt+Iv7ouhmFzLuG+54Z3AjbkIg=; b=vtGi4AItcETz7RiHs9RQOgBf8hE6ZsGBXUErU5K8bPHKo8ZUM09bNxyOzVqvwZOpQ28ZeS tyZsl/sKl6rK6ZqatPq2sncz+qizT7Id7Hta7rnP8zDnHUNHEl9NdiYkcVCIM9+G4LKAw5 QwZlnAZqD6PPx8scfMggRITKVh8FFFIwjQcaXLZLpoGyVPwUasqTMyP19jhnhu7xKB2ewB x2I0vGK1uiO6T9F0T+k/kmBHY9XS4mOtRw9Zwtw5MPQIAXfpQTmmMZFgIdLLbsmBbqvWtE fjb1pLMLhz5NpjSqauQbAwKuqdqseYNLY5Obfkk+UoW/xgLoXC5OH09uTzw6eQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1705899350; a=rsa-sha256; cv=none; b=yudcGK/Et2SA9tLRQKqy3w2DFPeSAMtuDfxmvGrV5e/7VjEarMz0H5hhNpAtrnbJtIG8Q6 JiZW4As7/AYIGm6CvwDCz6A1IRlTB1LbSJSyVv2qy0cMUu9J0wgHEoZHFjD0iRi4efiBgH DLCP7xImVXJ5/HtUGmHKEnbiScL+zPduZgFOA43qNV69AZwDFipQcFn0FXNjpJ/xgPs6cC rzpwkSkzIlfyvF9h+rHge/xYqPs+GVwUIVPnZntr2eXGNn1QxyQ33M8OY7zSzwQ9K1lzjp kEi1rA2fshdkprJaQVVnUt6/2w6oVePTMXpl1pBo6+tRKSaxPMlUlhcAts0fnQ== Received: by freefall.freebsd.org (Postfix, from userid 1033) id 4640919C10; Mon, 22 Jan 2024 04:55:50 +0000 (UTC) Date: Mon, 22 Jan 2024 04:55:50 +0000 From: Alexey Dokuchaev To: "Mikhail T." Cc: Daniel Engberg , Kurt Jaeger , ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: b430a140c818 - main - net-im/purple-gowhatsapp: add WhatsApp plugin for libpurple Message-ID: References: <7e07375b-32bc-4778-8977-d87d6e135679@virtual-estates.net> <8ab62f5f-bb62-4633-9d1c-d7a8a8e1fc8a@virtual-estates.net> <13433172-a8cb-494c-a435-fd4d8418a2e6@virtual-estates.net> <21dcca053d36f9bec4005ffb18897f51@mail.infomaniak.com> <7ae9295a-0b05-4589-85d9-440ba373707f@virtual-estates.net> List-Id: Commit messages for all branches of the ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-all@freebsd.org X-BeenThere: dev-commits-ports-all@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7ae9295a-0b05-4589-85d9-440ba373707f@virtual-estates.net> On Sun, Jan 21, 2024 at 02:16:19PM -0500, Mikhail T. wrote: > 21.01.24 13:47, Daniel Engberg: > > ... > > In reality it adds noise (which we already have enough of) on lists, > > Poudriere builds (because by default we build all ports) takes more time > > producing nothing, more time for people to review error logs and so on. > > All of this could be silenced with BROKEN, no? Yes, it could; I agree that backout request was uncalled for as you were in touch and actively working on a fix. However, you should not have pushed untested changes to the tree in the first place (whether it builds and works at your machine locally is irrelevant). > I [...] still don't understand the scale of the blowback... Perhaps because this is not the first time when your negligence to test things properly causes trouble? Last time I had to disable X265 across the tree as your update had broken it (even if temporarily, it was still quite annoying). Please find an appropriate tool (there are several, if p*re is not your cup of tea) which can provide sufficient Q/A control. ./danfe