From: Mathieu Othacehe <m.othacehe@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40955@debbugs.gnu.org
Subject: [bug#40955] [PATCH 2/5] build: install: Ignore chown exceptions.
Date: Tue, 05 May 2020 15:42:33 +0200 [thread overview]
Message-ID: <87y2q6cxbq.fsf@gmail.com> (raw)
In-Reply-To: <87wo5ua8zs.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 02 May 2020 13:09:43 +0200")
Hello Ludo,
Thanks for reviewing :)
> Or perhaps that’s still not helpful but we instead need a guarantee
> elsewhere that the UID/GID is going to be honored, perhaps by calling:
>
> (evaluate-populate-directive … #:default-gid 0 #:default-uid 0)
>
> and have it ignore chown when it matches #:default-uid and
> #:default-gid.
This seems like a good idea. This way, 'chown' is only applied if the
requested uid/gid doesn't match the default one.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-05-05 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 8:38 [bug#40955] [PATCH 0/5] Add new image API Mathieu Othacehe
2020-04-29 8:47 ` [bug#40955] [PATCH 1/5] build: store-copy: Export file-size procedure Mathieu Othacehe
2020-04-29 8:47 ` [bug#40955] [PATCH 2/5] build: install: Ignore chown exceptions Mathieu Othacehe
2020-05-02 11:09 ` Ludovic Courtès
2020-05-05 13:42 ` Mathieu Othacehe [this message]
2020-04-29 8:47 ` [bug#40955] [PATCH 3/5] build: bootloader: Add install-efi procedure Mathieu Othacehe
2020-05-02 12:16 ` Ludovic Courtès
2020-05-05 13:43 ` Mathieu Othacehe
2020-04-29 8:47 ` [bug#40955] [PATCH 4/5] image: Add a new API Mathieu Othacehe
2020-05-02 12:50 ` Ludovic Courtès
2020-05-05 13:52 ` Mathieu Othacehe
2020-05-02 13:02 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-05 14:12 ` Mathieu Othacehe
2020-04-29 8:47 ` [bug#40955] [PATCH 5/5] vm: Remove obsolete procedures Mathieu Othacehe
2020-05-02 12:52 ` Ludovic Courtès
2020-05-05 14:02 ` Mathieu Othacehe
2020-05-05 14:16 ` bug#40955: " Mathieu Othacehe
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2q6cxbq.fsf@gmail.com \
--to=m.othacehe@gmail.com \
--cc=40955@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).