From: Jon Turney <jon.turney@dronecode.org.uk>
To: Christian Franke <Christian.Franke@t-online.de>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: setup 2.920 release candidate - please test
Date: Sun, 14 Aug 2022 19:56:49 +0100 [thread overview]
Message-ID: <ef5e969f-56fb-3a4a-c353-8c0637e1f1ad@dronecode.org.uk> (raw)
In-Reply-To: <a55e0852-0ba2-3f9a-bb82-acc1dfca2c16@t-online.de>
On 14/08/2022 13:38, Christian Franke wrote:
> Jon Turney wrote:
>>
>> A new setup release candidate is available at:
>>
>> https://cygwin.com/setup/setup-2.920.x86_64.exe (64 bit version)
>> https://cygwin.com/setup/setup-2.920.x86.exe (32 bit version)
>>
>> Please test, and report any problems here.
>>
>
> This version aborts if "Sync" setting is reverted to "Best".
>
> Steps to reproduce:
> - Install from Internet
> - For All Users
> - Use System Proxy Settings
> - Mirror: any
> - Change "Best" -> "Sync"
> - Change "Sync" -> "Best"
>
> Result: Setup silently aborts, no setup.log* written.
Thanks for the clear reproduction steps. I had reports that this setup
version crashes, but nothing to investigate...
[....]
> libsolv: pkg rule creation took 0 ms
> ---
>
> Could not be reproduced with the released cygwin*.exe 2.919 from
> https://cygwin.com/
>
> Could also be reproduced with
> - 32-bit version
> - current git HEAD
> - a rebuild of 2.919 from "git checkout release_2.919"
>
> Possible problem in conjunction with newer versions Mingw-w64 toolchain ?
It's very likely caused by the long overdue libsolv update in that build.
prev parent reply other threads:[~2022-08-14 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 14:37 Jon Turney
2022-08-14 12:38 ` Christian Franke
2022-08-14 16:47 ` Achim Gratz
2022-08-14 19:00 ` Jon Turney
2022-08-15 8:18 ` Christian Franke
2022-08-14 18:56 ` 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=ef5e969f-56fb-3a4a-c353-8c0637e1f1ad@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Christian.Franke@t-online.de \
--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).