-
-
Notifications
You must be signed in to change notification settings - Fork 845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
webdav service : Radicale 3.0 is released. -f option is not longer supported. #1512
Comments
1513: Stick radicale to 2.1.12 version r=mergify[bot] a=ofthesun9 As 3.0 is breaking compatibility with 2.1 branch ## What type of PR? Sticking radicale to 2.1.12, while we investigate changes to use radicale 3.0 ## What does this PR do? Dockerfile modification to add ==2.1.12 ### Related issue(s) - #1512 Co-authored-by: ofthesun9 <olivier@ofthesun.net>
1513: Stick radicale to 2.1.12 version r=ofthesun9 a=ofthesun9 As 3.0 is breaking compatibility with 2.1 branch ## What type of PR? Sticking radicale to 2.1.12, while we investigate changes to use radicale 3.0 ## What does this PR do? Dockerfile modification to add ==2.1.12 ### Related issue(s) - #1512 Co-authored-by: ofthesun9 <olivier@ofthesun.net>
1513: Stick radicale to 2.1.12 version r=ofthesun9 a=ofthesun9 As 3.0 is breaking compatibility with 2.1 branch ## What type of PR? Sticking radicale to 2.1.12, while we investigate changes to use radicale 3.0 ## What does this PR do? Dockerfile modification to add ==2.1.12 ### Related issue(s) - #1512 Co-authored-by: ofthesun9 <olivier@ofthesun.net>
So far, seems that foreground is the default functionality, as 3.0 is delegating daemon duties to service managers. Tho, by the look of incoming issues in Radicale, it probably makes sense to not move to 3.0 just yet. Maybe this ticket could track relevant changes for Radicale 3.0? |
Yes, this PR should remain open until we investigate the changes needed to go switch to radicale 3.0. |
can do, tho likely weekend/next week |
@psukys Thanks ! |
Radicale 3.0.3 released 3 days ago |
Release notes for 3.0
Travis builds are currently failing:
I will propose a PR to stick to radicale 2.1.12, until we have time to investigate what other changes might be needed to use radicale 3.0
The text was updated successfully, but these errors were encountered: