On Thu, Dec 20, 2018 at 09:51:46PM +0100, Jonas Smedegaard wrote: > I suspect you misunderstand changelog.Debian Yes, I did misunderstand it.
> The place to learn what happened on your host is /var/log/apt/* and > /var/log/dpkg* (which you can access but not me - that's why I ask). I wasn't aware of the existence of /var/log/dpkg.log. That's a good thing to know. According to this log file, my previous version was 1.1.6-4. When I upgraded to 2.1.10-1, I think the only warning I saw was about the /etc/default/radicale file. > If export routine is broken then indeed it is broken. I see no reason > why it should be broken in this particular way, though. But thanks for > sharing your concern. What I meant was that if the export routine doesn't use the name of the old iCalendar file for the new directory, then the URL of the calendar – which is used by the client – changes as well. But I don't know if the export routine breaks configuration in such a way since it failed with a "ERROR: Failed to find child collections of '<path_to_iCalendar_file>': generator raised StopIteration" message. When it happened, I was so bored that instead of trying harder the export, I did the import in Lightning. -- Bernard Massot
