GNU bug report logs -
#74967
About /etc/subuid and /etc/subgid commits
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 74967 in the body.
You can then email your comments to 74967 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#74967
; Package
guix
.
(Thu, 19 Dec 2024 09:38:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Nicolas Graves <ngraves <at> ngraves.fr>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Thu, 19 Dec 2024 09:38:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi Giacomo,
I noticed the last 11 commits are breaking my peculiar tmpfs root
configuration. More precisely, I have more or less this layout :
tmpfs: /, $HOME
vfat32: /boot/efi
btrfs: /var/guix, /gnu/store, /var/lib, /boot ... + several directories
under $HOME
That means that at startup, I won't have anything in /etc nor $HOME
basically. To deploy guix home properly, I run a pam_exec on login which
symlinks /var/guix/profiles/per-user/${USER}/guix-home && current-guix
to their expected places, then runs the home activation script, and then
logins.
It is a bit circumvoluted, but it worked properly on my side on
guix <at> 478b9ccea8. Do you see a reason why your patches could break my
user login?
I can at least confirm that the $PATH for my $USER is not set properly
after login after these patches, before it was.
--
Best regards,
Nicolas Graves
Information forwarded
to
bug-guix <at> gnu.org
:
bug#74967
; Package
guix
.
(Thu, 19 Dec 2024 11:33:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 74967 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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 <at> 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 :)
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#74967
; Package
guix
.
(Thu, 19 Dec 2024 11:34:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 74967 <at> debbugs.gnu.org (full text, mbox):
I forgot to attach the two PAM related commits, apologies for the noise.
[0]:
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=3eb720bd0b4bab233918f979bb51b58437db06ad
[1]:
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=9411a1495f7cb2b116129a71a1fc1817e962fa5d
Information forwarded
to
bug-guix <at> gnu.org
:
bug#74967
; Package
guix
.
(Sat, 21 Dec 2024 16:50:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 74967 <at> debbugs.gnu.org (full text, mbox):
On 2024-12-19 12:32, paul wrote:
> 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 <at> 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 :)
I've tried bisecting and this time it seems to work properly. I'm not
sure what it was then, but it works fine now!
--
Best regards,
Nicolas Graves
Reply sent
to
paul <goodoldpaul <at> autistici.org>
:
You have taken responsibility.
(Sat, 21 Dec 2024 17:27:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Nicolas Graves <ngraves <at> ngraves.fr>
:
bug acknowledged by developer.
(Sat, 21 Dec 2024 17:27:01 GMT)
Full text and
rfc822 format available.
Message #19 received at 74967-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Nicolas, awesome! I'm closing this.
Cheers,
giacomo
Il 21 dicembre 2024 17:49:08 CET, Nicolas Graves <ngraves <at> ngraves.fr> ha scritto:
>On 2024-12-19 12:32, paul wrote:
>
>> 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 <at> 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 :)
>
>I've tried bisecting and this time it seems to work properly. I'm not
>sure what it was then, but it works fine now!
>
>--
>Best regards,
>Nicolas Graves
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#74967
; Package
guix
.
(Sat, 21 Dec 2024 17:28:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 74967-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hi Nicolas, awesome! I'm closing this.
Cheers,
giacomo
Il 21 dicembre 2024 17:49:08 CET, Nicolas Graves <ngraves <at> ngraves.fr> ha scritto:
>On 2024-12-19 12:32, paul wrote:
>
>> 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 <at> 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 :)
>
>I've tried bisecting and this time it seems to work properly. I'm not
>sure what it was then, but it works fine now!
>
>--
>Best regards,
>Nicolas Graves
[Message part 2 (text/html, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 19 Jan 2025 12:24:11 GMT)
Full text and
rfc822 format available.
This bug report was last modified 148 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.