public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Russell VT <russellvt@gmail.com>
To: L A Walsh <cygwin@tlinx.org>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: bug in cygwin tar reading unexpected input(s)...
Date: Tue, 15 Jun 2021 00:16:27 -0700	[thread overview]
Message-ID: <CANV2+nUOP4eyReRK-RJ1mUrs7ZHNUnKsgWi_eVNJKjhPjZfjzA@mail.gmail.com> (raw)
In-Reply-To: <60C82AAB.1090901@tlinx.org>

I think we need more context, here... as what does Windows versus Cygwin
think those permissions are...???

Are you running your terminal, as you... or did you run it as Administrator?

Have you run an update, and not rebooted?

There should be some "basic shell debugging" done here, first... since
there's a disconnect from when tar gets its file list, and when it
physically goes to retrieve a (possibly temporary) file. It will also
complain about directories it can read, but not access. So, it would be
better to figure out what the "difference" is between what you expect, and
what actually happened with the tar.

Unfortunately, permission issues between Windows and Cygwin can be
*extremely* complex (ie. there are a ton of details missing here, which
might make it easier to help troubleshoot).

Hope that helps point you in a good direction.

Cheers!
Russell VT

On Mon, Jun 14, 2021 at 9:22 PM L A Walsh <cygwin@tlinx.org> wrote:

> 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.
>
> Win7SP1x64
> cygcheck (cygwin) 3.2.0
>
> The tar continued and finished much as it would after an unreadable file.
>
> Another error, maybe similar,
>
>
> tar: C\:Prog64FastPictureViewer: Warning: Cannot file_has_acl_at: No
> such file or directory
>
>  From a file in "C:\Program Files\FastPictureViewer" [likely mis-]named
> "C:Prog64FastPictureViewer"
>
> It seems to be a .dll, that somehow got its name mangled.
>
> Not sure what it was trying to do, but the file seems to be 'in-use'.
>
>
>
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>


-- 
Russell M. Van Tassell <russellvt@gmail.com>

  reply	other threads:[~2021-06-15  7:16 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 [this message]
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
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=CANV2+nUOP4eyReRK-RJ1mUrs7ZHNUnKsgWi_eVNJKjhPjZfjzA@mail.gmail.com \
    --to=russellvt@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=cygwin@tlinx.org \
    /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).