From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated (experimental): coreutils-8.23-3
Date: Mon, 29 Sep 2014 12:13:00 -0000 [thread overview]
Message-ID: <loom.20140929T105037-80@post.gmane.org> (raw)
In-Reply-To: <announce.54239E64.7050600@byu.net>
Eric Blake <ebb9 <at> byu.net> writes:
> This build is also the first against the
> new ACL rules of cygwin1.dll, so there may be some oddities in ls as a
> result.
That hunch proved to be correct, but it is cp and not ls that is affected:
> cp -vr gnuplot.x86_64/dist/gnuplot /mnt/mirror/patch/x86_64/release/
cp: cannot create directory â/mnt/mirror/patch/x86_64/release/gnuplotâ: File
exists
> getfacl /mnt/mirror/patch/x86_64/release/gnuplot
# file: /mnt/mirror/patch/x86_64/release/gnuplot
# owner: share-owner
# group: Domain Users
user::---
group::---
group:share-adm:rwx
mask:rwx
other:---
default:user::---
default:group::---
default:group:share-adm:rwx
default:mask:rwx
default:other:---
The user doing this operation is member of share-adm, but not the
share-owner. It seems that cp is deciding that the (existing) directory
should be newly created, which of course fails. Reverting to both 8.23-2 or
8.15-3 fixes that problem.
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-09-29 9:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 8:47 Eric Blake
2014-09-29 12:13 ` Achim Gratz [this message]
2014-09-29 17:22 ` Eric Blake
2014-09-29 17:23 ` Achim Gratz
2014-09-30 16:27 ` Achim Gratz
2014-10-12 8:56 ` Corinna Vinschen
2014-10-13 15:54 ` Eric Blake
2014-10-14 9:56 ` Achim Gratz
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=loom.20140929T105037-80@post.gmane.org \
--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).