From: lemmi <lemmi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] radicale: owner mismatch for config and runit service
Date: Fri, 26 Aug 2022 16:45:14 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38923@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
New issue by lemmi on void-packages repository
https://github.com/void-linux/void-packages/issues/38923
Description:
### Is this a new report?
Yes
### System Info
Void 5.18.19_1 x86_64-musl GenuineIntel/KVM uptodate rFF
### Package(s) Affected
radicale-3.1.8_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
Radicale continues to work after an update or install without a `chown radicale:radicale /etc/radicale/*`
### Actual behaviour
`xbps-install` reset the owner in `/etc/radicale/*` to `root:root`. Together with the supplied permission, `radicale` started via the `runit` service isn't allowed to read the config and fails.
### Steps to reproduce
1. Install or update radicale
2. Use the provided runit service
3. breaks
next reply other threads:[~2022-08-26 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 14:45 lemmi [this message]
2022-08-26 14:49 ` lemmi
2022-10-04 8:19 ` teldra
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-38923@inbox.vuxu.org \
--to=lemmi@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).