bug in cygwin tar reading unexpected input(s)...
Tue Jun 15 07:16:27 GMT 2021
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.
On Mon, Jun 14, 2021 at 9:22 PM L A Walsh <email@example.com> 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.
> 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
> 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 <firstname.lastname@example.org>
More information about the Cygwin