The following reply was made to PR port-evbarm/58035; it has been
noted by GNATS.
From: Taylor R Campbell <riastradh%NetBSD.org@localhost>
To: Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost>
Cc: gnats-bugs%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost
Subject: Re: port-evbarm/58035: [RB] evbarm/earmv6: sshramdisk
probably has firmware files in a wrong place
Date: Thu, 14 Mar 2024 15:04:44 +0000
> Date: Thu, 14 Mar 2024 09:00:38 +0000
> From: jbglaw%lug-owl.de@localhost
>=20
> -IMAGEPREBUILD=3D ${TOOL_PAX} ${PAX_TIMESTAMP} -rw -pp
${DESTDIR}/libdata=
/firmware ${WORKDIR}
> +IMAGEPREBUILD=3D (cd ${DESTDIR} && ${TOOL_PAX} ${PAX_TIMESTAMP} -rw
-pp =
libdata/firmware ${WORKDIR})
${WORKDIR} is probably a relative path `work', in which case this will
copy ${DESTDIR}/libdata/firmware to ${DESTDIR}/work/libdata/firmware,
which explains the checkflist errors you saw.
Can you try this change instead?
-IMAGEPREBUILD=3D ${TOOL_PAX} ${PAX_TIMESTAMP} -rw -pp
${DESTDIR}/libdata/f=
irmware ${WORKDIR}
+IMAGEPREBUILD=3D (cd ${DESTDIR} && ${TOOL_PAX} ${PAX_TIMESTAMP} -w
libdata=
/firmware) | (cd ${WORKDIR} && ${TOOL_PAX} -r -pp)
(I don't know if there's a way to convince a single pax -rw instance
to chdir into a source directory before taking relative paths to be
copied into the target.)