| 1 |
Hello, |
| 2 |
After much discussion on the pull request |
| 3 |
<https://github.com/gentoo/gentoo/pull/7274>, reviewers and I have |
| 4 |
concluded with a new pkg_pretend message, which I would like to use as |
| 5 |
the new news message as well. As before, I ask that the committer of |
| 6 |
that merge request adjust the posted date in this news item and add it |
| 7 |
to the news repo when accepting the PR. Thanks! |
| 8 |
|
| 9 |
Title: Radicale 2 requires pre-install migration |
| 10 |
Author: Christopher Head <chead@×××××.ca> |
| 11 |
Posted: 2018-03-30 |
| 12 |
Revision: 2 |
| 13 |
News-Item-Format: 2.0 |
| 14 |
Display-If-Installed: <www-apps/radicale-2 |
| 15 |
|
| 16 |
Radicale version 2 uses a new storage format and is not able to read |
| 17 |
databases created by version 1. Version 1 releases starting from 1.1.3 |
| 18 |
include a --export-storage option which can be used to export their |
| 19 |
databases in a format that Radicale 2 can use; you must do this before |
| 20 |
upgrading to version 2. |
| 21 |
|
| 22 |
If you have kept the Gentoo-default database configuration, this will |
| 23 |
work: |
| 24 |
1. Stop any running instance of Radicale. |
| 25 |
2. Run `radicale --export-storage ~/radicale-exported`. |
| 26 |
3. Run `chown -R radicale: ~/radicale-exported` |
| 27 |
4. Run `mv /var/lib/radicale /var/lib/radicale.old`. |
| 28 |
5. Install Radicale version 2. |
| 29 |
6. Run `mv ~/radicale-exported /var/lib/radicale/collections`. |
| 30 |
|
| 31 |
For more details, or if you are have a more complex configuration, |
| 32 |
please see the migration guide: http://radicale.org/1to2/ |
| 33 |
If you do a custom migration, please ensure the database is cleaned out |
| 34 |
of /var/lib/radicale, including the hidden .props file. |
| 35 |
-- |
| 36 |
Christopher Head |
Archives