Re: port-evbarm/58035: [RB] evbarm/earmv6: sshramdisk probably has firmware files in a wrong place

[Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost>]

The following reply was made to PR port-evbarm/58035; it has been noted by GNATS.

From: Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost>
To: Christos Zoulas <christos%zoulas.com@localhost>
Cc: gnats-bugs%netbsd.org@localhost, port-evbarm-maintainer%netbsd.org@localhost,
	gnats-admin%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 16:54:42 +0100

 --tAmVnWIZ6lqEAvSf
 Content-Type: text/plain; charset=utf-8
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Thu, 2024-03-14 11:47:13 -0400, Christos Zoulas <christos%zoulas.com@localhost> wr=
 ote:
 > >  ${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.
 > >=20
 > >  Can you try this change instead?
 > >=20
 > >  -IMAGEPREBUILD=3D3D	${TOOL_PAX} ${PAX_TIMESTAMP} -rw -pp ${DESTDIR}/li=
 bdata/firmware ${WORKDIR}
 > >  +IMAGEPREBUILD=3D3D	(cd ${DESTDIR} && ${TOOL_PAX} ${PAX_TIMESTAMP} -w =
 libdata/firmware) | (cd ${WORKDIR} && ${TOOL_PAX} -r -pp)
 > >=20
 > >  (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.)
 >=20
 > Do we have to use pax? why not use tar -C?
 
 I'm actually quite used to use GNU tar, but TBH `pax` is way better
 specified. Despite being used to a different archiver, I quite think
 that `pax` is the way to go. We'll see where we end with. The hard
 part was to track down there that (kernel-embedded) filesystem came
 =66rom and why it contained my local build pathes. We'll see where we
 end with. The hard part was to track down there that (kernel-embedded)
 filesystem came from and why it contained my local build pathes.
 
 MfG, JBG
 
 --=20
 
 --tAmVnWIZ6lqEAvSf
 Content-Type: application/pgp-signature; name="signature.asc"
 
 -----BEGIN PGP SIGNATURE-----
 
 iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCZfMdwgAKCRAdvV51g5nh
 u5L9AJ0XymSrNGGNvdtAS7zXF9OlqUyKGACfXEVTXVDIu+jF27AGad1+RY7rEiM=
 =QLxR
 -----END PGP SIGNATURE-----
 
 --tAmVnWIZ6lqEAvSf--