From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] lz4 1.7.5-1
Date: Sun, 01 Oct 2017 18:54:00 -0000 [thread overview]
Message-ID: <80e15d3e-db8b-1384-2e1a-b172e6b07468@SystematicSw.ab.ca> (raw)
In-Reply-To: <553d0edf-2de0-316f-ee7f-0d0fc2753e8c@cegetel.net>
On 2017-10-01 10:31, S. Loiseau wrote:
> On Sun, 03 Sep 2017 21:02:44 -0500, Yaakov Selkowitz wrote:
>> The following packages have been uploaded to the Cygwin distribution:
>>
>> * liblz4_1-1.7.5-1
>
> My setup-x86_64 (version 2.881 from 2017-07-05) does not upgrade to this new
> version.
> My liblz4_1 is at version 131-1 and setup propose to "Keep" it. It does not
> appear on "Pending" view.
>
> Maybe some comparison inside setup.exe think that "1.7.5-1" <= "131-1" ?
>
> Other updates were proposed and executed.
> Version 1.7.5-1 is proposed by clicking 3 times on "Keep" (after "Reinstall"
> and "Uninstall").
>
> Below the setup.ini part, showing 1.7.5-1 as "Current" and 131-1 as "Prev"
>
> # This file was automatically generated at 2017-09-30 05:38:39 UTC.
> release: cygwin
> arch: x86_64
> setup-timestamp: 1506749919
> setup-version: 2.881
>
> @ liblz4_1
> sdesc: "LZ4 de/compressor"
> version: 1.7.5-1
> install: x86_64/release/lz4/liblz4_1/liblz4_1-1.7.5-1.tar.xz 30408
> source: x86_64/release/lz4/lz4-1.7.5-1-src.tar.xz 210608
> [prev]
> version: 131-1
> install: x86_64/release/lz4/liblz4_1/liblz4_1-131-1.tar.xz 17924
> source: x86_64/release/lz4/lz4-131-1-src.tar.xz 136668
Version number format changes often require manual intervention to upgrade, as
in this case.
> Output of cygcheck -s -r -v attached.
>
> Thank you for the great tool!
Cygwin setup developers are testing a new upgrade approach.
Can any of the setup developers comment on whether that will fix this issue?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-10-01 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 16:31 S. Loiseau
2017-10-01 18:54 ` Brian Inglis [this message]
[not found] <auto-000003744910@fwd2.webnames.ca>
2018-02-27 1:20 ` Brian Inglis
2018-02-27 6:12 ` Yaakov Selkowitz
2018-02-27 22:01 ` Jon Turney
-- strict thread matches above, loose matches on Subject: below --
2017-09-04 2:05 Yaakov Selkowitz
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=80e15d3e-db8b-1384-2e1a-b172e6b07468@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).