DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 86EB33858C98
MIME-Version: 1.0
Date: Sat, 22 Jun 2024 07:45:20 +0100
Message-ID: <CAJQQdJgYG-4LP4gJ-4mmy8gk3yD9CY8wThn=RRBod7uRFi-GAA@mail.gmail.com>
Subject: Aborting Cygwin setup in unattended modes
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
From: David Allsopp via Cygwin <cygwin AT cygwin DOT com>
Reply-To: David Allsopp <david AT tarides DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

If Cygwin's setup requires input (for example, to select a mirror),
with --quiet-mode hidden it simply terminates (there's no apparent
exit status or message, though).

With --quiet-mode noinput, Cygwin setup sits at the appropriate
dialog, but it's of course non-responsive.

Would it be possible in these situations for Cygwin to abort,
preferably with a non-zero exit code?

The background to this was running Cygwin setup in GitHub Actions (so
UI not visible), _without_ specifying --site, where the Cygwin
installation had been restored by actions/cache but not the registry
setting in HKLM\SOFTWARE\Cygwin\setup meaning that setup could not
find setup.rc and consequently determine the last-used mirror. The GUI
therefore invisibly froze at mirror selection.

That issue has obviously been fixed, but it would seem sensible that
Cygwin's setup doesn't ever display a dialog _requiring_ input where
all that input has been disabled!


David

-- 
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