DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 54DFgJsd1895422
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 54DFgJsd1895422
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=m08JXjnh
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org B22493858C24
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1747150937;
	bh=G0rpSQf0fd6Rlf+9OREmAIDA9GqixoogHnjl9oWrBCk=;
	h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	From;
	b=m08JXjnhMjqVKWHMPqTaTWCQ6IWr+DR+r0JE73RXennJyyWZ3ii7N1LqMiGUAYAYf
	6+RUF1K+NWlWEuyopkwwnhAf6lhkCtLBs6j+/jmEaendVlnL/zNrSIS4JJZQR3r/yh
	JdTqcn3UuowLd4PMk2Jcxrkk8sH4HsqEcZ6JEij0=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org B87E53858CD1
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org B87E53858CD1
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1747150865; cv=none;
	b=lfAxbY7vFTGzmbZW9yIie7us28zF53IBqUR5CABPhWru/UgICWSTmfJdzNyEUaKPW4KDBPVGvex2UuSXsEiA/ry989C5mKRYpySlkQEGEU3edkTdMXETaRmXN4ojOoUy9Scv1UcMKWQ4tpyH3saferjlbIBXebUptI7MAKk+rxc=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1747150865; c=relaxed/simple;
	bh=STxhMDq3RYowFp8GMoWDarobKfrdlsrOHxTJRDZ2DhI=;
	h=Message-ID:Date:MIME-Version:From:Subject:To:DKIM-Signature;
	b=S6LDBr/xYyjFiN2s3+2EkD0Q+x8JERmTn/90G8yzoMYVnn2c+xkQqVHS58IzpUXQUxKy2VQFbgJIJtxIZPlrI+KIZnmskib2NGHbMQayKShDFFStpVGkdbr1EtZQdSj3/x5GaH6m0XVNDzQtsCuGBF44Q6DszXn0AIDTIUh0VZ4=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org B87E53858CD1
Message-ID:	<8c0312e1-a37d-433a-bea2-6eec96eda5af@SystematicSW.ab.ca>
Date:	Tue, 13 May 2025 09:41:01 -0600
MIME-Version:	1.0
User-Agent:	Mozilla Thunderbird
Subject:	Re: Using Cygwin installation on network share in CI fails
To:	cygwin AT cygwin DOT com
References:	<CA+1jF5oPR8s20fEpadcdpE8TA+H_0P-inL8sSax7zz3QAcxLWg AT mail DOT gmail DOT com>
	<6ec5c987-b2ff-421d-b8f4-8b1ee7dca29c AT SystematicSW DOT ab DOT ca>
	<CA+1jF5orHBdQ3fQOY7FVGYwQYpVWS=TFnXbtcwxHh512fr4hQw AT mail DOT gmail DOT com>
Organization:	Systematic Software
In-Reply-To:	<CA+1jF5orHBdQ3fQOY7FVGYwQYpVWS=TFnXbtcwxHh512fr4hQw@mail.gmail.com>
X-Stat-Signature:	cwtmbccph573sunhpykrnterff93ogjy
X-Rspamd-Server:	rspamout06
X-Rspamd-Queue-Id:	E089F8000F
X-Session-Marker:	427269616E2E496E676C69734053797374656D6174696353572E61622E6361
X-Session-ID:	U2FsdGVkX1/WroQ94uw3dm6+FElC3X+pQ1IBf/OPuk4=
X-HE-Tag:	1747150862-657061
X-HE-Meta:	U2FsdGVkX1+Qc6USL0C/1V7DRQDzW1tX5lhvJt9mBvhE2df/AjX317+uMjHY3hjyYKOkp+XhBTOI7oNQmVc+OmujczkO3MK+hvbvdwDAjmBIpYUPzu3U4r7JwOdvszjd92bYNS/CvaGOBrdNOj9pjYHtIuzczX7rqumDY5IzlOrhIB0qPiBT05ohXlaexsh+P5MZ1lQvzp8n23ON+sHNkSrH0GMD6CSSYsCI114BjpMxyu3FzyF9efuVrkCyM4pPOGmN9ySdceoD4Ao5uQWBMYKAVx1PrY3AFbtZXQKyucWoHlRmRsjQ6yfE1msOFrqOpSye9cDN0m188kd+r24ZwWmHplXuVS++qnPnwAPST9039vhNWrxTuYSi644glgq+xKwn7Kqrx2k=
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Brian Inglis via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	cygwin AT cygwin DOT com
Cc:	Brian Inglis <Brian DOT Inglis AT SystematicSW DOT ab DOT ca>
Errors-To:	cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 54DFgJsd1895422

On 2025-05-13 02:33, Aurélien Couderc via Cygwin wrote:
> On Mon, May 12, 2025 at 7:43 PM Brian Inglis via Cygwin wrote:
>> On 2025-05-12 10:34, Aurélien Couderc via Cygwin wrote:
>>> Using Cygwin install on network share in CI fails.
>>> This seems to be a recent regression, as this was working a year before.

If you have not run it in a year, it is possibly many things have changed in 
your environment.

>>> Now on Windows 10 with Cygwin 3.6.1 it fails with error 127.
>> That can mean a missing DLL function entry.

> No, I do not think so, as Cygwin works fine if I install it on NTFS.

So you are not installing it on NTFS?
What kind of share are you installing it on?

Are you installing it using the *latest* download of Cygwin Setup from

	https://cygwin/com/setup_x86_64.exe

Do the installed files have all their read and exec bits set - this was an issue 
with a recent older release of Cygwin Setup where some files did not.

> WIndows DLLS should be fine, and the system is up to date with patches
> and has a support contract.

Should be is not definite!
Patches have been known to cause issues!
Does the support contract cover supporting the execution of Cygwin and utilities?

> But Cygwin fails if I install it on a Windows network share. Same
> installation procedure (.\setup-x86_64.exe -q --no-write-registry
> --no-admin --root %cd%
> --no-desktop --site "https://mirrors.kernel.org/sourceware/cygwin"),
> just different drive (N: instead of C:)

A verbal description of a common failure is inadequate.
We are not mind readers and have no idea how your CI environment is set up.
Everything works fine in our CI environment, so your environment is defective, 
and we have no information allowing us to do more than speculate and suggest 
what may be an issue.

It appears possible it is an issue with how the share you are using as a network 
drive is now set up.
It may have been changed recently due to some process or policy change by your 
IT department.
Please ask them what they have done recently that might affect the share you 
have been using successfully since 2016.

Also please note that recent Windows changes have started blocking Cygwin 
programs with the same names as programs provided by MS (as outdated and 
insecure versions) like bash, curl, ssh*, tar, etc. possibly under the Windows 
security heading of Tamper Protection?

You have failed to respond to requests for actual information about or from the 
failing environment.
We need to see actual output from commands of the file system properties and 
directory contents and permissions.

Maybe follow the problem reporting guidelines to run cygcheck -hrsv in the CI 
and include the output as a plain text attachment to your post.

Then there may be enough information for someone to address your issue.

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

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -