public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: bug in cygwin tar reading unexpected input(s)...
Date: Wed, 16 Jun 2021 19:22:16 +0200	[thread overview]
Message-ID: <87im2dk9mf.fsf@Rainer.invalid> (raw)
In-Reply-To: <60C82AAB.1090901@tlinx.org> (L. A. Walsh's message of "Mon, 14 Jun 2021 21:20:59 -0700")

L A Walsh writes:
> Tar'ing up a windows dir (ProgData) had some unexected failures:
>
> Several of the sort:
>
> tar: Dbgview: Warning: Cannot llistxattrat: No such file or directory
> tar: Desktops: Warning: Cannot llistxattrat: No such file or directory
> tar: DiskView: Warning: Cannot llistxattrat: No such file or directory
> tar: LoadOrd: Warning: Cannot llistxattrat: No such file or directory
> tar: portmon: Warning: Cannot llistxattrat: No such file or directory
>
> Where the item listed (Dbgview, DiskView, etc) is a
> windows symlink like:
>
> 2019/02/07  22:53    <SYMLINK>      Dbgview [SI\Dbgview.exe]
> 2019/02/07  22:53    <SYMLINK>      Desktops [SI\Desktops.exe]
> 2019/02/07  22:53    <SYMLINK>      DiskView [SI\DiskView.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?



Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

  parent reply	other threads:[~2021-06-16 17:22 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 [this message]
2021-06-19 11:34   ` L A Walsh
2021-06-19 13:28   ` L A Walsh
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=87im2dk9mf.fsf@Rainer.invalid \
    --to=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).