Skip to content
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

Closed
ofthesun9 opened this issue May 20, 2020 · 5 comments · Fixed by #1526
Closed

webdav service : Radicale 3.0 is released. -f option is not longer supported. #1512

ofthesun9 opened this issue May 20, 2020 · 5 comments · Fixed by #1526
Labels
priority/p2 Minor bug / Could have

Comments

@ofthesun9
Copy link
Contributor

Release notes for 3.0
Travis builds are currently failing:

Printing logs for: webdav_webdav_1_e0f619906f75
usage: radicale [OPTIONS]
radicale: error: unrecognized arguments: -f

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

@ofthesun9 ofthesun9 added the priority/p0 Critical bug without workaround / Must have label May 20, 2020
bors bot added a commit that referenced this issue May 20, 2020
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 <[email protected]>
bors bot added a commit that referenced this issue May 20, 2020
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 <[email protected]>
bors bot added a commit that referenced this issue May 21, 2020
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 <[email protected]>
@psukys
Copy link

psukys commented May 26, 2020

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?

@ofthesun9
Copy link
Contributor Author

Yes, this PR should remain open until we investigate the changes needed to go switch to radicale 3.0.
Fot the time being, master is built with Radicale 2.1.12. There is also a backport for Mailu 1.7, but not merged yet.
I could push a PR to get a build against Radicale 3.0, but I can't run functional test for the time being..
@psukys , would you have time to do some functional tests on Radicale 3.0 ?

@psukys
Copy link

psukys commented May 27, 2020

can do, tho likely weekend/next week

@ofthesun9
Copy link
Contributor Author

@psukys Thanks !
the build with radicale 3.0 is available through: mailutest/radicale:pr-1526

@ofthesun9 ofthesun9 added priority/p2 Minor bug / Could have and removed priority/p0 Critical bug without workaround / Must have labels Jun 3, 2020
@ofthesun9
Copy link
Contributor Author

ofthesun9 commented Jun 9, 2020

Radicale 3.0.3 released 3 days ago
I will rebuild the test image mailutest/radicale:pr-1526

@bors bors bot closed this as completed in 3e533a8 Aug 9, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority/p2 Minor bug / Could have
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants