On 22/01/2025 17:47, Bill Stewart via Cygwin wrote:
On Wed, Jan 22, 2025 at 7:17 AM Marco Atzeri wrote:
Lester,
it seems to me that you have a clear problem in COMMUNICATION. Do NOT
reply to me only. Reply to the mailing list.
I am NOT your personal support HOTLINE.
This is the last advise.
Hi Cygwin list,
Replying to this email to let you know that we've sent updated information on
the proposed changes to cygwin-developers, including a patch, which we've also
sent to cygwin-patches.
The patch replaces the following undocumented API calls with the corresponding
documented APIs:
On Tue, 14 Jan 2025, Takashi Yano via Cygwin wrote:
> Personally, I personally prefer releasing 3.5.6 ASAP.
Is this the plan, now that the hangs seem to be resolved? (Maybe after
additional confirmation/testing?)
--
Problem reports: https://cygwin.com/problems.html
FAQ: h
ASSI via Cygwin writes:
> I've got a new machine with Win11 at work, copied over all my
> configuration from the old Win10 one, but I can't seem to get gpg2 to
> show the passphrase prompt through the W32 GUI of GPG agent. In fact
> the agent doesn't seem to even start (the named pipes do not get
On Jan 21 16:30, Jeremy Drake via Cygwin wrote:
> I've been trying to track down why ruby 3.4.1 is failing to build for
> msys2. I've now confirmed that this same issue reproduces with
> upstream Cygwin 3.5.4 and 3.6.0-0.335.gb879cd1661ad, so I thought I'd
> bring it up here:
>
> when building ru
On Jan 22 00:37, Roland Mainz via Cygwin wrote:
> Hi!
>
>
>
> If a Windows filesystem does not support a type of timestamp it sets
> the matching timestamp field in |FILE_BASIC_INFO| to |0LL| (e.g. see
> Windows-driver-samples/filesys/cdfs/fileinfo.c:
> |Buffer->LastAccessTime.QuadPart = 0|
On Wed, Jan 22, 2025 at 7:17 AM Marco Atzeri wrote:
Lester,
> it seems to me that you have a clear problem in COMMUNICATION. Do NOT
> reply to me only. Reply to the mailing list.
>
> I am NOT your personal support HOTLINE.
> This is the last advise.
>
Indeed. Here are some other references that m
On 2025-01-22 01:00, ASSI via Cygwin wrote:
I've got a new machine with Win11 at work, copied over all my
configuration from the old Win10 one, but I can't seem to get gpg2 to
show the passphrase prompt through the W32 GUI of GPG agent. In fact
the agent doesn't seem to even start (the named pip
On 21/01/2025 15:26, Lester Ingber wrote:
No, the problem is not "solved" at all.
We just have to click away now-seven instances of python!
Thanks anyway.
Lester
Lester,
it seems to me that you have a clear problem in COMMUNICATION.
Do NOT reply to me only. Reply to the mailing list.
I am N
On Mon, 20 Jan 2025 10:48:55 +0100
Michael Soegtrop wrote:
> Dear Cygwin Team,
>
> apparently there was a change in the test release (what I get when I run
> cygwin setup with --allow-test-packages) in the last few days. With the
> latest test release I see CI failures again with the same effect
On Wed, 22 Jan 2025 at 00:38, Roland Mainz via Cygwin wrote:
>
> Hi!
>
>
>
> If a Windows filesystem does not support a type of timestamp it sets
> the matching timestamp field in |FILE_BASIC_INFO| to |0LL| (e.g. see
> Windows-driver-samples/filesys/cdfs/fileinfo.c:
> |Buffer->LastAccessTime.
On 22 Jan 2025, at 09:00, ASSI via Cygwin wrote:
>
> I've got a new machine with Win11 at work, copied over all my
> configuration from the old Win10 one, but I can't seem to get gpg2 to
> show the passphrase prompt through the W32 GUI of GPG agent. In fact
> the agent doesn't seem to even start
I've got a new machine with Win11 at work, copied over all my
configuration from the old Win10 one, but I can't seem to get gpg2 to
show the passphrase prompt through the W32 GUI of GPG agent. In fact
the agent doesn't seem to even start (the named pipes do not get
created) and I get prompted di
13 matches
Mail list logo