Your message dated Wed, 23 Jan 2019 15:07:16 +0100
with message-id <154825243625.5603.3799198324999111...@auryn.jones.dk>
and subject line Radicale 2.x need no migration path to itself
has caused the Debian Bug report #864746,
regarding radicale: Radicale 1.1.3 required to migrate data to Radicale 2
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.)
--
864746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: radicale
Version: 1.1.1+20160115
Severity: grave
Justification: renders package unusable
Dear Maintainer,
according to the radicale 1 to 2 migration guide http://radicale.org/1to2/
"Calendars and address books are stored in a different way between 1.x.x and
2.0.x versions. Launching 2.0.x without migrating your collections first will
not work, Radicale won’t be able to read your previous data."
"To migrate data to Radicale 2.0.x the command line argument --export-storage
was added to Radicale 1.1.3."
As Radicale 1.1.3 is currently the newest release of the Radicale 1.1.x
branch, it is the ownly Radicale release providing the ability to
convert existing data stored in radicale installations to the format
required by Radicale 2.x.x.
Currently, Radicale 1.1.3 is not available as Debian package.
To enable continued use of the Radicale package by Debian users in the future
2.x.x releases (already in experimental), I kindly ask Radicale 1.1.3 to
be packaged or the --export-storage functionality backported.
This would ensure that this functionality is rolled out once it is
needed when migration to Radicale 2.x.x is required.
Thank you very much.
--- End Message ---
--- Begin Message ---
Version: 2.1.11-1
This bug is about Radicale 1.x failing to upgrade to Radicale 2.x.
Since upstream chose to handle such migration only from Radicale 1.x,
not offer something similar from Radicale 2.x, this bug is fixed with
the release of Radicale 2.x.
If someone feel the need for Radicale 2.x supporting migration of
Radicale 1.x data, then please file a separate bugreport. Such
bugreport should probably be of severity wishlist and tagged upstream.
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
--- End Message ---
