Re: tar: Can't translate pathname 'xxx' to UTF-8

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

> Date: Fri, 25 Sep 2026 22:38:28 +0100
> From: Jonathan Perkin <jperkin%pkgsrc.org@localhost>
> 
> * On 2026-09-25 at 21:19 BST, Taylor R Campbell wrote:
> 
> >Caveat: The bsdtar shipped in NetBSD _base_ is happy to do iconv
> >conversions (if NetBSD knows about them).  The bsdtar shipped in
> >_pkgsrc_ is built without any iconv support, because it is a
> >statically linked bootstrap thing and iconv complicates the bootstrap
> >story yadda yadda yadda.
> 
> If building archivers/bsdtar with iconv support helps avoid some of 
> these issues then we should just do that.  It's not in the core 
> bootstrap path - it's only pulled in as a post-bootstrap dependency if a 
> package declares EXTRACT_USING=bsdtar and the host system does not 
> provide one.

bsdtar may not be, but libarchive is as a mandatory dependency of
pkg_install, and we only have one way to build libarchive at the
moment which both bootstrap and pkg_install and archivers/bsdtar all
share, as far as I'm aware.

If want to split archivers/libarchive into archivers/libarchive-boot
and archivers/libarchive or otherwise disentangle the
libarchive-3.8.9.tgz package from the pkg_install bootstrap, maybe
that would resolve it.

(It would also not resolve anything with archives having invalid
UTF-8, archives having other data that can't be converted to UTF-8, or
attempts to extract in a locale without UTF-8 ctype.  But maybe those
don't matter; maybe all the real issues are just with trying to
extract UTF-8 paths under LC_CTYPE=C.)