Github messages for voidlinux
 help / color / mirror / Atom feed
From: jason1987d <jason1987d@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] radicale: update to 3.3.1.
Date: Sun, 15 Dec 2024 17:29:10 +0100	[thread overview]
Message-ID: <20241215162910.3630A2E68D@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53225@inbox.vuxu.org>

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

There is an updated pull request by jason1987d against master on the void-packages repository

https://github.com/jason1987d/void-packages radicale
https://github.com/void-linux/void-packages/pull/53225

radicale: update to 3.3.1.
#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architecture, x86_64-libc


A patch file from https://github.com/void-linux/void-packages/pull/53225.patch is attached

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

From 2b65faefb1ecb6d60e6735f4a092f6ce5c64710c Mon Sep 17 00:00:00 2001
From: Jason Elswick <jason@jasondavid.us>
Date: Tue, 26 Nov 2024 10:26:10 -0600
Subject: [PATCH] radicale: update to 3.3.2.

---
 srcpkgs/radicale/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/radicale/template b/srcpkgs/radicale/template
index 69280f239d6f3c..ea8788bb1d76e5 100644
--- a/srcpkgs/radicale/template
+++ b/srcpkgs/radicale/template
@@ -1,6 +1,6 @@
 # Template file for 'radicale'
 pkgname=radicale
-version=3.3.0
+version=3.3.2
 revision=1
 build_style=python3-pep517
 hostmakedepends="python3-setuptools"
@@ -14,7 +14,7 @@ license="GPL-3.0-or-later"
 homepage="https://radicale.org"
 changelog="https://raw.githubusercontent.com/Kozea/Radicale/master/CHANGELOG.md"
 distfiles="https://github.com/Kozea/Radicale/archive/refs/tags/v${version}.tar.gz"
-checksum=7080b96c670b954182202a5d77484d447607cf907b6f6bf4051f257b6d182164
+checksum=d2af06ab88163b1b32a23bee2de7e45c41180a8d296b60a0add41cd9a994f43b
 conf_files="
  /etc/radicale/config
  /etc/radicale/rights"

  reply	other threads:[~2024-12-15 16:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 16:28 [PR PATCH] " jason1987d
2024-12-15 16:29 ` jason1987d [this message]
2025-01-01  3:29 ` [PR PATCH] [Updated] radicale: update to 3.3.2 jason1987d
2025-01-01  3:31 ` radicale: update to 3.3.3 jason1987d
2025-01-01  3:40 ` [PR PATCH] [Updated] " jason1987d
2025-01-01  3:46 ` jason1987d
2025-01-01  3:50 ` jason1987d
2025-01-04 17:47 ` [PR REVIEW] " ahesford
2025-01-04 17:47 ` ahesford
2025-01-04 22:28 ` jason1987d
2025-01-05  3:19 ` ahesford
2025-01-05 15:41 ` jason1987d
2025-01-05 15:44 ` jason1987d
2025-01-05 15:47 ` jason1987d
2025-01-05 18:53 ` [PR PATCH] [Updated] " jason1987d
2025-01-05 18:53 ` jason1987d
2025-01-05 19:23 ` ahesford
2025-01-12  0:41 ` jason1987d
2025-01-12 19:19 ` [PR PATCH] [Updated] " jason1987d
2025-01-12 19:23 ` radicale: update to 3.4.0 jason1987d
2025-01-12 19:23 ` jason1987d
2025-01-12 19:58 ` [PR REVIEW] " ahesford
2025-01-12 20:30 ` [PR PATCH] [Updated] " jason1987d
2025-01-12 20:39 ` [PR PATCH] [Merged]: " ahesford

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=20241215162910.3630A2E68D@inbox.vuxu.org \
    --to=jason1987d@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).