public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Subject: Re: setup 2.883 release candidate - please test
Date: Tue, 12 Dec 2017 06:53:00 -0000	[thread overview]
Message-ID: <5a2f2229.46e8ca0a.8b93c.4c34@mx.google.com> (raw)
In-Reply-To: <f540232e-0e05-b6fc-fb74-824c3198a177@dronecode.org.uk>

On Mon, 11 Dec 2017 18:46:30, Jon Turney wrote:
> A new setup release candidate is available at:
> 
>    https://cygwin.com/setup/setup-2.883.x86.exe    (32 bit version)
>    https://cygwin.com/setup/setup-2.883.x86_64.exe (64 bit version)
> 
> Please test and report problems to cygwin@cygwin.com. If no regressions 
> are discovered in the next week or so, it will be promoted to release.

Here is an old issue - say you go to install a package, but your download is
corrupt. You get this:

    ---------------------------
    Cygwin Setup
    ---------------------------
    Package file wget has a corrupt local copy, please remove and retry.
    ---------------------------
    OK   
    ---------------------------

*Then setup closes*. This is not right. If the archive is missing, or if the
archive fails the SHA check, *then the file should be redownloaded by setup*,
and SHA check run again. With the current system, setup exits, then the user has
to navigate to where the problem file is, for example:

C:\http%3a%2f%2fcygwin.mirror.constant.com%2f\x86_64\release\wget

then delete the problem file, then restart setup. I cant see why setup shouldnt
just automate all of this. Also here is a new issue - on the "Select Connection
Type" page - "Use System Proxy Settings" is the first choice, and by default the
selected choice. "Direct Connection" should be the first choice, and by default
the selected choice.


--
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

  reply	other threads:[~2017-12-12  0:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 21:11 Jon Turney
2017-12-12  6:53 ` Steven Penny [this message]
2017-12-12 14:15   ` Ken Brown
2017-12-13  4:09     ` Steven Penny
2017-12-13  5:21       ` Vince Rice
2017-12-13  7:50         ` cyg Simple
2017-12-13 14:33           ` Ken Brown
2017-12-15  0:32 ` Achim Gratz

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=5a2f2229.46e8ca0a.8b93c.4c34@mx.google.com \
    --to=svnpenn@gmail.com \
    --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).