Date: Sun, 21 Jan 2024 11:16:15 +0100 From: Mathieu Arnold <mat@freebsd.org> To: "Mikhail T." <mi+t@virtual-estates.net> Cc: Daniel Engberg <daniel.engberg.lists@pyret.net>, ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: Re: git: b430a140c818 - main - net-im/purple-gowhatsapp: add WhatsApp plugin for libpurple Message-ID: <ptq5dukjavkfpoe2gic6mssywdxh7f77xsounaxmy5llxinz2j@w6243b7unduq> In-Reply-To: <7e07375b-32bc-4778-8977-d87d6e135679@virtual-estates.net> References: <202401202030.40KKUApC045320@gitrepo.freebsd.org> <f22ba5fb94cbee57ef6dbac2bdb3db87@mail.infomaniak.com> <f74f9837-121e-47ac-819b-27a40d3b4891@virtual-estates.net> <ewlhhqgckfoo4nj2jmryynhh2admdz6wy3lwkyav7nvhok565l@liht5kzkacig> <7e07375b-32bc-4778-8977-d87d6e135679@virtual-estates.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--2bvwv5v2o4gvonz4 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 21, 2024 at 04:46:29AM -0500, Mikhail T. wrote: > 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. >=20 > 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. >=20 > But this time, as I pointed out already, the failure is due to some firew= all > rule on the build cluster. Ah, no, it's not some firewall rule on the build cluster, it is how the build has worked for the last 11 years when poudriere was created and was made the official way we build everything. The only time network access is authorized is during the fetch phase. You would probably know that if you used poudriere to test your ports like everybody else does. > 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. >=20 > > 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"? Well, it's not your personal sandbox, it is the official FreeBSD ports repository. You must test your changes before you submit them to make sure they actually work. You obviously did not here. > > 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 wor= ded > anywhere as strongly as "must". In any corporate world, when your manager tells you those things, you say "yes" and you do it, or you go work somewhere else. It is not the first time you have been told these things, and yet, you still refuse to abide by the rules we all follow. Those rules don't need to be written anywhere, especially when you've been told those rules at one point or another along the years. > > 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 someon= e else can run those tests. >=20 > 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=3D276204>; fo= r 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=A0 longer time-period). Please, = take > care of your own demons privately. Thank you. Yours, Well, your port is broken and cannot be built, yet, it is not marked BROKEN, so it will waste time again and again on the package building cluster. --=20 Mathieu Arnold --2bvwv5v2o4gvonz4 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQITBAABCgB9FiEE9XJBpJetWizkEBUef2IOCp6dQb4FAmWs7u9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY1 NzI0MUE0OTdBRDVBMkNFNDEwMTUxRTdGNjIwRTBBOUU5RDQxQkUACgkQf2IOCp6d Qb7EJQwAuhjeH6Q0Zjo+upzs5wtK/tEv2P3ykqr993dcym+5y4jj0JcgUtQE3RT9 4OsX11GwDDN7um4ndU+AovuAejSRg4GFxshCoTptBBKAyIJ7CJci6bdj9rA8x9t7 Z7FEPuUcoMhnfGRS8fa1kGj0pVKoJyfyYOVvsvkGHB77felWJ71dRXaNrMsgFk0e 0k5euNm6w967ABJFst9bgXvxjcoHvjYYmBK00toBHn8W8BtcbFI15Z4jpiSmvSnJ /xgj4tMkmyOZYcOowfVzWU7V6DN6HYD9z0eaTkdUQAUs5KJpGJNp0h23QZ04RBSe fsNHup09G1VxzYivgOfSsJ3QbxGKYc3dwB7I1QKysrb1pZtUOMETEV2XlBzV/bVR Ki56lrQiefAmcaCjqojWiYXGnuVHBrNJDj1PE4hyyOIwSVNmnUikXN4VD5NP8O8H +1vz1c2fWeM5ze1kNsFNFzOYs+D6jtg8kZKArvcbCEgNrqOw2hs1rr4hi5C4EO0m ZkCI9PMh =W1SJ -----END PGP SIGNATURE----- --2bvwv5v2o4gvonz4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ptq5dukjavkfpoe2gic6mssywdxh7f77xsounaxmy5llxinz2j>