From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: setup 2.910 release candidate - please test
Date: Sun, 28 Nov 2021 21:53:20 +0000 [thread overview]
Message-ID: <7002686b-083f-2bd5-6b8c-f1deb04c00b3@dronecode.org.uk> (raw)
In-Reply-To: <871r303uhi.fsf@Rainer.invalid>
On 28/11/2021 20:17, Achim Gratz wrote:
> Jon Turney writes:
>> A new setup release candidate is available at:
>>
>> https://cygwin.com/setup/setup-2.910.x86_64.exe (64 bit version)
>> https://cygwin.com/setup/setup-2.910.x86.exe (32 bit version)
>>
>> Please test, and report any problems here.
>
> It should be noted that updating to this version in an existing checkout
> needs a full bootstrap due to the changes in libgetopt++ or the link
> step will fail.
To be clear, this is a problem (see [1]) that will only be seen if you
are building setup yourself from source.
[1] https://cygwin.com/pipermail/cygwin-apps/2021-October/041613.html
prev parent reply other threads:[~2021-11-28 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 17:22 Jon Turney
2021-11-28 20:17 ` Achim Gratz
2021-11-28 21:53 ` Jon Turney [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7002686b-083f-2bd5-6b8c-f1deb04c00b3@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).