Re: [Rpm-maint] [rpm-software-management/rpm] rpmug: Make sure /etc/passwd and /etc/group from chroot are used (PR #2480)

2023-04-14 Thread Daan De Meyer
Rewriting the f-variants is a bit more work than I'm willing to spend on this. I realized that I can simply install in two steps, first to install `setup` which provides /etc/passwd and then to install the rest. For the second step, I mount over passwd from the root over passwd from the host and

Re: [Rpm-maint] [rpm-software-management/rpm] rpmug: Make sure /etc/passwd and /etc/group from chroot are used (PR #2480)

2023-04-14 Thread Daan De Meyer
Closed #2480. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/pull/2480#event-9005424815 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-

Re: [Rpm-maint] [rpm-software-management/rpm] rpmug: Make sure /etc/passwd and /etc/group from chroot are used (PR #2480)

2023-04-12 Thread Panu Matilainen
Thanks for looking into this! For rpmugUname() and rpmugGname(), an important side-effect of the caching is the string storage. That seems necessary to maintain, returning a pointer that could be invalidated by an unrelated call to the getpw*() etc family of calls doesn't cut it. Also, the cach

[Rpm-maint] [rpm-software-management/rpm] rpmug: Make sure /etc/passwd and /etc/group from chroot are used (PR #2480)

2023-04-12 Thread Daan De Meyer
If we chroot(), getpwnam() and friends will still return results from the host /etc/passwd and related files because of caching. We can't flush the caches ourselves, so instead, let's open /etc/passwd ourselves in the chroot and use fgetpwent() and friends to read from it. This makes sure we avo