Github messages for voidlinux
 help / color / mirror / Atom feed
From: teldra <>
Subject: [PR PATCH] radicale: update to 3.1.3.
Date: Wed, 26 Jan 2022 22:39:09 +0100	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]

There is a new pull request by teldra against master on the void-packages repository update-radicale

radicale: update to 3.1.3.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR:**briefly**

#### New package
- This new package conforms to the [quality requirements]( **YES**|**NO**

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](
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 is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update-radicale-35253.patch --]
[-- Type: text/x-diff, Size: 1242 bytes --]

From 3daf44653cab5c66441dfc4f6fd165e8677e6893 Mon Sep 17 00:00:00 2001
From: teldra <>
Date: Wed, 26 Jan 2022 22:37:06 +0100
Subject: [PATCH] radicale: update to 3.1.3.

 srcpkgs/radicale/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/radicale/template b/srcpkgs/radicale/template
index bc4fb07f17bd..411986d802d5 100644
--- a/srcpkgs/radicale/template
+++ b/srcpkgs/radicale/template
@@ -1,6 +1,6 @@
 # Template file for 'radicale'
@@ -12,9 +12,9 @@ short_desc="Complete calendar and contact storing and manipulating solution"
 maintainer="teldra <>"

             reply	other threads:[~2022-01-26 21:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 21:39 teldra [this message]
2022-01-28  6:37 ` [PR PATCH] [Merged]: " ericonr

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).