On 2024-03-16, Odhiambo Washington <[email protected]> wrote:
>
> On Sat, Mar 16, 2024 at 3:57=E2=80=AFPM Mark <[email protected]> wr=
> ote:
>
>> On Wed, Mar 13, 2024 at 5:44=E2=80=AFPM Odhiambo Washington <odhiambo@gma=
> il.com>
>> wrote:
>>
>>>
>>> This is why I suggested he should run Mailman3 from the word go.
>>>
>>>
>>>
>> It looks almost impossible to setup Mailman3 on OpenBSD.
>>
>> No, this is not working at all;
>> https://xn--gckvb8fzb.com/mailman3-on-openbsd-71/
>>
>> Any other tutorial I could try?
>>
>> Thank you.
>>
>
> What exactly isn't working for you?
Yes, this is a key thing when asking questions. Saying "No, this is not
working at all" followed by a URL is not much help. Copy text from
a terminal, showing _what commands you ran_ and _what you saw_.
> The setup is actually pretty easy.
mailman itself should be fairly easy to get installed in a venv, but
mailman-web pulls in cryptography and that can be problematic sometimes.
Trying to build that via pip isn't working at the moment in -current:
error: failed to run custom build command for `openssl-sys v0.9.99`
...
This crate is only compatible with OpenSSL (version 1.0.1
through 1.1.1, or 3), or LibreSSL 2.5 through 3.8.1, but a
different version of OpenSSL was found. The build is now
aborting due to this version mismatch.
- so you'll probably have better luck by installing py3-cryptography
from packages (when built in ports, openssl-sys is automatically
patched to fix this problem), and when you create the venv, use
--system-site-packages to allow the system package to be used.
*However*, if you're doing this on a system which already has various
python packages installed, using this may result in some conflicts with
other software, so if you run into problems from that and can't
uninstall the relevant package, you may need to use a fairly clean
machine.
(The ideal thing would be to get mailman updated to 3.x in ports,
but looking at 'pip list' after installing mailman and mailman-web
in a venv, there are 84 modules installed, getting on for 40 not
in ports yet, and some of the others probably need updating -
possibly with a ripple effect on other ports - so it's a lot of
work; running in a venv with most things installed via pip is
a saner option).
--
Please keep replies on the mailing list.
