From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: setup with experimental libsolv-based dependency solving
Date: Thu, 18 Jan 2018 19:15:00 -0000 [thread overview]
Message-ID: <222e08ca-5ab9-cbf7-7d07-13a8a96c0d0b@dronecode.org.uk> (raw)
In-Reply-To: <7d047b10-eb43-9f62-f724-85f6f5ebb776@dronecode.org.uk>
On 23/11/2017 18:08, Jon Turney wrote:
> On 30/10/2017 15:52, Jon Turney wrote:
>> On 25/10/2017 20:18, Jon Turney wrote:
>>>
>>> This has a lot of internal changes, so could use some wider testing.
>>> Please test.
> [...]
>> I've replaced these with:
> [...]
> I've replaced these with:
[...]
I've replaced these with:
https://cygwin.com/setup/setup-2.884-45-gb87162.x86.exe
https://cygwin.com/setup/setup-2.884-45-gb87162.x86_64.exe
Changes compared to setup-2.882-62-g75a2e0:
libsolv related:
- When test versions are enabled, a test version is no longer preferred
over a non-test version with a higher version
- Default solutions are now identified in the problem report, and
applied if the user chooses to accept them
- Meaningless '.any' arch suffix to package names is suppressed in the
problem report
- Reinstall tasks are preserved in the chooser when going back from the
dependency problem page
other:
- Query the user for action to take if a corrupt local file is found
- Validate package hash after download
- Rebase to include changes in 2.883 and 2.884
I'm interested in opinion on what else is needed, before this can be
released as 2.885
next prev parent reply other threads:[~2018-01-18 19:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 19:19 Jon Turney
2017-10-26 5:41 ` Achim Gratz
2017-10-26 12:06 ` Jon Turney
2017-10-26 17:36 ` Achim Gratz
2017-10-27 18:57 ` Ken Brown
2017-10-27 19:52 ` Ken Brown
2017-10-28 12:31 ` Ken Brown
2017-10-29 17:26 ` Jon Turney
2017-10-30 15:52 ` Jon Turney
2017-11-23 18:08 ` Jon Turney
2018-01-18 19:15 ` Jon Turney [this message]
2018-01-22 17:54 ` Ken Brown
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=222e08ca-5ab9-cbf7-7d07-13a8a96c0d0b@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@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).