Replies: 3 comments
-
|
The reason for this problems seems to be a change in DAVx5 fork of the /e/ project, as @patrickunterwegs explaint in a GitHub Dicussion. An issue at /e/ project about this exists here, but was closed as inactive. |
Beta Was this translation helpful? Give feedback.
-
|
Oh I see. Sorry I made a duplicate, I didn't look at the discussions, only issues. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, sorry for the late reply on this. Life has been a bit harsh in the last couple of months. However, trying to catch up what I had to leave behind. I will still move this topic to discussions to keep it open for other users. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
/e/os has a built-in webdav client. It's a fork of dav5x, the source is accessible here: https://gitlab.e.foundation/e/os/AccountManager
JTX board currently doesn't recognize this as a viable backend.
Describe the solution you'd like
I wish to use this built-in account manager/webdav client as a synchronization backend instead of separately installing dav5x.
Describe alternatives you've considered
Dav5x works fine for synchronization, as far as I can tell, it isn't bothered by the /e/ client.
Additional context
If work from the /e/ side is required to achieve this, leave it be, since I can't upgrade to the latest release due to a bug.
Your current device and version
Beta Was this translation helpful? Give feedback.
All reactions