From: Jon Turney <jon.turney@dronecode.org.uk>
To: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: setup (2.917)
Date: Fri, 28 Jan 2022 14:56:34 +0000 [thread overview]
Message-ID: <03a35c82-6347-fcdf-8f53-751ca573d959@dronecode.org.uk> (raw)
In-Reply-To: <575a2721-8331-5edd-09d5-a67aa7e04af7@shaddybaddah.name>
On 27/01/2022 07:28, Shaddy Baddah wrote:
> Hi,
>
>
> On 25/1/22 7:02 am, Jon Turney wrote:
> > A new version of Setup (2.917) has been uploaded to:
> >
> > https://cygwin.com/setup-x86_64.exe (64 bit version)
> > https://cygwin.com/setup-x86.exe (32 bit version)
> >
> > Changes compared to 2.915:
> ...
>
> I've had a new problem with this version, which I have been able to
> work around.
I guess this means 2.915 didn't have this problem.
> I normally do a two stage update of Cygwin, with the second stage
> being running down the "Install from Local Directory" path.
>
> This was silently existing. As it turned out, it was doing so as I had
> an old, setup.ini from a mirror I had unintentionally selected (rather
> than my preferred mirror). Here's the preamble to that setup.ini:
>
[...]
>
> I moved that out of the way, and then was able to proceed.
>
> I was fortunate that I acted on a hunch. Otherwise, even with -v on
> command line, there was nothing that could indicate to me what was
> causing the issue.
>
> I'm hoping that this silent exit can be fixed, to at least give an
> indication, via logging or pop-up or other, of what is blocking the
> install.
Thanks for reporting this.
This seems to be a crash which occurs if you're not using 'download and
install' mode, and have cached setup.ini files from multiple mirrors,
and those differ in if any install package for a given source package is
available.
I've uploaded an updated setup with an attempted fix for this:
https://cygwin.com/setup/setup-2.917-3-g489d9c.x86_64.exe
https://cygwin.com/setup/setup-2.917-3-g489d9c.x86.exe
Perhaps you could try that and see if it improves things for you?
Thanks.
next prev parent reply other threads:[~2022-01-28 14:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 20:02 Jon Turney
2022-01-27 7:28 ` Shaddy Baddah
2022-01-28 14:56 ` Jon Turney [this message]
2022-01-31 3:06 ` Shaddy Baddah
2022-01-31 5:36 ` © Fxzx mic
2022-01-31 6:25 ` Marco Atzeri
2022-01-31 6:43 ` © Fxzx mic
2022-01-31 8:20 ` Samuel Lelièvre
2022-01-31 12:13 ` Jon Turney
2022-01-31 15:46 ` Andrey Repin
2022-01-31 19:56 ` Brian Inglis
2022-01-24 22:49 Buchbinder, Barry (NIH/NIAID) [E]
2022-01-24 23:12 ` Bill Stewart
2022-01-25 22:33 Buchbinder, Barry (NIH/NIAID) [E]
2022-01-26 8:47 ` Adam Dinwoodie
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=03a35c82-6347-fcdf-8f53-751ca573d959@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=lithium-cygwin@shaddybaddah.name \
/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).