From: teldra <teldra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Radicale update
Date: Wed, 16 Sep 2020 17:28:55 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24944@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
New issue by teldra on void-packages repository
https://github.com/void-linux/void-packages/issues/24944
Description:
We have `radicale` which is superseded by `radicale2` and their db seem to be incompatible. (Thats the reason, why `radicale2` was introduced.) Now there is `radicale-3.x` released and I wonder, if I should just update `radicale` or `radicale2` to `radicale-3.x` or introduce `radicale3`.
The databases of `radicale2` and `radicale3` are compatible (tested) nut user needs to manage some changes to its configfile. (<https://github.com/Kozea/Radicale/blob/3.0.x/NEWS.md#upgrade-checklist>). I don't know, if radicale-1.x or radicale-2.x will be updated in the future.
What is best practice here?
next reply other threads:[~2020-09-16 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 15:28 teldra [this message]
2020-09-16 16:32 ` teldra
2020-09-16 16:32 ` [ISSUE] [CLOSED] " teldra
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24944@inbox.vuxu.org \
--to=teldra@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).