From: fanyx <fanyx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] radicale: fix permissions post-install
Date: Sun, 01 Oct 2023 21:52:23 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46357@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 377 bytes --]
There is a new pull request by fanyx against master on the void-packages repository
https://github.com/fanyx/void-packages fix/radicale
https://github.com/void-linux/void-packages/pull/46357
radicale: fix permissions post-install
Picks up #39973
Also add `_` prefix to system user
A patch file from https://github.com/void-linux/void-packages/pull/46357.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fix/radicale-46357.patch --]
[-- Type: text/x-diff, Size: 2459 bytes --]
From 5f0bb42a609d93879e8a2546b807029245abfa35 Mon Sep 17 00:00:00 2001
From: fanyx <fanyx@posteo.net>
Date: Sun, 1 Oct 2023 21:47:46 +0200
Subject: [PATCH] radicale: fix permissions post-install
---
srcpkgs/radicale/INSTALL | 11 +++++++++++
srcpkgs/radicale/files/radicale/run | 2 +-
srcpkgs/radicale/template | 13 ++++++-------
3 files changed, 18 insertions(+), 8 deletions(-)
create mode 100644 srcpkgs/radicale/INSTALL
diff --git a/srcpkgs/radicale/INSTALL b/srcpkgs/radicale/INSTALL
new file mode 100644
index 0000000000000..830c308f38534
--- /dev/null
+++ b/srcpkgs/radicale/INSTALL
@@ -0,0 +1,11 @@
+# *-*-shell-*-*
+#
+case ${ACTION} in
+post)
+ # fix permissions and owners
+ chown _radicale:_radicale /etc/radicale/config
+ chown _radicale:_radicale /etc/radicale/rights
+ chmod 644 /etc/radicale/config
+ chmod 640 /etc/radicale/rights
+ ;;
+esac
diff --git a/srcpkgs/radicale/files/radicale/run b/srcpkgs/radicale/files/radicale/run
index ab664721091e9..f9f20fa972320 100755
--- a/srcpkgs/radicale/files/radicale/run
+++ b/srcpkgs/radicale/files/radicale/run
@@ -1,3 +1,3 @@
#!/bin/sh
exec 2>&1
-exec chpst -u radicale radicale -C /etc/radicale/config
+exec chpst -u _radicale _radicale -C /etc/radicale/config
diff --git a/srcpkgs/radicale/template b/srcpkgs/radicale/template
index a6fabe065463c..b5a0cb3a0a33f 100644
--- a/srcpkgs/radicale/template
+++ b/srcpkgs/radicale/template
@@ -1,7 +1,7 @@
# Template file for 'radicale'
pkgname=radicale
version=3.1.8
-revision=3
+revision=4
build_style=python3-module
hostmakedepends="python3-setuptools"
depends="python3-vobject python3-dateutil python3-passlib python3-bcrypt
@@ -22,11 +22,11 @@ conf_files="
make_dirs="
/etc/radicale 755 root root
/usr/share/radicale/ 755 root root
- /var/log/radicale/ 700 root root
- /var/lib/radicale 750 radicale radicale"
-system_accounts="radicale"
-radicale_homedir="/var/lib/radicale"
-radicale_descr="Radicale user"
+ /var/log/radicale/ 750 _radicale _radicale
+ /var/lib/radicale 750 _radicale _radicale"
+system_accounts="_radicale"
+_radicale_homedir="/var/lib/radicale"
+_radicale_descr="Radicale user"
replaces="radicale2<3.0.6"
do_check() {
@@ -38,7 +38,6 @@ do_check() {
post_install() {
vinstall config 644 etc/radicale/
vinstall rights 640 etc/radicale/
- vinstall config 644 usr/share/examples/radicale
vinstall radicale.wsgi 644 usr/share/radicale
vsv radicale
vdoc README.md
next reply other threads:[~2023-10-01 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 19:52 fanyx [this message]
2023-10-01 19:55 ` classabbyamp
2023-10-01 19:56 ` fanyx
2023-10-01 19:58 ` [PR PATCH] [Updated] " fanyx
2023-10-01 20:04 ` [PR REVIEW] " classabbyamp
2023-10-01 20:05 ` fanyx
2023-10-01 20:08 ` [PR PATCH] [Updated] " fanyx
2023-12-12 11:54 ` fanyx
2023-12-12 12:00 ` fanyx
2024-03-12 1:44 ` radicale: fix permissions post-install, remove deprecated pytests github-actions
2024-03-23 13:53 ` [PR PATCH] [Closed]: " fanyx
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46357@inbox.vuxu.org \
--to=fanyx@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).