From: L A Walsh <cygwin@tlinx.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: cygwin@cygwin.com
Subject: Re: bug in cygwin tar reading unexpected input(s)...
Date: Sat, 19 Jun 2021 06:28:38 -0700 [thread overview]
Message-ID: <60CDF106.6030907@tlinx.org> (raw)
In-Reply-To: <87im2dk9mf.fsf@Rainer.invalid>
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 <SYMLINK> 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.
next prev parent reply other threads:[~2021-06-19 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 4:20 L A Walsh
2021-06-15 7:16 ` Russell VT
2021-06-15 21:13 ` L A Walsh
2021-06-17 1:47 ` Russell VT
2021-06-16 17:22 ` Achim Gratz
2021-06-19 11:34 ` L A Walsh
2021-06-19 13:28 ` L A Walsh [this message]
2021-07-03 23:36 ` L A Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=60CDF106.6030907@tlinx.org \
--to=cygwin@tlinx.org \
--cc=Stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).