emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Loris Bennett" <loris.bennett@fu-berlin.de>
To: emacs-orgmode@gnu.org
Subject: Re: org-caldav-sync hanging
Date: Tue, 12 May 2020 12:59:22 +0200	[thread overview]
Message-ID: <873685qv05.fsf@hornfels.zedat.fu-berlin.de> (raw)
In-Reply-To: <87zhadphm1.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Tue, 12 May 2020 11:33:58 +0100")

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Tuesday, 12 May 2020 at 09:29, Loris Bennett wrote:
>> The Nextcloud instance at work is version 15 and is accessible via the
>> browser, but there was some outage recently and some server-side
>> tweakage may also have occurred while things were being fixed.
>
> I don't know if this is related but a recent point release to nextcloud
> caused problems with an OPTIONS directive that org-caldav-sync uses.  A
> subsequent bug fix has corrected this but may not have been incorporated
> in your server yet.
>
> See https://github.com/nextcloud/server/issues/20624
>
> The provider I use for calendar services had to manually patch their
> instance of nextcloud to get it working again for org-caldav-sync.

Thanks for the pointer, but the link seems to refer to a regression
introduced between versions 18.0.3 and 18.0.4, whereas the server I am
talking to is some version of version 15.

My android phone is able to sync in both directions via DavX5, so the
server is obviously not totally borked in terms of syncing.  So some
aspect of the org-caldav-sync seems to be hitting the problem.

-- 
This signature is currently under construction.


  reply	other threads:[~2020-05-12 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12  7:29 org-caldav-sync hanging Loris Bennett
2020-05-12 10:33 ` Eric S Fraga
2020-05-12 10:59   ` Loris Bennett [this message]
2020-05-12 14:59     ` Garjola Dindi
2020-05-18  8:47       ` Loris Bennett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873685qv05.fsf@hornfels.zedat.fu-berlin.de \
    --to=loris.bennett@fu-berlin.de \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).