Your message dated Thu, 07 Feb 2019 02:46:57 +0000 with message-id <e1grzil-000by5...@fasolo.debian.org> and subject line Bug#916921: fixed in radicale 2.1.11-4 has caused the Debian Bug report #916921, regarding radicale: upgrade to 2.x breaks compatibility with 1.x without any prior warning to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 916921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: radicale Version: 2.1.11-2 Severity: important On Debian unstable, Radicale was just upgraded from 1.x to 2.x. Only after upgrading did I realize that my calendars were not available any more. As stated on https://radicale.org/1to2/, upgrade to 2.x forces you to use Python 3, and thus to upgrade mod_wsgi as well. I was using Python 2 version of mod_wsgi only because it was the default version and it wasn't causing any problem (Radicale was my only WSGI application). Moreover, Radicale 2.x can't even use 1.x data files. You must export your files *before* upgrading. The Debian package silently ignores all these issues. I think there should be warning messages and a ad hoc prerm kind of script. By the way, installing Radicale 1.x and using --export-storage didn't even work for me. It probably had something to do with my using single iCalendar file calendars and my /etc/radicale/config was not configured to support this anymore. Just in case someone with the same problem as me read this message, here is how I fixed all this mess. For each calendar, I unsubscribed in Lightning, created a new calendar through the web interface, renamed the created directory in /var/lib/radicale/collections/collection-root/<username>/ (for some reason, Radicale uses random hexadecimal strings instead of calendar title, whereas it is the actual string you have to type in your CalDAV client), subscribed the newly created calendar in Lightning, and imported the old iCalendar file from /var/lib/radicale/collections/<username>/ using the "Events and Tasks->Import" Lightning menu. It actually was more straightforward than using the whole export storage thing. After doing that my other CalDAV clients worked without needing to be reconfigured. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: armel Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages radicale depends on: ii adduser 3.118 ii init-system-helpers 1.56+nmu1 ii lsb-base 10.2018112800 ii python3 3.7.1-3 ii python3-radicale 2.1.11-2 Versions of packages radicale recommends: ii ssl-cert 1.0.39 Versions of packages radicale suggests: ii apache2 2.4.37-1 ii apache2-utils 2.4.37-1 pn libapache2-mod-proxy-uwsgi <none> pn python3-bcrypt <none> pn python3-passlib <none> pn uwsgi <none> -- Configuration Files: /etc/radicale/config changed [not included] -- debconf-show failed
--- End Message ---
--- Begin Message ---Source: radicale Source-Version: 2.1.11-4 We believe that the bug you reported is fixed in the latest version of radicale, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 916...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard <d...@jones.dk> (supplier of updated radicale package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Thu, 07 Feb 2019 02:28:00 +0100 Source: radicale Architecture: source Version: 2.1.11-4 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard <d...@jones.dk> Changed-By: Jonas Smedegaard <d...@jones.dk> Closes: 916921 Changes: radicale (2.1.11-4) unstable; urgency=medium . * Add NEWS entry about incompatible changes to storage format. Closes: Bug#916921. Thanks to Bernard Massot. Checksums-Sha1: 714d7de1aae6cb30851bd6e864693e37e1e72e75 2293 radicale_2.1.11-4.dsc 42037a7c0748fae1e9ed92cae2d30dd412c4731c 20892 radicale_2.1.11-4.debian.tar.xz 6135ccacef5dd2b0e466654e6c7a2b9be78437ad 6588 radicale_2.1.11-4_amd64.buildinfo Checksums-Sha256: 303140c592e7c012aa0f7a4daeff41dec5dac3d625f2fa40015dbc297d18deb8 2293 radicale_2.1.11-4.dsc 2d969f54d3a6430185b30dfc55f0c88518f3df924ddada6b359035ee2960bb83 20892 radicale_2.1.11-4.debian.tar.xz 08e3bc5eeb971d244765d00b27f3c67c07911dbff1a9bd127cfa7c9f582e2c24 6588 radicale_2.1.11-4_amd64.buildinfo Files: b5e292b097f4a06c6ea4d89351904227 2293 web optional radicale_2.1.11-4.dsc ec4d064dc6a0565fd098bba2ec5de737 20892 web optional radicale_2.1.11-4.debian.tar.xz 9c60c554da7a0d6b78fd9231ecfdc7d9 6588 web optional radicale_2.1.11-4_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxbjosACgkQLHwxRsGg ASF5ahAAji22Uyq4zndQYKcUkwVUaq95tabIDPBj9pC6iXxyxMav0QCtmiaogjbj LxlfL7b3CmydTZk7rCrUF4gr1dJAXRGBwNKwxTqqwyX4gDa+fvcpZlZi7LYJGkCQ YaHkRIze8TaVz0IHhH+Otnh7nqe7/jeJ8bVlp28R4VjJxiDS4BkkK/Sm7ZlNaOgU CWn9hT4WHsD/R7015UOiQNMBCJWowSBlsEOhr4Sn2XXHtBhS+QKmycEmfiGgt7TA VnwVm3Rp4HkDFI4mcgqF5aVIZnn+9zt4xvjSV9puJJsMuX/hcZspv/3AU0CYGUp/ DfGuGeKzNkTe0AeRUZPwuQxFV4Qw/qllkruapJPWZjA9VZUEXxGLGK1R8QFEsZRH q0QXmFr85bQB7Iy0DRdhdAizT507bw+1Ebzz8FAPnetxuB0lNFIKKfPlyDirvfiI xpl2JdQOxEM70BHtzEHsj0ScJOILAm0T7ihulEqwOVkALXtfdP5aSql27/DmH3LT 4j9Vwlw/+s6cvG40R7E/7qTFpJmERqL+PhglvHfdm62H58N7T1MurwKzymDxIWFg P6LWxbANrdTY43lxgx9JDxua1sVQp940VI4pSX0MoyIWhrQQwDi5wMmu4+I6JxAW 6XfwK6ukT9aHalzzrl3JaC2FnGOC1nZEDLYiXNXFEdvAUOsVxoU= =2lxm -----END PGP SIGNATURE-----
--- End Message ---
