From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated (experimental): coreutils-8.23-3
Date: Mon, 29 Sep 2014 17:22:00 -0000 [thread overview]
Message-ID: <542990F0.2050000@redhat.com> (raw)
In-Reply-To: <loom.20140929T105037-80@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
On 09/29/2014 03:02 AM, Achim Gratz wrote:
> 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.
Can you give me a simple self-contained script that creates all
necessary prerequisites before attempting the failing 'cp', to help me
in trying to reproduce what is going differently here?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-09-29 17:03 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
2014-09-29 17:22 ` Eric Blake [this message]
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=542990F0.2050000@redhat.com \
--to=eblake@redhat.com \
--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).