public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: dos2unix: Failed to change the permissions of temporary output file …: Permission denied
Date: Sat, 1 Jan 2022 11:02:30 -0700	[thread overview]
Message-ID: <a8e744d4-46ee-2338-413e-33f06dfbab31@SystematicSw.ab.ca> (raw)
In-Reply-To: <31808206.20211229183014@yandex.ru>

On 2021-12-29 08:30, Andrey Repin wrote:
> Greetings, All!
> 
> I've got a problem with recent Cygwin and some old scripts of mine.
> Particularly, the script at one point trying to normalize EOL's in a file so
> that following operations run smooth.
> 
> But the step fails with message about permission changes.
> The problem is,
> 1. the file is located on a network share and
> 2. it is a noacl share.
> 
> The scripts were running fine several months ago and nothing has сhanged on
> host and remore except Cygwin itself.
> 
> $ getfacl Localization.lua
> getfacl: Localization.lua: Not supported
> 
> $ icacls Localization.lua
> Localization.lua No mapping between account names and security IDs was done.
> (I)(F)
>                   No mapping between account names and security IDs was done.
> (I)(RX)
>                   All:(I)(RX)
> 
> Successfully processed 1 files; Failed processing 0 files
> 
> Cygwin Package Information
> Package              Version        Status
> cygwin               3.3.3-1        OK
> dos2unix             7.4.2-1        OK
> 
> Anything else I can do to provide more information?

Hi Andrey,

Happy New (Grigorian) Year!

Maybe show us a standalone script command line execution, script 
execution trace (like -xv), failing command line expansion, failure 
messages, Cygwin permissions of relevant components, and Cygwin 
installation status of all the components (or cygcheck -hrsv log).

I don't know what Localization.lua is and showing Windows perms of it 
has to do with anything you described, but it looks like it may no 
longer have Cygwin perms, so maybe fill in some blanks here also.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  parent reply	other threads:[~2022-01-01 18:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29 15:30 Andrey Repin
2022-01-01 11:32 ` Andrey Repin
2022-01-01 18:02 ` Brian Inglis [this message]
2022-01-02  9:53   ` Andrey Repin
2022-01-02 10:05   ` Andrey Repin
2022-01-02 20:59     ` Brian Inglis

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=a8e744d4-46ee-2338-413e-33f06dfbab31@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).