From: Brian Cully via Guix-patches via <guix-patches@gnu.org>
To: 62726@debbugs.gnu.org
Subject: [bug#62726] [PATCH] services: Activate `setuid-program-service-type' in shepherd.
Date: Wed, 07 Jun 2023 08:58:16 -0400 [thread overview]
Message-ID: <874jnja0pj.fsf_-_@psyduck.jhoto.kublai.com> (raw)
In-Reply-To: <c8454cf94417a48931f2583c9af14df83820d354.1680966995.git.bjc@spork.org> (Brian Cully's message of "Sat, 8 Apr 2023 11:16:35 -0400")
I've made some changes to this patch to address some issues:
1) I've added ‘setuid-programs’ as a requirement to various Shepherd
services which need it, such as dbus and pam. I've also added it to
‘user-processes’ as a requirement to catch things we don't specify
explicitly.
2) I've removed (@ (gnu services) setuid-programs), rather than marking
it deprecated. Since the variable name (setuid-programs-service-type)
hasn't changed, normal deprecation doesn't work anyway, and just leads
to annoying double-import warnings.
This probably deserves an entry in ‘guix pull --news’, because, as a
Shepherd service it can now be used by other Shepherd services, and the
module path has changed, which will cause errors for existing system
configurations which use ‘setuid-programs-service-type’. I'm not sure
the best way to go about adding it, though, or if I should let a
committer do it.
next prev parent reply other threads:[~2023-06-07 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 15:09 [bug#62726] services: Activate `setuid-program-service-type' in shepherd Brian Cully via Guix-patches via
2023-04-08 15:16 ` [bug#62726] [PATCH] " Brian Cully via Guix-patches via
2023-06-07 12:58 ` Brian Cully via Guix-patches via [this message]
2023-06-07 12:59 ` [bug#62726] [PATCH v2] " Brian Cully via Guix-patches via
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=874jnja0pj.fsf_-_@psyduck.jhoto.kublai.com \
--to=guix-patches@gnu.org \
--cc=62726@debbugs.gnu.org \
--cc=bjc@spork.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).