I think the line:
daemon="${TRUEPREFIX}/bin/radicale -d"
in the rc script is wrong (probably a leftover from the 2.x port). There is no
-d option in Radicale 3.x AFAIC.
Also the Description states that Radicale is a CalDAV server. It is also a
CardDAV server though.
HTH
Mike
> Am 04.05.2025 um 17:53 schrieb TronDD <tro...@kagu-tsuchi.com>:
>
> On Fri May 2, 2025 at 9:27 PM EDT, TronDD wrote:
>> On Fri May 2, 2025 at 8:03 PM EDT, Stuart Henderson wrote:
>>> rapid releases are not a problem, it just needs a maintainer who cares.
>>
>>
>> I'm not sure can be that maintainer, I don't even have time right now to
>> finish this and decide if I want to switch back or not.
>>
>> Anyway thanks for the rc_bg tip, I remember that now that I see it.
>>
>> I was unable to fetch the tarball from pypi so in my haste, I switched to
>> pull from github. I updated the patches but didn't check if there were new
>> things to patch, and did not cleanup the post-install steps. I updated the
>> rc script with rc_gb, though, and verified it worked.
>>
>> It starts, it runs, it worked well enough for me to connect and make sure I
>> could pull my data out of it but that's all I did.
>>
>> There are upgrade steps from v2 to v3 documented in their ChangeLog but I
>> still ended up just running radicale --verify-storage over and over and
>> looking up the errors in the docs.
>>
>> Tim.
>
> I had some time to make another passs. I cleaned up patches, made sure the
> post-install steps were still doing something, and took a stab at updating the
> README.
>
> Tim.
>
>
