> Commit
> [f9c7b53](https://github.com/rpm-software-management/rpm/commit/f9c7b53f50adc129baee809692d4c80b3bd15432)
> is supposed to be a no-op, so if that is the thing changing behavior then we
> need to look at it, I don't remember any intentional change to this effect
> anyway. That
Oh, right. The patch does only move the `rpmugInit` call to later. I first
thought it now does that whenever entering the chroot and was wondering why the
commit message is more vocal about that.
I still have this vivid memory of rpm no longer using the the files from
outside the chroot. But I
Commit f9c7b53 is supposed to be a no-op, so if that is the thing changing
behavior then we need to look at it, I don't remember any intentional change to
this effect anyway. That doesn't change the fact that rpm cannot bootstrap
user/group info, never could.
--
You are receiving this because
This is caused by RPM no longer using the user and group information from out
side of the change root. Earlier versions were not properly using the inside
files in all cases.
The uid and gid of these files are set before they are moved in place. So the
shadow group does not exist yet. While
There is a package "setup" which contains sceleton files /etc/shadow,
/etc/shadow, /etc/passwd, /etc/group etc.
Files /etc/shadow and /etc/gshadow are owned by root:shadow:
%attr(0440,root,shadow) %config(noreplace,missingok) %{_sysconfdir}/shadow
%attr(0440,root,shadow)
