From owner-freebsd-questions@freebsd.org Mon Feb 5 18:44:49 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A9F5EE5B60 for ; Mon, 5 Feb 2018 18:44:49 +0000 (UTC) (envelope-from dalescott@shaw.ca) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 31F1F8294D for ; Mon, 5 Feb 2018 18:44:48 +0000 (UTC) (envelope-from dalescott@shaw.ca) Received: from dalet420 ([174.0.43.39]) by shaw.ca with ESMTP id ilktenlPZppe1ilkue556v; Mon, 05 Feb 2018 11:44:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shaw.ca; s=s20150330; t=1517856282; bh=eoxi4FbdfMhIDjCLj/5wlmT2sBQRTP1pUQGXM5saj7M=; h=From:To:References:In-Reply-To:Subject:Date; b=w7DEvosWNtcc779XcV+k8SAlD8pjSRwn01X9Y0o5cox4VNr2+VMEpqfqd0ZEb6wpG 0kllPrb4UciId/bDpqohmTmB77POR+5oX0DCngOuk3rlgSxMOCC5yaMOac38R7NQ+u Ae96JyKarmIKSG8eBrf+/kIV6lTTjHNhrQI/h6iW3+blfIe75ngfRQTCZfejrTqVyz e7T8SHwJtvKmQPEXLirR9Q71qUTs4EH1gAYOp9LU3aoBS0GlG7YgXacYCv3Lp2/ezJ u35FPnj7a9kye0u+l1Ec3MSt3jImnsu2tdkAgAvCAPkGYnk+sepDqvfRzntHUDcE1U w2Jek3b3yiYRA== X-Authority-Analysis: v=2.3 cv=Bo6zP7f5 c=1 sm=1 tr=0 a=TiBur8m8wieNAdBnNdHE5Q==:117 a=TiBur8m8wieNAdBnNdHE5Q==:17 a=kj9zAlcOel0A:10 a=x7bEGLp0ZPQA:10 a=5mcg790sAAAA:8 a=6IL3gGmbkmilRJdfysoA:9 a=CjuIK1q_8ugA:10 a=uQeDYW1NI25gHNlrW_eK:22 From: "Dale Scott" To: "'Christian Weisgerber'" , References: <00d101d399eb$318a7c40$949f74c0$@shaw.ca> In-Reply-To: Subject: RE: freebsd tar fails but not gtar ?!? Date: Mon, 5 Feb 2018 11:44:39 -0700 Message-ID: <00ff01d39eb1$62977750$27c665f0$@shaw.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHONWgI8asJPhL5ttsRNtkHwBXWHQFLyXaQo5aYPbA= Content-Language: en-us X-CMAE-Envelope: MS4wfC/0zOOgf6M+QApTj7KkPe+voGgV9MlDqs9Mva53nCz3bvxp38CeX3vhnOXHWNSSLzlFTugpI1GXb98jU+OTVBUM3TBfRtAVB2qGljS147On7g3vW/4A 82gI2jbEs8pNMPXMGubE8lpGKNmRbLwGjzrCEHzOR3qgPnn9Zhfbi7bJVec8jF85RfWlC/QLCQhL2A== X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Feb 2018 18:44:49 -0000 On 2018-02-03 Christian Weisgerber wrote: > How is it failing? The "Can't translate pathname" messages you quote are > warnings, not errors. > > > It?s been suggested that locale on the system isn?t set correctly. > > Does this sound familiar to anyone? > > Well, when I take a file with UTF-8-encoded non-ASCII characters in its name > and tar it up in the POSIX locale, then I get the same warning. Clearly tar is > trying to normalize path name encodings in some way. Unfortunately this is > not documented. My best guess is that it tries to iconv(3) path names from > the current locale encoding to UTF-8. If the path names are have an invalid > encoding in the current locale, iconv(3) fails, prompting the warning. > > You can simply ignore the warnings. If you extract the archive under the > same conditions as those when you created it, the path names will be just > fine. I'm somewhat ashamed to admit I hadn't actually checked the tar archive. You are correct, the files with warnings are all included. > Or you can make sure that the character encoding in your locale setting > matches those of the file names you are backing up. Most likely something > like LC_CTYPE=en_US.UTF-8 will do. If you don't understand what I'm talking > about, you might want to read up on those topics. I will try your suggestion, and yes, I definitely need to read up on locale setting! :-) Thanks and best regards, Dale --- Dale R. Scott, P.Eng. http://www.dalescott.net