public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ismail Donmez <ismail@donmez.ws>
To: cygwin@cygwin.com
Subject: Re: [TESTERS needed] New POSIX permission handling
Date: Thu, 16 Apr 2015 16:09:00 -0000	[thread overview]
Message-ID: <1429200569630-117621.post@n5.nabble.com> (raw)
In-Reply-To: <20150416110304.GA26837@calimero.vinschen.de>

Hi,


Corinna Vinschen-2 wrote
> On Apr 16 03:20, Ismail Donmez wrote:
>> Corinna Vinschen-2 wrote
>> > I just applied a patch which is supposed to handle this owner==group
>> > scenario better.
>> > 
>> > In short, Cygwin will try to handle POSIX user and group permissions
>> > separately, even if owner == group.  This is basically a fake as far
>> > as the actual permissions of the account are concerned, but it allows
>> > applications still to chmod to different user and group perms.  It
>> > just *looks* different in the end.
>> > 
>> > The only restriction of this is that the POSIX user permissions are
>> > always changed so that the user perms are >= the group perms in this
>> > situation.  So this:
>> > 
>> >   chmod 460 foo
>> > 
>> > will be internally twisted into
>> > 
>> >   chmod 660 foo
>> > 
>> > 
>> > I uploaded new developer snapshots to https://cygwin.com/snapshots/
>> > and I'm just uploading a 2.0.0-0.5 test release with this change.
>> 
>> I tested the new test release (rm -rfd the cygwin installation and
>> re-installed from scratch just to be sure), my original testcase with
>> quilt
>> and mutt works, BUT now when I run make install inside mutt source it
>> complains that /usr/bin/install cannot change permissions on the
>> destination
>> executables.
> 
> Hmm, ok.  Off the top of my head I don't understand this.
> 
>> can post an easily reproducable error. Because running the same command
>> myself gives no error whatsoever. I'll try to come up with a better
>> report.
> 
> That would be nice.  A good start would be to know what permission mask
> install is trying to set the destination to.  Maybe that sheds some light.

So I am trying to configure and install mutt, and the first error I see is
at the end of configure:

configure: creating ./config.status
chmod: changing permissions of './config.status': Permission denied
configure: error: write failure creating ./config.status

Well, looks like its right:

[~/src/mutt]> chmod +x config.status
chmod: changing permissions of ‘config.status’: Permission denied

[~/src/mutt]> uname -a
CYGWIN_NT-6.3 ux31a 2.0.0(0.287/5/3) 2015-04-15 17:39 x86_64 Cygwin

[~/src/mutt]> getfacl .
# file: .
# owner: ismail
# group: ismail
user::rwx
group::r-x
group:SYSTEM:rwx
group:Administrators:rwx
mask:r-x
other:r-x
default:user::rwx
default:group::r-x
default:group:SYSTEM:rwx
default:group:Administrators:rwx
default:mask:r-x
default:other:r-x

[~/src/mutt]> getfacl config.status
# file: config.status
# owner: ismail
# group: ismail
user::rwx
group::r-x
group:SYSTEM:rwx
group:Administrators:rwx
mask:r-x
other:r-x

Any ideas? :)

Thank you.




--
View this message in context: http://cygwin.1069669.n5.nabble.com/TESTERS-needed-New-POSIX-permission-handling-tp117406p117621.html
Sent from the Cygwin list mailing list archive at Nabble.com.

--
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

  reply	other threads:[~2015-04-16 16:09 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 10:07 Corinna Vinschen
2015-04-10 21:13 ` Warren Young
2015-04-11  9:35   ` Corinna Vinschen
2015-04-11  0:00 ` Steven Penny
2015-04-11  9:40   ` Corinna Vinschen
2015-04-11 10:07     ` Corinna Vinschen
2015-04-11 16:26       ` Ernie Rael
2015-04-12  8:22         ` Corinna Vinschen
2015-04-11 10:23     ` Corinna Vinschen
2015-04-11 10:47     ` Steven Penny
2015-04-11 14:30       ` Corinna Vinschen
2015-04-11 16:05       ` Andrey Repin
2015-04-12 17:37         ` Adam Dinwoodie
2015-05-16  2:39   ` Steven Penny
2015-05-17  7:44     ` Duncan Roe
2015-05-19  7:52     ` Jiří Engelthaler
2015-04-11  8:47 ` Achim Gratz
2015-04-11  9:02   ` David Macek
2015-04-11  9:08     ` Achim Gratz
2015-04-11  9:51       ` David Macek
2015-04-11 11:51         ` Achim Gratz
2015-04-11 10:00     ` Corinna Vinschen
2015-04-11 12:36       ` David Macek
2015-04-11 14:31         ` Corinna Vinschen
2015-04-11  9:44   ` Corinna Vinschen
2015-04-11 11:11     ` Bryan Berns
2015-04-11 14:32       ` Corinna Vinschen
2015-04-11 16:05   ` Andrey Repin
2015-04-11 17:11 ` donmez
2015-04-12  8:35   ` Corinna Vinschen
2015-04-12 13:21     ` İsmail Dönmez
2015-04-12 14:25       ` Corinna Vinschen
2015-04-15 15:42         ` Corinna Vinschen
2015-04-16 10:20           ` Ismail Donmez
2015-04-16 11:03             ` Corinna Vinschen
2015-04-16 16:09               ` Ismail Donmez [this message]
2015-04-16 16:24                 ` Corinna Vinschen
2015-04-16 16:48                   ` Ismail Donmez
2015-04-17  7:30                     ` Corinna Vinschen
2015-04-17 10:06                       ` Corinna Vinschen
2015-04-17 15:17                         ` Ismail Donmez
2015-04-17 16:22                           ` 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=1429200569630-117621.post@n5.nabble.com \
    --to=ismail@donmez.ws \
    --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).