public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Robert Cohen <cohen@merl.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory
Date: Sat, 03 Mar 2018 23:00:00 -0000	[thread overview]
Message-ID: <8571f617c5a740608e267364827e7733@merl.com> (raw)

Summary of problem:
When installing Cygwin from a local directory, setup-x86_64.exe version 2.889 doesn't
list the packages that I additionally selected for download when previously downloading
to that directory, and the top line of the GUI under Category view says "No packages found<->Default".
Continuing the install only installs the packages preselected by setup.

Details:
To install a fresh version of Cygwin, I usually do this: Run setup-x86_64.exe
using "Download Without Installing", select some additional packages, and then after
everything finished, I rerun setup-x86_64.exe using "Install from Local Directory",  and then
the GUI, under Category view, shows "All <-> Default", beneath which is a hierarchical
list including the packages preselected by setup along with the additional ones that I selected
when downloading.

Here's the problem: I performed the above process using today's version of setup-x86_64.exe
from cygwin.com, which according to setup.ini is setup version 2.889, and the
"Download Without Installing" setup worked as expected. However, when I next
did "Install from Local Directory" using that directory, instead of showing "All<->Default", it
showed "No packages found<->Default", and only the packages preselected by
setup were not going to be skipped. I tried changing "Default" to "Install" at the
top level of the list, but that then selected everything for install, not just the preselected
packages and the additional ones I had downloaded. I repeated this process using
a few different mirror sites for the download phase, but that made no difference.

Interestingly, if I copy an older version of setup-x86_64.exe into my already-downloaded
directory, e.g. setup-x86_64.exe version 2.880, the GUI is able to find the selected packages
that I had already downloaded using setup version 2.889, after of course giving a few warnings
about the current ini file being from a newer version of setup. In other words, if I download
using setup v2.889, then when subsequently installing from that directory, setup v2.889 doesn't
know what additional packages I had selected, whereas setup v2.880 does know.

I'm wondering if I'm not doing something correctly, or if there is an issue with version 2.889 of
setup-x86_64.exe not finding packages that were additionally selected for download.

Version details:
The  beginning of setup.ini in my download directory includes this:
release: cygwin
arch: x86_64
setup-timestamp: 1519974241
setup-version: 2.889

This was done on Windows 10 pro, using  setup-x86_64.exe v2.889 downloaded
on March 3, 2018 UTC from cygwin.com, which currently indicates that the most recent
version of the Cygwin DLL is 2.10.0.

Thanks in advance for any help.
 Robert

--
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:[~2018-03-03 23:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03 23:00 Robert Cohen [this message]
2018-03-03 23:54 ` Brian Inglis
2018-03-04  1:51   ` Robert Cohen
2018-03-04  2:16 ` Ken Brown
2018-03-04  2:32   ` Brian Inglis
2018-03-04  3:01   ` Robert Cohen
2018-03-04  3:11     ` Ken Brown
2018-03-04  4:01       ` Robert Cohen
2018-03-04  5:02         ` Brian Inglis
2018-03-04  5:26           ` Robert Cohen
2018-03-04 15:22         ` Ken Brown
2018-03-06 23:14 ` Jon Turney
2018-03-07  3:37   ` Robert Cohen
2018-03-07 12:15     ` Jon Turney
2018-03-07 20:09       ` Robert Cohen
     [not found]       ` <b03fcc59d6ed4831b4f7c9a225d14466@merl.com>
2018-03-07 20:18         ` Jon Turney
2018-03-22 21:56           ` Ken Brown
2018-03-23 16:54             ` Achim Gratz
2018-03-23 21:10               ` Ken Brown
2018-03-24  1:05                 ` Brian Inglis

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=8571f617c5a740608e267364827e7733@merl.com \
    --to=cohen@merl.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).