From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: 1.7.9-1 Patch command mangles permissions on windows 7
Date: Fri, 14 Oct 2011 10:43:00 -0000 [thread overview]
Message-ID: <4E981221.5080102@cornell.edu> (raw)
In-Reply-To: <CAL1QdWffTReMc64HhqTuu1zX0E5rwTeceAZ-vK23o6cNNbtWGQ@mail.gmail.com>
On 10/13/2011 7:15 PM, Roger Pack wrote:
> Forgive me if this is a commonly reported bug, but I wasn't sure if
> other discussions on permissions issues were the same as this issue...
>
> $ c:\installs\cygwin\bin\patch.exe -p0< multithread_utilities_trunk.diff
> (Stripping trailing CRs from patch.)
> patching file xxx/yyy/zzz/Test.java
> ...
>
> now attempt to use the files I just patched:
>
> $ mvn clean install
> ...
> [ERROR] error: error reading xxx\yyy\zzz\Test.java;
> xxx\yyy\zzz.java (Access is denied)
>
> I was able to reproduce this on another computer, as well.
> Windows 7, 64 bit, blah blah blah.
>
> When I right click on the files and go to properties -> security,
> somehow all users except administrators have no rights to the modified
> files.
This could be related to the problem discussed starting at
http://cygwin.com/ml/cygwin/2009-11/msg00922.html
The issue there was ACLs on the temporary directory used by patch. The
resolution of that was to set TMP and TEMP to "/tmp" in Cygwin's default
startup files (see /etc/defaults/profile). But you appear to be running
patch outside of a Cygwin shell, so you're not benefiting from that fix.
(I'm basing this guess on the fact that you start patch by giving its
Windows path.)
Ken
--
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:[~2011-10-14 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 23:15 Roger Pack
2011-10-14 10:43 ` Ken Brown [this message]
2011-10-14 12:47 ` Roger Pack
2011-10-17 14:20 ` Andrey Repin
2011-11-18 20:55 ` Roger Pack
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=4E981221.5080102@cornell.edu \
--to=kbrown@cornell.edu \
--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).