From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.3.3-1 [with DEPRECATION NOTES]
Date: Mon, 31 Jan 2022 10:22:18 +0100 [thread overview]
Message-ID: <YfeqShMvv/CAvU85@calimero.vinschen.de> (raw)
In-Reply-To: <2110109458.20220128114144@yandex.ru>
On Jan 28 11:41, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> > Hi Andrey,
>
> > On Jan 26 19:34, Andrey Repin wrote:
> >> Greetings, Corinna Vinschen via Cygwin-announce!
> >> [...]
> >> $ /usr/bin/d2u ./Localization.lua
> >> dos2unix: Failed to change the permissions of temporary output file ./d2utmpEBELkH: Permission denied
> >> dos2unix: problems converting file ./Localization.lua
>
> > I could easily reproduce your problem, which I introduced myself into
> > Cygwin 3.3.2. At the time I was wrestling with a new Samba version and
> > thought I have seen a problem with permissions. However, I don't know
> > how to reproduce the problem because it just doesn't show up anymore.
>
> I could arrange a debug session, if you need.
As I wrote, I could reproduce your problem easily. What I can't
reproduce is the original problem I thought I have seen back when I
pushed the patch breaking your scenario.
> > So I just reverted the patch. It worked this way for years.
>
> > I also created new developer snapshots for testing. I guess it's
> > about time for a 3.3.4 release...
>
> Simple retry completed without an error on the snapshot Cygwin DLL.
Thanks for testing,
Corinna
prev parent reply other threads:[~2022-01-31 9:22 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
2022-01-27 14:43 ` Corinna Vinschen
2022-01-28 8:41 ` Andrey Repin
2022-01-31 9:22 ` Corinna Vinschen [this message]
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=YfeqShMvv/CAvU85@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).