From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: etesync-dav upgrade to 0.18.1, new package radicale3
Date: Thu, 23 Jul 2020 16:08:26 +0200 [thread overview]
Message-ID: <20200723140826.DKns6b45w7yVGFXgEOKPguU4ZhtspMVoAHlDY2CnS_4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22810@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/22810#issuecomment-663028529
Comment:
I'm not crazy about splitting to `radicale1` and updating `radicale` to v3. It's not much better than making `radicale3`. An inability to upgrade from the old `radicale` package sounds like an argument for holding local package versions, rather than altering the package tree to accomodate outdated software.
Maybe the `INSTALL.msg` for an updated `radicale` could include some basic instructions for reverting to an old version if that is required by some users:
```
CAUTION: Radicale 3.x is not backwards compatible with Radicale 1.x. If you are upgrading from Radicale 1.x, please consult upstream documentation for information about migrating existing data to the format used by this version.
If you are unable to upgrade but require Radicale 1.x to function, you can install the xtools package and run
xdowngrade /var/cache/xbps/radicale-<version>.<arch>.xbps
xbps-pkgdb -m hold radicale
for your architecture and locally cached version number.
If you do not have a cached version of the package, you can install an unmanaged version with, for example
pip install radicale<2
You may wish to use a virtual environment to isolate pip-installed packages from system-managed packages.
```
next prev parent reply other threads:[~2020-07-23 14:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22810@inbox.vuxu.org>
2020-07-04 12:16 ` ProjectMoon
2020-07-05 18:29 ` Piraty
2020-07-06 14:46 ` ProjectMoon
2020-07-18 0:04 ` CameronNemo
2020-07-18 0:04 ` CameronNemo
2020-07-18 0:05 ` [PR REVIEW] " CameronNemo
2020-07-18 9:38 ` ProjectMoon
2020-07-18 9:59 ` ProjectMoon
2020-07-22 20:31 ` [PR PATCH] [Updated] " ProjectMoon
2020-07-22 20:35 ` ProjectMoon
2020-07-22 20:43 ` [PR REVIEW] " ericonr
2020-07-22 20:43 ` ericonr
2020-07-22 20:43 ` ericonr
2020-07-22 20:43 ` ericonr
2020-07-22 20:44 ` ericonr
2020-07-22 20:49 ` [PR REVIEW] " ProjectMoon
2020-07-22 20:51 ` ProjectMoon
2020-07-22 20:52 ` ericonr
2020-07-22 20:55 ` [PR PATCH] [Updated] " ProjectMoon
2020-07-22 21:00 ` [PR REVIEW] " ericonr
2020-07-22 21:00 ` ericonr
2020-07-22 21:01 ` ericonr
2020-07-23 2:39 ` ahesford
2020-07-23 2:39 ` ahesford
2020-07-23 2:39 ` ahesford
2020-07-23 2:39 ` ahesford
2020-07-23 6:38 ` lemmi
2020-07-23 8:45 ` [PR REVIEW] " ProjectMoon
2020-07-23 8:47 ` ProjectMoon
2020-07-23 8:47 ` ProjectMoon
2020-07-23 14:08 ` ahesford [this message]
2020-07-23 15:50 ` CameronNemo
2020-07-28 18:48 ` [PR PATCH] [Updated] " ProjectMoon
2020-07-28 18:48 ` [PR PATCH] [Closed]: " ProjectMoon
2020-07-28 18:55 ` ProjectMoon
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=20200723140826.DKns6b45w7yVGFXgEOKPguU4ZhtspMVoAHlDY2CnS_4@z \
--to=ahesford@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).