toolchain/59378: mtree set files in daily builds do not always batch

[stephen%borrill.org.uk@localhost]

>Number:         59378
>Category:       toolchain
>Synopsis:       mtree set files in daily builds do not always batch
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    toolchain-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 30 14:35:00 +0000 2025
>Originator:     Stephen Borrill
>Release:        9.4_STABLE
>Organization:
Precedence Technologies Ltd
>Environment:
NetBSD 9.4_STABLE NetBSD 9.4_STABLE (XEN3_DOMU) #0: Sat Oct 26 15:06:49 UTC 2024  mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/xen/compile/XEN3_DOMU amd64

>Description:
Set tarballs include a ./etc/mtree/set.SETNAME file. This should tally with the files in that tarball, but sometimes files differ.

The files that differ always appear to be as follows on netbsd-9:

usr/lib/i386/libkadm5clnt.so.14.0
usr/lib/i386/libkadm5srv.so.15.0

netbsd-10 seems OK from a quick glance.

OK:
https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-10/202504290810Z/amd64/binary/sets/base.tar.xz

Not OK:
https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/202504280110Z/amd64/binary/sets/base.tar.xz
https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/202504242110Z/amd64/binary/sets/base.tar.xz
https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/202504201400Z/amd64/binary/sets/base.tar.xz

>How-To-Repeat:
# ftp https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/202504280110Z/amd64/binary/sets/base.tar.xz
# mkdir dest
# tar -xpzf base.tar.xz -C dest
# mtree -p dest < dest/etc/mtree/set.base

Output shows two mis-matched files:

usr/lib/i386/libkadm5clnt.so.14.0:
        sha256 (0xd6949162c5d1a078d71b5c391df429fe0119c48673df255e3f87c7509b3b0d50, 0x66f1911d5fad9f1b03a0d4100758b9eb0dacb9e8f669cd0426c3746123fd4426)
usr/lib/i386/libkadm5srv.so.15.0:
        sha256 (0x85666f48fb1360300746d3fc6218ca751128840cbe716a9e9f6d70d0836556f2, 0x5ceaa46de43bd45ab72e0516b3b836b9dd066a875e701f3b4514dc0aba44dafe)

>Fix:
Unknown