From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pmg-devel@lists.proxmox.com, Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: applied: [PATCH pmg-api] d/postinst: do not error out on chown/chmod /var/spool/pmg/
Date: Wed, 15 Jul 2026 15:10:11 +0200 [thread overview]
Message-ID: <178412100047.1678796.13340561470527773108.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260622082137.2431-1-s.ivanov@proxmox.com>
On Mon, 22 Jun 2026 10:21:17 +0200, Stoiko Ivanov wrote:
> When /var/spool/pmg is a dedicated mountpoint on an unpriviledged
> container, its `.lost+found` is not writeable by root inside the
> container.
>
> In this case - it makes sense to not cause postinst to error-out, as
> the failing change of mode/ownership is not problematic.
>
> [...]
Applied, thanks!
[1/1] d/postinst: do not error out on chown/chmod /var/spool/pmg/
commit: 138e1574d91ff91f32a8d14690e783f8a2913986
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
prev parent reply other threads:[~2026-07-15 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 8:21 [PATCH pmg-api] d/postinst: do not error out on chown/chmod /var/spool/pmg/ Stoiko Ivanov
2026-07-14 9:30 ` Dominik Csapak
2026-07-15 13:10 ` Fabian Grünbichler [this message]
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=178412100047.1678796.13340561470527773108.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/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