From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from Ishtar.sc.tlinx.org (ishtar.tlinx.org [173.164.175.65]) by sourceware.org (Postfix) with ESMTPS id E89833857C75 for ; Sat, 19 Jun 2021 13:29:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E89833857C75 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=tlinx.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tlinx.org Received: from [192.168.3.12] (Athenae [192.168.3.12]) by Ishtar.sc.tlinx.org (8.14.7/8.14.4/SuSE Linux 0.8) with ESMTP id 15JDT9eS027961; Sat, 19 Jun 2021 06:29:12 -0700 Message-ID: <60CDF106.6030907@tlinx.org> Date: Sat, 19 Jun 2021 06:28:38 -0700 From: L A Walsh User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Achim Gratz CC: cygwin@cygwin.com Subject: Re: bug in cygwin tar reading unexpected input(s)... References: <60C82AAB.1090901@tlinx.org> <87im2dk9mf.fsf@Rainer.invalid> In-Reply-To: <87im2dk9mf.fsf@Rainer.invalid> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jun 2021 13:29:37 -0000 On 2021/06/16 10:22, Achim Gratz wrote: > L A Walsh writes: > >> Tar'ing up a windows dir (ProgData) had some unexected failures >> of the sort: >> >> tar: Dbgview: Warning: Cannot llistxattrat: No such file or director, >> >> Where the item listed (Dbgview, ...) is a windows symlink like: >> >> 2019/02/07 22:53 Dbgview [SI\Dbgview.exe], >> and stems from the use of the --xattrs switch. >> > > Hmm. Looks like some of the symlink / attrs content is taking a route > that doesn't deal correctly with '\' as a path separator. Which isn't > too terribly surprising in a way, but it would still be useful to find > out where. Can you run (a pared down) example in strace and show the > result? > ---- Interesting diagnosis. Won't know if I can do so until I've tried. Should be _able_ to setup a test case, will have to try it and see. Thanks for the exact diagnosis of what's needed, and next step! :-) Linda So far, have been busy w/other things, like reinstalling my OS....but will try to get back to this.. tnx.