Re: git: b430a140c818 - main - net-im/purple-gowhatsapp: add WhatsApp plugin for libpurple
- Reply: Mathieu Arnold : "Re: Re: git: b430a140c818 - main - net-im/purple-gowhatsapp: add WhatsApp plugin for libpurple"
- In reply to: Mathieu Arnold : "Re: Re: git: b430a140c818 - main - net-im/purple-gowhatsapp: add WhatsApp plugin for libpurple"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 21 Jan 2024 09:46:29 UTC
21.01.24 02:04, Mathieu Arnold: > On Sat, Jan 20, 2024 at 07:30:55PM -0500, Mikhail T. wrote: >> But why would you want it backed out?! > Because you added a port that does not build. That's not a reason to back it out even if it really failed due to some mistake on my part. I made such mistakes before. But this time, as I pointed out already, the failure is due to some firewall rule on the build cluster. None of the thing Daniel pointed out caused the failure to build. It is a firewall rule. Setting DEVELOPER does not warn about it either. > The FreeBSD ports tree is not your own ports tree where you add things to see if they build. It certainly is not "my own", but what's wrong with "adding things to see if they build"? > You have to ... > You must use ... > You must also ... Would you mind pointing the rules and the bylaws, that you allege I violated? Are they spelled out somewhere? Nothing I'm able to find is worded anywhere as strongly as "must". > If you are not willing to do those basic things everyone else is doing, then please do not push changes yourself and only submit PR so that someone else can run those tests. When a change has a potential to affect the work of others, I do that. See PR 276204 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276204> for the most recent example. But this was simply a new port. If it failed, no one is any worse off, than if it didn't exist at all. And yet, you're coming down on me like I ruined your day (or an evenĀ longer time-period). Please, take care of your own demons privately. Thank you. Yours, -mi