public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Possible setup-x86_64 2.908 bugs?
Date: Thu, 29 Apr 2021 18:10:15 +0100	[thread overview]
Message-ID: <a0488465-ca48-6e4a-a4db-f4708897f5b2@dronecode.org.uk> (raw)
In-Reply-To: <9604e283-fa0c-220f-a687-dbe3e5743452@jhmg.net>

On 29/04/2021 17:41, Jim Garrison via Cygwin wrote:
> I got the "newer version" prompt just now when running setup and
> downloaded 2.908 (I was on 2.905).
> 
> Now I'm seeing really flaky behavior in 2.908
> 
[...]
> 
> * "This version of setup is *older* than the one you used last time"


I guess the message here is "setup.ini is older than the one you used 
last time you installed cygwin."

This indicates that (setup thinks that) the timestamp in the retrieved 
setup.ini file has gone backwards.

(determined by comparing the value saved in /etc/setup/timestamp with 
that given by the setup-timestamp: line close to the beginning of setup.ini)

>   Does not happen the first time the new setup is launched, but then
>   occurs intermittently thereafter.  I saw that message on two
>   occasions, and the second time setup-x86_64.exe crashed a few
>   seconds later. No message, the window just closed after I dismissed
>   the message popup.
> 
>   Note: When I downloaded the new setup-x86_64.exe I overwrote the
>   old one, so there's no chance (barring an OS caching bug) I was
>   running 2.905 at that point.

There haven't really been any setup changes in the relevant area.

The only thing I can think of is that it's possible that your mirror URL 
might have been upgraded from http to https, which might effect how any 
proxy you are behind is working.

Some old setup versions are available at [1], if you want to downgrade.

[1] https://cygwin.com/setup/

      reply	other threads:[~2021-04-29 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 16:41 Jim Garrison
2021-04-29 17:10 ` 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=a0488465-ca48-6e4a-a4db-f4708897f5b2@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).