Peter Bieringer

@deronnax can you please dig into why the "lint" test failed?

@deronnax this broke more now...can you try to run test suite locally (https://github.com/Kozea/Radicale/wiki/Development-Testing-Release#complete-test-suite) to fix this

@deronnax - is it possible to provide still setup.py for legacy support? I ran here into a **deadlock** while trying packaging for EPEL9: - pyproject.toml requires a higher version than...

BTW: in worst case I revert this until at least python3.11-bcrypt appears on EPEL9.

Just note that I was able to use the legacy files to package for EL8 and EL9, will include them in the package for now with .legacy suffix and in...

@deronnax - currently I have adjusted in pre-next release tests simply the spec files for EL8 and EL9 and use the setup.*.legacy files - working well: ``` %{__rm} pyproject.toml %{__cp}...

@vuntz : - what do you mean with "update"? - which version are you using? - which client is in use? If I e.g. create a new item with "Thunderbird",...

@vuntz : understood now the situation, never watched for it so far. Touching the storage cache code for this "upgrade" scenario only sounds like an overkill for now, potentially it...

Starting "radicale" as a *user* with systemd was never tested so far, why not starting "radicale" as a system service using the anyhow created system user "radicale"? This is well...

Please setup an "Apache" reverse proxy in parallel with suggested configuration, validate that it's working e.g. by using hints from - https://github.com/Kozea/Radicale/wiki/Reverse-Proxy-Diagnostics-Troubleshooting - https://github.com/Kozea/Radicale/wiki/Server-Diagnostics---Troubleshooting (but using reverse proxy port instead...