Re: git: b430a140c818 - main - net-im/purple-gowhatsapp: add WhatsApp plugin for libpurple
Date: Mon, 22 Jan 2024 04:55:50 UTC
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