From: Christopher Head <gentoo-dev@chead.ca>
To: gentoo-dev@lists.gentoo.org
Cc: pr@gentoo.org
Subject: [gentoo-dev] News item for Radicale upgrade
Date: Thu, 1 Mar 2018 21:49:44 -0800 [thread overview]
Message-ID: <20180301214944.07c5ab83@amdahl.home.chead.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]
Hello,
I have filed a pull request
<https://github.com/gentoo/gentoo/pull/7274> to add Radicale 2.1.8 to
the tree. Migrating from Radicale 1 to 2 requires running a database
export command using Radicale 1, i.e. *before* upgrading, as Radicale 2
can’t read version 1’s storage format. Please see below my proposed
news item to go along with this version bump. Note that I am not a
developer and am therefore unable to commit this myself; I would
appreciate that it be reviewed and then whoever accepts my pull request
also add this news item at the same time. Because of this, I have set
the Posted date to today, as I can’t predict when it will actually be
posted; I ask that the committer please revise the date accordingly.
Thank you!
Title: Radicale 2 requires pre-install migration
Author: Christopher Head <chead@chead.ca>
Posted: 2018-03-01
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.
Please see the Radicale migration guide for more information:
http://radicale.org/1to2/
--
Christopher Head
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2018-03-02 5:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 5:49 Christopher Head [this message]
2018-03-30 21:50 ` [gentoo-dev] News item for Radicale upgrade Christopher Head
2018-03-30 21:53 ` Christopher Head
2018-03-31 4:54 ` Ulrich Mueller
2018-04-03 6:09 ` Christopher Head
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=20180301214944.07c5ab83@amdahl.home.chead.ca \
--to=gentoo-dev@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