Hello,
I submitted a patch for mail/mailman3 more than one year ago [1]. It
required updates to multiple ports, which all have been merged, but
mail/mailman3 has not. Since the original report, I added an updated
patch to upgrade to 3.3.5 and I just finished building 3.3.7 locally.
The curre
Hi guys
I hope you're doing well
I wanted to tell you that I'm currently working on games/jaggedalliance2
upgrade to 0.20.0 (
https://ja2-stracciatella.github.io/2022/11/14/release-0.20.0.html) which
brings support for newer miniaudio-0.11
That means that
https://cgit.freebsd.org/ports/commit/?i
What's the policy on dodgy acting ports?
I had elinks crash (well, the spidermonkey part crashed)
elinks then accused me of editting the config file manually (I hadn't)
and then went into an intentional endless loop.
I think this should be patched out:
| src/util/error.c :
|
| /* Us
On 2022-11-14 16:05, Jamie Landeg-Jones wrote:
What's the policy on dodgy acting ports?
I had elinks crash (well, the spidermonkey part crashed)
elinks then accused me of editting the config file manually (I hadn't)
and then went into an intentional endless loop.
I think this should be patched
On 2022-11-10 10:58:04 (+0800), Jan Beich wrote:
Simon Wright writes:
My issue is that since the build servers are IPv6-only and my
provider
in Philippines does not offer any IPv6 service at all, I need to use
a
proxy to use curl to access this file:
http://beefy16.nyi.freebsd.org/data/131am
On Mon, 14 Nov 2022, Chris wrote:
> Exceptionally bad behavior for anything in the ports tree.
> I think this port should be patched out of the ports tree.
And then block that creature from ever having anything to do with ports
again... That is a gross abuse of trust.
-- Dave
Jamie Landeg-Jones wrote:
> What's the policy on dodgy acting ports?
>
> I had elinks crash (well, the spidermonkey part crashed)
>
> elinks then accused me of editting the config file manually (I hadn't)
> and then went into an intentional endless loop.
>
> I think this should be patched out:
El mar., 15 nov. 2022 1:05, Jamie Landeg-Jones escribió:
> What's the policy on dodgy acting ports?
>
> I had elinks crash (well, the spidermonkey part crashed)
>
> elinks then accused me of editting the config file manually (I hadn't)
> and then went into an intentional endless loop.
>
> I think
