Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Jan 2024 04:55:50 +0000
From:      Alexey Dokuchaev <danfe@freebsd.org>
To:        "Mikhail T." <mi+t@virtual-estates.net>
Cc:        Daniel Engberg <daniel.engberg.lists@pyret.net>, Kurt Jaeger <pi@freebsd.org>, 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:  <Za31VoG8TQkGXIJ_@FreeBSD.org>
In-Reply-To: <7ae9295a-0b05-4589-85d9-440ba373707f@virtual-estates.net>
References:  <ewlhhqgckfoo4nj2jmryynhh2admdz6wy3lwkyav7nvhok565l@liht5kzkacig> <7e07375b-32bc-4778-8977-d87d6e135679@virtual-estates.net> <ptq5dukjavkfpoe2gic6mssywdxh7f77xsounaxmy5llxinz2j@w6243b7unduq> <8ab62f5f-bb62-4633-9d1c-d7a8a8e1fc8a@virtual-estates.net> <Zaz0W9odSaxyDrCj@fc.opsec.eu> <13433172-a8cb-494c-a435-fd4d8418a2e6@virtual-estates.net> <21dcca053d36f9bec4005ffb18897f51@mail.infomaniak.com> <df410abd-dd00-4e7e-83eb-f8a95ec15b9f@virtual-estates.net> <d745fc126e79b4455dfc3e87964baa54@mail.infomaniak.com> <7ae9295a-0b05-4589-85d9-440ba373707f@virtual-estates.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Za31VoG8TQkGXIJ_>