From: paul via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Nicolas Graves <ngraves@ngraves.fr>, 74967@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#74967: About /etc/subuid and /etc/subgid commits
Date: Thu, 19 Dec 2024 12:32:11 +0100 [thread overview]
Message-ID: <16590227-48f1-474e-bcb7-07011b33fde0@autistici.org> (raw)
In-Reply-To: <871py4qaj9.fsf@ngraves.fr>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
Hi Nicolas, apologies for breaking your system :( Is is possible for you
to try and bisect the history to find the culprit commit?
On 12/19/24 10:36, Nicolas Graves wrote:
> It is a bit circumvoluted, but it worked properly on my side on
> guix@478b9ccea8. Do you see a reason why your patches could break my
> user login?
I'm not sure, I was wondering: do you use/extend the subids-service-type
in your configuration or did you already have manually setup /etc/subuid
or /etc/subgid? Otherwise I'm not sure how it can impact your system, if
you could share even some parts of your operating-system configuration
it would make finding the problem a little easier.
Since you mentioned PAM, these two changes that I authored were recently
merged. Could you try and see whether your system work at commit
a1ecd7f56c4ffadc49d5501a0df7f4c4556120c2 which is the parent of the
first pam change?
Thank you very much :)
[-- Attachment #2: Type: text/html, Size: 1391 bytes --]
next prev parent reply other threads:[~2024-12-19 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 9:36 bug#74967: About /etc/subuid and /etc/subgid commits Nicolas Graves
2024-12-19 11:32 ` paul via Bug reports for GNU Guix [this message]
2024-12-19 11:33 ` paul via Bug reports for GNU Guix
2024-12-21 16:49 ` Nicolas Graves
2024-12-21 17:23 ` paul via Bug reports for GNU Guix
2024-12-21 17:27 ` paul via Bug reports for GNU Guix
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=16590227-48f1-474e-bcb7-07011b33fde0@autistici.org \
--to=bug-guix@gnu.org \
--cc=74967@debbugs.gnu.org \
--cc=goodoldpaul@autistici.org \
--cc=ludo@gnu.org \
--cc=ngraves@ngraves.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.