Bug 2000477

This issue actually comes from systemd and its tmpfiles tmpfiles.d/var.conf. It resets ownership and permissions for /var/log/lastlog as well as for /var/log/btmp (so the latter become inconsistent with what is specified in the %files section in systemd.spec).

@jamacku please, how exactly is necessary to change util-linux.spec to be compatible with recent setup and systems changes?

Now there is 

%install
touch ${RPM_BUILD_ROOT}/var/log/lastlog
chmod 0644 ${RPM_BUILD_ROOT}/var/log/lastlog

%post           
# only for minimal buildroots without /var/log
[ -d /var/log ] || mkdir -p /var/log
touch /var/log/lastlog
chown root:root /var/log/lastlog
chmod 0644 /var/log/lastlog
# Fix the file context, do not use restorecon
if [ -x /usr/sbin/selinuxenabled ] && /usr/sbin/selinuxenabled; then
        SECXT=$( /usr/sbin/matchpathcon -n /var/log/lastlog 2> /dev/null )
        if [ -n "$SECXT" ]; then
                # Selinux enabled, but without policy? It's true for buildroots
                # without selinux stuff on host machine with enabled selinux.
                # We don't want to use any RPM dependence on selinux policy for
                # matchpathcon(2). SELinux policy should be optional.
                /usr/bin/chcon "$SECXT"  /var/log/lastlog >/dev/null 2>&1 || :
        fi      
fi              

%files
%ghost %attr(0644,root,root) %verify(not md5 size mtime) /var/log/lastlog

@kzak See bug 2044592.

@kzak based on @zjedrzej PR https://src.fedoraproject.org/rpms/util-linux/pull-request/10 I suppose, that change in util-linux spec file is required.

(In reply to Jan Macku from comment #4)
> @kzak based on @zjedrzej PR
> https://src.fedoraproject.org/rpms/util-linux/pull-request/10 I suppose,
> that change in util-linux spec file is required.

Oops, I've completely missed Zbyszek's PR. Sorry

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: util-linux), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:4082