X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 39F6B384B0C1
Authentication-Results:	sourceware.org; dmarc=none (p=none dis=none)
	header.from=SystematicSw.ab.ca
Authentication-Results:	sourceware.org;
	spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca
X-Authority-Analysis:	v=2.3 cv=ecemg4MH c=1 sm=1 tr=0
	a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17
	a=IkcTkHD0fZMA:10 a=eALN4BIB3nVMZjRVyBcA:9 a=QEXdDO2ut3YA:10
Subject:	Re: setup-x86_64.exe --quiet-mode issues using Management Tools
To:	cygwin AT cygwin DOT com
References:	<DM5PR05MB295527B652FAF4256E9B26F7FFDB0 AT DM5PR05MB2955 DOT namprd05 DOT prod DOT outlook DOT com>
	<6a7a523f04684961b1f5fc5b5081a72f AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
	<CANV9t=QFyo+nR8wvMy0Om=WTLNCmi297H2CBqGfLq-fkKdtp0w AT mail DOT gmail DOT com>
	<a1266f159dc749608d2ba37519f51fd5 AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
	<CANV9t=Rhphf2B4WL2g4chv=xzYgZDD7NkJjFW1OV4eyWvV_e7Q AT mail DOT gmail DOT com>
	<f59e75f46c2b407fa37bcf74b3bc0232 AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
	<CANV9t=SeR8X25_z9N=WJrY-x9gnQkDUunVPGi3zs_zL8xUNV7w AT mail DOT gmail DOT com>
	<c20d98fc3269447a86600de2421a976e AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
	<CANV9t=QP6Sn+Ly+OWM6AuFT=p7_mYENra+5bf0d=hziLcgfeVQ AT mail DOT gmail DOT com>
	<c09f23e947904b25ad7011c936fd27f8 AT BELBRU-EXMP101 DOT eeas DOT europa DOT eu>
	<CANV9t=TYCsGsohqGRVpNGUsGf=Cua_wtk+itWmxVtdkUUeux7A AT mail DOT gmail DOT com>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Autocrypt:	addr=Brian DOT Inglis AT SystematicSw DOT ab DOT ca; prefer-encrypt=mutual;
	keydata=
	mDMEXopx8xYJKwYBBAHaRw8BAQdAnCK0qv/xwUCCZQoA9BHRYpstERrspfT0NkUWQVuoePa0
	LkJyaWFuIEluZ2xpcyA8QnJpYW4uSW5nbGlzQFN5c3RlbWF0aWNTdy5hYi5jYT6IlgQTFggA
	PhYhBMM5/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsDBQkJZgGABQsJCAcCBhUKCQgLAgQW
	AgMBAh4BAheAAAoJEB62lxu92I8Y0ioBAI8xrggNxziAVmr+Xm6nnyjoujMqWcq3oEhlYGAO
	WacZAQDFtdDx2koSVSoOmfaOyRTbIWSf9/Cjai29060fsmdsDLg4BF6KcfMSCisGAQQBl1UB
	BQEBB0Awv8kHI2PaEgViDqzbnoe8B9KMHoBZLS92HdC7ZPh8HQMBCAeIfgQYFggAJhYhBMM5
	/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsMBQkJZgGAAAoJEB62lxu92I8YZwUBAJw/74rF
	IyaSsGI7ewCdCy88Lce/kdwX7zGwid+f8NZ3AQC/ezTFFi5obXnyMxZJN464nPXiggtT9gN5
	RSyTY8X+AQ==
Organization:	Systematic Software
Message-ID:	<205a969a-9f65-9601-0fe1-681a7a3f043e@SystematicSw.ab.ca>
Date:	Tue, 21 Apr 2020 14:32:57 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
	Thunderbird/68.7.0
MIME-Version:	1.0
In-Reply-To:	<CANV9t=TYCsGsohqGRVpNGUsGf=Cua_wtk+itWmxVtdkUUeux7A@mail.gmail.com>
X-CMAE-Envelope:	MS4wfJRjmD62izthF1vj5goq0u1gQoJu/1kF183tYcPboiUJ9BopY31gwMHpXqpnU9oXYdfMZsOIsgKstdW4JkXYiTYvps6dNUCSdMNuYKBmaZ/2yyodvJrY
	3NP8B33nq7Lbif/BnTAbnI1oKC2bq3I4/Bse2VRCj5yaiNa8kdZ2+X9rDpFes2moPxoHAZNLCHL2uQ==
X-Spam-Status:	No, score=-16.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3,
	RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<http://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:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On 2020-04-21 08:17, Bill Stewart wrote:
> On Tue, Apr 21, 2020 at 7:56 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>> Are you sure that a setup that is automated with a silent installation, but
>> it still displays a progress popup, it cannot fail if it is not able to
>> display that window when there is no user logged in? I am not, hence I
>> would prefer that setup could ensure a real background operation.
>>
>> An exception displaying the progress window could lead to the interruption
>> of the installation process. That is a blocking condition as well, even
>> though no input is required by the user.

> An exception during the installation would only block if it prevents the
> process from closing (i.e., if it displays a message box). That could happen
> in an installation even if the installer isn't displaying a GUI.
> 
> What I am saying is what's important about automated installation is that it
> not block (even in the case of an exception). Whether the installer displays
> a GUI or not is really irrelevant, particularly if the installation isn't
> running as the current user (in which case the current user doesn't see the
> GUI anyway).

One issue with the -M, --package-manager semi- and -q, --quiet-mode unattended
installs are that any errors are logged only in /var/log/setup.log.full, which
is overwritten by the next run, with only a summary log remaining at the end of
the cumulative /var/log/setup.log, and not all error or warning messages are
significant.

The is especially likely if *any* Cygwin processes are running when setup
starts, so you need to kill off any processes running any commands or using any
DLLs under the Cygwin root, before running setup.

You will have to manage the processes and error logs with your network install
wrapper, although some work could be delegated to permanent postinstall
[0z]p_...sh scripts in /etc/postinstall/.

The order of running postinstall script is alpha order, I believe under the
default/POSIX/C locale, with 0p_...sh scripts run before and zp_...sh scripts
run after all others.

It is *essential* that /etc/postinstall/0p_000_autorebase.dash always run first
and to completion without errors, as otherwise Cygwin DLLs could overlap,
especially under Cygwin 32 installs, and any program could fail, with a variety
of possible errors.

As part of my Cygwin profile, I check for any remaining files matching
	/etc/postinstall/[!0z][!pqrst][!_]*.*sh
or
	/{,usr/}{,*86*/**/}{*bin,lib}/*.{dll,exe}.new
as new exes and DLLs should replace the old files before postinstall scripts
run, and non-permanent package postinstall scripts should be renamed with .done
suffixed after execution, otherwise setup needs to be rerun with no Cygwin
processes running, or the system needs to be restarted, as Cygwin may have
created a Windows post-install script to complete the replacements.

You will also have to manage upgrades with -g, --upgrade-also to handle
upgrading to get security and other urgent regular base package maintenance
patches applied, for example Windows release support in Cygwin, and crypto,
ca-certificates, openssl, tzdata package upgrades.

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

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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 -