From: Christopher Head <chead@chead.ca>
To: gentoo-dev@lists.gentoo.org
Cc: pr@gentoo.org
Subject: Re: [gentoo-dev] News item for Radicale upgrade
Date: Mon, 2 Apr 2018 23:09:58 -0700 [thread overview]
Message-ID: <20180402230958.05364a57@amdahl.home.chead.ca> (raw)
In-Reply-To: <20180301214944.07c5ab83@amdahl.home.chead.ca>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
One more try, this time with the proper revision number.
Title: Radicale 2 requires pre-install migration
Author: Christopher Head <chead@chead.ca>
Posted: 2018-04-02
Revision: 1
News-Item-Format: 2.0
Display-If-Installed: <www-apps/radicale-2
Radicale version 2 uses a new storage format and is not able to read
databases created by version 1. Version 1 releases starting from 1.1.3
include a --export-storage option which can be used to export their
databases in a format that Radicale 2 can use; you must do this before
upgrading to version 2.
If you have kept the Gentoo-default database configuration, this will
work:
1. Stop any running instance of Radicale.
2. Run `radicale --export-storage ~/radicale-exported`.
3. Run `chown -R radicale: ~/radicale-exported`
4. Run `mv /var/lib/radicale /var/lib/radicale.old`.
5. Install Radicale version 2.
6. Run `mv ~/radicale-exported /var/lib/radicale/collections`.
For more details, or if you are have a more complex configuration,
please see the migration guide: http://radicale.org/1to2/
If you do a custom migration, please ensure the database is cleaned out
of /var/lib/radicale, including the hidden .props file.
--
Christopher Head
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2018-04-03 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 5:49 [gentoo-dev] News item for Radicale upgrade Christopher Head
2018-03-30 21:50 ` Christopher Head
2018-03-30 21:53 ` Christopher Head
2018-03-31 4:54 ` Ulrich Mueller
2018-04-03 6:09 ` Christopher Head [this message]
2018-04-08 9:17 ` Michał Górny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180402230958.05364a57@amdahl.home.chead.ca \
--to=chead@chead.ca \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox