* On 2026-09-25 at 20:11 BST, Taylor R Campbell wrote:
Date: Fri, 25 Sep 2026 20:43:26 +0200 From: Manuel Bouyer <bouyer%antioche.eu.org@localhost> I think I've seen comments about a similar issue before. What would be the correct way to fix this ?What platform is this on and in what stage of the build did it happen? You may be thinking of this thread, and of its resolution of setting LC_CTYPE.UTF-8 in EXTRACT_ENV (on NetBSD), after I fixed a bug in NetBSD's libarchive/bsdtar so that it would not silently suppress an underlying error:
FWIW this is still the cause of the top breakage on at least SmartOS, and presumably will be the same on any platform that doesn't ship a native bsdtar without this handling.
I don't really understand why it doesn't JFDI and extract the bytes, and am curious about what happens if we kludge LC_CTYPE to UTF-8 and then have an archive which contains filenames that aren't valid UTF-8?
Why is this suddenly a problem now? Why does using GNU tar work fine?I'd rather the EXTRACT_USING=bsdtar stuff was handled differently, it's frustrating having to pull in what appears on the surface to be a broken bsdtar on systems where the native tar would not have these issues.
I'm sure there are complicated reasons why these failures are correct, but the current situation sucks.
-- Jonathan Perkin pkgsrc.smartos.org Open Source Complete Cloud www.tritondatacenter.com