DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 65GJ6mgq149265
DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C0D544BA2E11
To: cygwin@cygwin.com
Subject: Re: BUG: Cygwin install on new machine: "can't run
 /etc/postinstall/openssl.sh: No such file"
In-Reply-To: <01baebab-0fcc-4b48-9806-d68aa3d7d0c3@dronecode.org.uk> (Jon
 Turney via Cygwin's message of "Tue, 16 Jun 2026 19:23:03 +0100")
References: <CA+1jF5oHp=u78kn+b0e-pS9QpFVJ3mLC9+kUMMG0vp+Hcor9JA@mail.gmail.com>
 <87bjdauzrq.fsf@Gerda.invalid>
 <01baebab-0fcc-4b48-9806-d68aa3d7d0c3@dronecode.org.uk>
Date: Tue, 16 Jun 2026 21:06:21 +0200
Message-ID: <877bnyuwya.fsf@Gerda.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Precedence: list
From: ASSI via Cygwin <cygwin@cygwin.com>
Reply-To: ASSI <Stromeko@nexgo.de>
Content-Type: text/plain; charset="utf-8"
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

Jon Turney via Cygwin writes:
> It does seem that both libssl1.1 and libssl3 have this file (which is
> permitted).

Oh I forgot about this wart… that only rears it's ugly head when both
packages are installed in the same run, though.  Now what pulls in
libssl1.1 still on a fresh Cygwin install?  I guess I should just rename
that script to openssl3.sh to get around that issue.

> Not sure how the logic in setup handles that case, though.

It will have renamed the sole existing file the first time it was run to
openssl.sh.done and then complain it can find it when it wants to run it
for the second package.


Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

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