From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Engster Subject: Re: problem with org-caldav and ox-icalendar: UID property wrapping Date: Thu, 05 Jun 2014 22:28:24 +0200 Message-ID: <87fvjjm787.fsf@engster.org> References: <87vbthd6mw.fsf@pinto.chemeng.ucl.ac.uk> <878uqdzj6w.fsf@gmail.com> <87wqdxz5aj.fsf@engster.org> <87oay9n4z2.fsf@engster.org> <874n01ov66.fsf@pinto.chemeng.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54848) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WseHD-0003pk-Bs for emacs-orgmode@gnu.org; Thu, 05 Jun 2014 16:28:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WseH7-00006m-9P for emacs-orgmode@gnu.org; Thu, 05 Jun 2014 16:28:43 -0400 Received: from randomsample.de ([5.45.97.173]:57326) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WseH6-000067-W4 for emacs-orgmode@gnu.org; Thu, 05 Jun 2014 16:28:37 -0400 Received: from dslc-082-083-050-255.pools.arcor-ip.net ([82.83.50.255] helo=spaten) by randomsample.de with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1WseGz-0005tx-W4 for emacs-orgmode@gnu.org; Thu, 05 Jun 2014 22:28:30 +0200 In-Reply-To: <874n01ov66.fsf@pinto.chemeng.ucl.ac.uk> (Eric S. Fraga's message of "Wed, 4 Jun 2014 10:56:01 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Eric S. Fraga writes: > On Tuesday, 3 Jun 2014 at 21:54, David Engster wrote: > > [...] > >> Well, that took a bit longer, but I pushed it now... >> >> -David > > Well, the good news is that you have indeed fixed the problem I noted > about IDs on more than one line. > > The bad news is that other things are now broken. I haven't had time to > totally narrow down was is happening but basically: Yes, I made a stupid mistake. I hope it is fixed now, but it might be necessary to delete the remote calendars and sync anew. Sorry for that. -David