> On Sep 24, 2024, at 20:30, Yasuhiro Kimura wrote:
>
>> The upstream being EOL’d doesn’t, IMO, affect the support we have in ports.
>> Unless we’re EOL’ing the port, then we should fix the problem in our
>> script that we install with the port.
>>
>
> Then you should submit bug report to Fre
> On Sep 24, 2024, at 07:56, Matthias Fechner wrote:
>
> you are aware, that dhcpd is EOL since end of 2022:
> https://www.isc.org/dhcp/
>
> and was replaced by kea?
>
> Not sure if it makes sense to put much effort into it.
The upstream being EOL’d doesn’t, IMO, affect the support we have
> On Sep 24, 2024, at 03:38, Tatsuki Makino wrote:
>
> Hello.
>
> As seen from the output of set -x, I think it has been trimmed too much.
>
> https: //cgit.freebsd.org
> /ports/tree/net/isc-dhcp44-server/files/isc-dhcpd.in#n505
>
> Is there a workaround?
>
> dhcpd_flags="-q -4"
> or
> dh
> On Sep 24, 2024, at 03:11, Helge Oldach wrote:
>
> Chris Ross wrote on Tue, 24 Sep 2024 04:59:39 +0200 (CEST):
>> I have in /etc/rc.conf:
>>
>> dhcpd_flags="-4 -q
>
> This one perhaps?
Bah. That was a cut-n-paste and then Mail changed it. I h
Hello. FreeBSD 14.1, isc-dhcp44-server-4.4.3P1_1. I find when I run
“service isc-dhcpd restart”, I get failures/errors boiling down to:
Unknown command -4-cf
Usage: dhcpd [-p ] [-f] [-d] [-q] [-t|-T]
[-4|-6] [-cf config-file] [-lf lease-file]
Tracing the script, I see this is caused b
> On Sep 11, 2024, at 13:38, Ronald Klop wrote:
>
> Has this py-OpenSSL issue been resolved already?
> If not, I can take a look in the near future.
>
> Regards,
Not that I know of, but I haven’t tried to reproduce it recently. I got around
It manually and moved on. :-)
I can check this
> On Aug 24, 2024, at 16:55, Peter Pentchev wrote:
>
> On Sat, Aug 24, 2024 at 02:45:28PM -0400, Chris Ross wrote:
>> So, I'm looking for a simple proxy. I have used simpleproxy in the past,
>> but it doesn’t support IPv6 currently. In looking at options, I see
&g
So, I'm looking for a simple proxy. I have used simpleproxy in the past,
but it doesn’t support IPv6 currently. In looking at options, I see
net/tcpproxy, but I can’t tell if that project is still alive at all.
https://www.spreadspace.org/tcpproxy/ exists an supplies tarballs, but
has no good info
> On Aug 19, 2024, at 08:33, Chris Ross wrote:
> Yes. I would expect that downgrading py-cryptography might be best, but
> upgrading py-openssl would also work. And you’re right there isn’t
> a build problem, but trying to run deluge produces:
>
> --- 8< —-- 8<- ---
> On Aug 18, 2024, at 16:55, Edward Sanford Sutton, III
> wrote:
>
> On 8/18/24 13:19, Chris Ross wrote:
>> I’m installing deluge-cli with pkg, and I am (as default I think) pointed to
>> quarterly packages from FreeBSD. However, deluge-cli needs py311-openssl
I’m installing deluge-cli with pkg, and I am (as default I think) pointed to
quarterly packages from FreeBSD. However, deluge-cli needs py311-openssl,
which gets me py311-openssl-23.2.0. pyopenssl needs py-cryptography, and
when I ask pkg for py311-cryptography it gets me py311-cryptography-42.0.8
11 matches
Mail list logo
