From: Andrey Repin <anrdaemon@yandex.ru>
To: Andrey Repin <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.3.3-1 [with DEPRECATION NOTES]
Date: Wed, 26 Jan 2022 21:49:58 +0300 [thread overview]
Message-ID: <1737745223.20220126214958@yandex.ru> (raw)
In-Reply-To: <387205474.20220126193416@yandex.ru>
Greetings, Andrey Repin!
> Greetings, Corinna Vinschen via Cygwin-announce!
>> The following packages have been uploaded to the Cygwin distribution:
>> * cygwin-3.3.3-1
>> * cygwin-devel-3.3.3-1
>> * cygwin-doc-3.3.3-1
> It seems there's some network shares problem going on with 3.3
> 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 remote except Cygwin itself.
> $ ls -ld . ./Localization.lua
> drwxr-xr-x 1 anrdaemon None 0 Jan 2 12:07 .
> -rw-r--r-- 1 anrdaemon None 32212 Jan 1 14:32 ./Localization.lua
> $ /usr/bin/d2u ./Localization.lua
> dos2unix: Failed to change the permissions of temporary output file ./d2utmpEBELkH: Permission denied
> dos2unix: problems converting file ./Localization.lua
> $ getfacl . ./Localization.lua
> getfacl: .: Not supported
> 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
> Saved SID's are domain ones
> Localization.lua
> D:(A;ID;FA;;;S-1-5-21-2269650170-3990761244-2407083512-1105)
> (A;ID;0x1200a9;;;S-1-5-21-2269650170-3990761244-2407083512-513)
> (A;ID;0x1200a9;;;WD)
> Where S-1-5-21-2269650170-3990761244-2407083512-1105 is mine.
> # file: Localization.lua
> # owner: anrdaemon
> # group: domain\040users
> user::rwx
> user:anrdaemon:rwx
> group::r-x
> group:domain\040users:r-x
> mask::rwx
> other::r-x
> Client PC is not part of the domain, but user name and password do match.
> Again, rolling back to 3.2 restores the operation.
I've found a working domain client VM, and the issue remains even in domain
environment. Which is surprising, to say the least. And this is no antivirus
issue, as there's no any AV installed on the client VM.
> Cygwin Package Information
> Package Version Status
> cygwin 3.3.3-1 OK
> dos2unix 7.4.2-1 OK
> cygcheck output attached.
> Strace output attached as well, but it's rather short.
> Downgrading to Cygwin 3.2.0 resolved the problem.
> Anything else I can do to provide more information?
--
With best regards,
Andrey Repin
Wednesday, January 26, 2022 21:47:56
Sorry for my terrible english...
next prev parent reply other threads:[~2022-01-26 18:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 16:48 Corinna Vinschen via Cygwin-announce
2022-01-26 16:34 ` Andrey Repin
2022-01-26 18:49 ` Andrey Repin [this message]
2022-01-27 14:43 ` Corinna Vinschen
2022-01-28 8:41 ` Andrey Repin
2022-01-31 9: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=1737745223.20220126214958@yandex.ru \
--to=anrdaemon@yandex.ru \
--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).