From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: setup 2.925 release candidate - please test
Date: Fri, 14 Apr 2023 16:29:19 +0100 [thread overview]
Message-ID: <6d0249fb-e867-2de8-63cf-f2656f665523@dronecode.org.uk> (raw)
A new setup release candidate is available at:
https://cygwin.com/setup/setup-2.926.x86_64.exe (64 bit version)
https://cygwin.com/setup/setup-2.926.x86.exe (32 bit version)
Please test, and report any problems here.
Changes compared to 2.925:
- Add some resilience against transient errors when reading files from
the local package cache, as can occasionally happen when it resides on a
network filesystem (thanks to Corinna Vinschen)
- Fix reinstall via command line (thanks to Bill Stewart for helping to
identify this is a regression in 2.919)
Addresses: https://cygwin.com/pipermail/cygwin/2023-March/253352.html
- Translation updates.
- Add a link to translation website on splash page
- Add a tooltip to the additional site textbox and extend '--site' help
text to indicate that 'site' can also be specified by a path or UNC
path, as well as a URL.
Replies to this message are not the place for setup feature requests.
For instructions on obtaining and building the source code for setup,
see https://sourceware.org/cygwin-apps/setup.html
Please send bug reports, as usual, to the public mailing list cygwin AT
cygwin DOT com.
next reply other threads:[~2023-04-14 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 15:29 Jon Turney [this message]
2023-04-14 19:12 ` Marco Atzeri
2023-04-15 15:03 ` Andrey Repin
2023-04-14 19:28 ` Jon Turney
2023-07-27 2:35 ` setup 2.926 " Bill Stewart
-- strict thread matches above, loose matches on Subject: below --
2023-02-02 14:00 setup 2.925 " Jon Turney
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=6d0249fb-e867-2de8-63cf-f2656f665523@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).