Github messages for voidlinux
 help / color / mirror / Atom feed
From: teldra <teldra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] radicale: fixes and cleanup
Date: Mon, 14 Nov 2022 14:22:03 +0100	[thread overview]
Message-ID: <20221114132203.aKwY3fzuwSLwreGCGcNqmFDJ6FxNbIy5YPjBFoOTvZU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39973@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1319 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/39973

radicale: fixes and cleanup
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**
should fix https://github.com/void-linux/void-packages/issues/38923

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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/39973.patch is attached

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

From 041a6aa7b29ed0ae9dace65cd458ad8234020c2a Mon Sep 17 00:00:00 2001
From: teldra <teldra@rotce.de>
Date: Sat, 15 Oct 2022 22:56:04 +0200
Subject: [PATCH] radicale: fixes and cleanup

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

diff --git a/srcpkgs/radicale/template b/srcpkgs/radicale/template
index 62e0125da827..2ecfa2988390 100644
--- a/srcpkgs/radicale/template
+++ b/srcpkgs/radicale/template
@@ -1,7 +1,7 @@
 # Template file for 'radicale'
 pkgname=radicale
 version=3.1.8
-revision=2
+revision=3
 build_style=python3-module
 hostmakedepends="python3-setuptools"
 depends="python3-vobject python3-dateutil python3-passlib python3-bcrypt
@@ -36,9 +36,10 @@ do_check() {
 }
 
 post_install() {
-	vinstall config 644 etc/radicale/
-	vinstall rights 640 etc/radicale/
-	vinstall config 644 usr/share/examples/radicale
+	vinstall config 755 etc/radicale/
+	vinstall rights 755 etc/radicale/
+	vsconf config
+	vsconf rights
 	vinstall radicale.wsgi 644 usr/share/radicale
 	vsv radicale
 	vdoc README.md

  parent reply	other threads:[~2022-11-14 13:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15 20:57 [PR PATCH] " teldra
2022-10-16  0:32 ` fanyx
2022-10-16  9:08 ` [PR PATCH] [Updated] " teldra
2022-10-16  9:09 ` teldra
2022-11-13 10:50 ` fanyx
2022-11-13 11:02 ` [PR PATCH] [Updated] " teldra
2022-11-14 13:22 ` teldra [this message]
2022-11-14 13:24 ` teldra
2022-11-14 15:23 ` fanyx
2023-02-10 12:23 ` [PR PATCH] [Updated] " teldra
2023-02-10 12:26 ` teldra
2023-02-10 12:31 ` teldra
2023-02-10 15:44 ` classabbyamp
2023-02-10 16:27 ` [PR PATCH] [Updated] " teldra
2023-02-10 16:30 ` teldra
2023-02-10 18:02 ` classabbyamp
2023-02-10 21:19 ` [PR PATCH] [Updated] " teldra
2023-02-10 21:27 ` teldra
2023-02-11  0:56 ` classabbyamp
2023-05-12  1:50 ` github-actions
2023-05-26  1:53 ` [PR PATCH] [Closed]: " github-actions

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=20221114132203.aKwY3fzuwSLwreGCGcNqmFDJ6FxNbIy5YPjBFoOTvZU@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).