Skip to content

Fix compatibility with radicale >= 3.5.10#365

Open
phaer wants to merge 3 commits intoetesync:masterfrom
phaer:fix/radicale-3.6.0-compat
Open

Fix compatibility with radicale >= 3.5.10#365
phaer wants to merge 3 commits intoetesync:masterfrom
phaer:fix/radicale-3.6.0-compat

Conversation

@phaer
Copy link
Copy Markdown

@phaer phaer commented Feb 26, 2026

First commit is the same as #360, but gated behind a version check for backwards compatibility.

The second one handles change in the signature of WSGIReponse after Kozea/Radicale@64f5e585

@Xiretza @tasn

@phaer phaer changed the title Fix compatibility with radicale >= 3.5.5 Fix compatibility with radicale >= 3.5.10 Feb 26, 2026
phaer added a commit to phaer/nixpkgs that referenced this pull request Feb 26, 2026
Radicale 3.5.5 changed the upload() return type to a 2-tuple and
Radicale 3.5.10 changed WSGIResponse from a 3-tuple to a 4-tuple.

Proposed for upstreaming in etesync/etesync-dav#365
phaer added a commit to phaer/nixpkgs that referenced this pull request Feb 27, 2026
Radicale 3.5.5 changed the upload() return type to a 2-tuple and
Radicale 3.5.10 changed WSGIResponse from a 3-tuple to a 4-tuple.

Proposed for upstreaming in etesync/etesync-dav#365
ahernandezjr pushed a commit to ahernandezjr/nixpkgs that referenced this pull request Mar 3, 2026
Radicale 3.5.5 changed the upload() return type to a 2-tuple and
Radicale 3.5.10 changed WSGIResponse from a 3-tuple to a 4-tuple.

Proposed for upstreaming in etesync/etesync-dav#365
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant