From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: L A Walsh <cygwin@tlinx.org>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: win dirs don't handle lack of inherited rule(?): getfacl + tar dir Warning: Cannot acl_to_text: Invalid argument
Date: Sun, 10 Mar 2019 11:20:00 -0000 [thread overview]
Message-ID: <20190310112034.GA3785@calimero.vinschen.de> (raw)
In-Reply-To: <5C84EB7B.70408@tlinx.org>
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
On Mar 10 03:48, L A Walsh wrote:
>
>
> On 3/8/2019 4:15 AM, Corinna Vinschen wrote:
> > On Mar 7 19:35, L A Walsh wrote:
> >> I ran tar on another directory and got a huge number**
> >> of these:
> >> tar: rules: Warning: Cannot acl_to_text: Invalid argument
> >> tar: adblockplus: Warning: Cannot acl_to_text: Invalid argument
> >> tar: autopager: Warning: Cannot acl_to_text: Invalid argument
> >> tar: bookmarkbackups: Warning: Cannot acl_to_text: Invalid argument
> >> ---
> > Can you please provide the cacls or icacls command creating
> > a directory that allows to reproduce the issue?
>
> I doubt that area of my disk has ever been manipulated by
> cacls or icacls. That's in my roaming profile.
Sorry to be blunt, but the circumstances don't matter. If you want
Cygwin (and thus: tar) to behave better, I need a reproducer. For that
I must be able to create a DACL which looks like yours so I see the same
"Invalid argument" message.
So, again, please provide the cacls or icacls command creating a
directory that allows to reproduce the issue.
If that's not possible, you will have to debug this yourself, ideally by
running tar under GDB and setting a breakpoint to Cygwin's acl_to_text
function to find out what it chokes on.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-10 11:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 3:36 L A Walsh
2019-03-08 12:15 ` Corinna Vinschen
2019-03-10 10:48 ` L A Walsh
2019-03-10 11:20 ` Corinna Vinschen [this message]
2019-03-10 13:35 ` Andrey Repin
2019-03-10 16:38 ` L A Walsh
2019-03-10 22:50 ` Andrey Repin
2019-03-10 23:15 ` L A Walsh
2019-03-10 14:09 ` Brian Inglis
2019-03-12 15:45 ` L A Walsh
2019-03-12 16:36 ` Corinna Vinschen
2019-03-13 2:22 ` L A Walsh
2019-03-13 9:19 ` Corinna Vinschen
2019-03-13 9:32 ` Corinna Vinschen
2019-03-13 11:34 ` Corinna Vinschen
2019-03-15 2:46 ` L A Walsh
2019-03-15 9:17 ` Corinna Vinschen
2019-03-15 12:25 ` Brian Inglis
2019-03-15 13:34 ` Corinna Vinschen
2019-03-15 14:46 ` L A Walsh
2019-03-15 14:52 ` Corinna Vinschen
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=20190310112034.GA3785@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).