Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Jan 2024 04:46:29 -0500
From:      "Mikhail T." <mi+t@virtual-estates.net>
To:        Mathieu Arnold <mat@freebsd.org>
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: git: b430a140c818 - main - net-im/purple-gowhatsapp: add WhatsApp plugin for libpurple
Message-ID:  <7e07375b-32bc-4778-8977-d87d6e135679@virtual-estates.net>
In-Reply-To: <ewlhhqgckfoo4nj2jmryynhh2admdz6wy3lwkyav7nvhok565l@liht5kzkacig>
References:  <202401202030.40KKUApC045320@gitrepo.freebsd.org> <f22ba5fb94cbee57ef6dbac2bdb3db87@mail.infomaniak.com> <f74f9837-121e-47ac-819b-27a40d3b4891@virtual-estates.net> <ewlhhqgckfoo4nj2jmryynhh2admdz6wy3lwkyav7nvhok565l@liht5kzkacig>

next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------1oKAV0WwIo07SqnErV6BFLoC
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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

--------------1oKAV0WwIo07SqnErV6BFLoC
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">21.01.24 02:04, Mathieu Arnold:<br>
    </div>
    <blockquote type="cite"
cite="mid:ewlhhqgckfoo4nj2jmryynhh2admdz6wy3lwkyav7nvhok565l@liht5kzkacig">
      <pre><pre class="moz-quote-pre" wrap="">On Sat, Jan 20, 2024 at 07:30:55PM -0500, Mikhail T. wrote:
</pre><blockquote type="cite" style="color: #007cff;"><pre
      class="moz-quote-pre" wrap="">But why would you want it backed out?!
</pre></blockquote><pre class="moz-quote-pre" wrap="">Because you added a port that does not build.</pre></pre>
    </blockquote>
    <p> 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.</p>
    <p>But this time, as I pointed out already, the failure is due to
      some firewall rule on the build cluster.</p>
    <p>None of the thing Daniel pointed out caused the failure to build.
      It is a firewall rule. Setting <font face="monospace">DEVELOPER</font>
      does not warn about it either.<br>
    </p>
    <blockquote type="cite"
cite="mid:ewlhhqgckfoo4nj2jmryynhh2admdz6wy3lwkyav7nvhok565l@liht5kzkacig">
      <pre><pre class="moz-quote-pre" wrap="">The FreeBSD ports tree is not your own ports tree where you add things to see if they build.</pre></pre>
    </blockquote>
    It certainly is not "my own", but what's wrong with "adding things
    to see if they build"?<br>
    <blockquote type="cite"
cite="mid:ewlhhqgckfoo4nj2jmryynhh2admdz6wy3lwkyav7nvhok565l@liht5kzkacig">
      <pre>You have to ...
You must use ...
You must also ...    </pre>
    </blockquote>
    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".<br>
    <blockquote type="cite"
cite="mid:ewlhhqgckfoo4nj2jmryynhh2admdz6wy3lwkyav7nvhok565l@liht5kzkacig">
      <pre><pre class="moz-quote-pre" wrap="">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.
</pre></pre>
    </blockquote>
    <p>When a change has a potential to affect the work of others, I do
      that. See <a moz-do-not-send="true"
        href="https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276204">PR
        276204</a> 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,</p>
    <blockquote>
      <p>-mi<br>
      </p>
    </blockquote>
  </body>
</html>

--------------1oKAV0WwIo07SqnErV6BFLoC--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7e07375b-32bc-4778-8977-d87d6e135679>