Re: radicale can't start

rapid releases are not a problem, it just needs a maintainer who cares.

-- 

  Sent from a phone, apologies for poor formatting.

On 2 May 2025 23:32:38 Mike Fischer <fischer+obsd@lavielle.com> wrote:

Am 02.05.2025 um 18:04 schrieb trondd@kagu-tsuchi.com:

On 2025/05/02 11:30, Hugo Osvaldo Barrera wrote:

On Thu, 1 May 2025, at 20:31, prx wrote:

Hello,

I noticed since 7.7 upgrade that radicale fails to start.

I tried to run it manually, then I see this message:

```

[a5719463ff8] ERROR: An exception occurred during server startup: 

module 'ssl' has no attribute 'wrap_socket'

ERROR:radicale:An exception occurred during server startup: module 

'ssl' has no attribute 'wrap_socket'

```

It seems there are deprecated modules, but maybe I'm wrong?

The deprecated module was removed in Python 3.12:

https://docs.python.org/3.12/whatsnew/3.12.html#ssl

Radicale removed this usage in 2020:

https://github.com/Kozea/Radicale/commit/11ea3cc7a4eadd91867138c4b024ea399ca90634

That change was released later that year, in 3.0.0.

The current port is 1.1.6

There are two current ports, 1.1.6 for migration purposes (the storage

format changed in 2.x), and 2.1.12 (latest 2.x).

The 1.x port needs to die but we haven't been forceful enough in telling

people to update, I've just added a pkg/MESSAGE about this.

The 2.x port needs updating to 3.x, there are incompatible changes but

the storage format is the same, so I think that's ok. Is there somebody

using radicale who can look at doing that update?

(Don't worry about changing the dir name, we can just merge it all into

productivity/radicale, easier to update first and then merge).

Presumably 2.x is broken in the same way as 1.x re ssl wrap_socket;

the simplest temporary workaround is probably to disable TLS in radicale

and put a reverse proxy in front, but updating woukd be better.

Sorry, I do have a WIP update to radicale 3 I haven't had time to send along

yet.  It's the bare minimum to get it running which is when I then discovered

that they no longer deamonize and write to a log file.  Foreground only and I

am not sure if our rc system handles that.

A solution for that problem can be found in:

https://github.com/Kozea/Radicale/wiki/Installing-on-OpenBSD

Hint:

rc_bg=YES

Note: That solution uses a Python virtual environment which given the fairly rapid Radicale releases in recent months seems like a better solution than waiting for the port to be updated? OTOH having a port is nice as well and the port _reserves_ the user/group _radicale.

HTH

Mike