From: teldra <teldra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] radicale: update to 3.1.5.
Date: Mon, 14 Mar 2022 16:44:11 +0100 [thread overview]
Message-ID: <20220314154411.DfhpzbPNwDtgQ5UkmG5LnvEq8W1ImY1xjrM4qis4rKA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35726@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
There is an updated pull request by teldra against master on the void-packages repository
https://github.com/teldra/void-packages update-radicale
https://github.com/void-linux/void-packages/pull/35726
radicale: update to 3.1.5.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/35726.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-radicale-35726.patch --]
[-- Type: text/x-diff, Size: 1666 bytes --]
From c46331b374dbbadfa5820eb892a8ff30033e4a26 Mon Sep 17 00:00:00 2001
From: teldra <teldra@rotce.de>
Date: Mon, 21 Feb 2022 10:17:21 +0100
Subject: [PATCH] radicale: update to 3.1.5.
- remove conf file entry, because it changes filerights after updates
- add README.voidlinux to briefly describe, how to add this file
---
srcpkgs/radicale/template | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/radicale/template b/srcpkgs/radicale/template
index 8d81e3b61304..4591de6cac6e 100644
--- a/srcpkgs/radicale/template
+++ b/srcpkgs/radicale/template
@@ -1,6 +1,6 @@
# Template file for 'radicale'
pkgname=radicale
-version=3.1.4
+version=3.1.5
revision=1
wrksrc="Radicale-${version}"
build_style=python3-module
@@ -14,11 +14,10 @@ license="GPL-3.0-or-later"
homepage="https://radicale.org"
changelog="https://github.com/Kozea/Radicale/blob/master/CHANGELOG.md"
distfiles="https://github.com/Kozea/Radicale/archive/refs/tags/v${version}.tar.gz"
-checksum=7658db3bb78ddb5934b573a875d1ef3ca6cfe932a4a15dc0c781126bea7f41c1
+checksum=1d631d0c0efd049c05fb32876d8e4f5662df4fa91f8aa6f52a994608d9a3e12d
conf_files="
/etc/radicale/config
/etc/radicale/rights
- /etc/radicale/users
/etc/sv/radicale/log/run"
make_dirs="
/etc/radicale 755 root root
@@ -33,11 +32,11 @@ replaces="radicale2<3.0.6"
post_install() {
vinstall config 644 etc/radicale/
vinstall rights 640 etc/radicale/
- vinstall /dev/null 640 etc/radicale users
vinstall config 644 usr/share/examples/radicale
vinstall radicale.wsgi 644 usr/share/radicale
vsv radicale
vdoc README.md
+ vdoc "${FILESDIR}/README.voidlinux"
}
radicale2_package() {
next prev parent reply other threads:[~2022-03-14 15:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 9:49 [PR PATCH] " teldra
2022-02-21 13:46 ` Anachron
2022-03-13 22:36 ` [PR REVIEW] " paper42
2022-03-14 15:44 ` teldra [this message]
2022-03-14 15:46 ` [PR PATCH] [Updated] " teldra
2022-03-14 15:47 ` [PR REVIEW] " teldra
2022-03-14 15:48 ` [PR PATCH] [Updated] " teldra
2022-03-31 23:14 ` teldra
2022-03-31 23:15 ` teldra
2022-04-02 15:37 ` [PR PATCH] [Merged]: " leahneukirchen
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=20220314154411.DfhpzbPNwDtgQ5UkmG5LnvEq8W1ImY1xjrM4qis4rKA@z \
--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).