https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238568
--- Comment #6 from Vlad Biley ---
This issue seems stale, but I've just run into it. That tar behavior causes me
some confusion. I will run it with LANG=C.UTF-8, it seems then it works
correctly, preserving names and without warnings.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238568
--- Comment #5 from a...@playground.ru ---
The filesystem has no internal charset so it is weird to do charset
translations from no-charset (= BINARY) to any explicit charset.
Also it is not good that resulting archive somehow dependent on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238568
--- Comment #4 from Conrad Meyer ---
(Prior to FreeBSD 10, the default tar format was likely the older "ustar"
instead of "pax".)
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238568
--- Comment #3 from Conrad Meyer ---
This is specified by POSIX' pax:
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/pax.html
"If there is a hdrcharset extended header in effect for a file, the value field
for any gname, linkp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238568
--- Comment #1 from a...@playground.ru ---
This started happening in FreeBSD 10.
Before that tar never tried to do charset translations by any means.
--- Comment #2 from Conrad Meyer ---
It's a non-fatal warning that changes the exit statu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238568
--- Comment #1 from a...@playground.ru ---
This started happening in FreeBSD 10.
Before that tar never tried to do charset translations by any means.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238568
Bug ID: 238568
Summary: tar filenames encoding problem
Product: Base System
Version: 11.2-STABLE
Hardware: Any
OS: Any
Status: New
Severity: Affects
