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
