public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory
Date: Sun, 04 Mar 2018 05:02:00 -0000	[thread overview]
Message-ID: <f43085cc-0b73-41c2-2b1c-fb2b6d548fbb@SystematicSw.ab.ca> (raw)
In-Reply-To: <b09ca8edbac840fb802ed788558bfc3b@merl.com>

On 2018-03-03 21:01, Robert Cohen wrote:
>> On March 3, 2018 22:11, Ken Brown wrote:
>> On 3/3/2018 10:01 PM, Robert Cohen wrote:
>>>    Thanks for finding that. However, I am using the same "Local Package Directory" that I used
>>> when I ran it to do the download. For example, here's where things were for all the steps:
>>>
>>> 1. Directory C:\Updates\cygwin_download, containing setup-x86_64.exe and nothing else
>>> 2. Ran setup, "Download without installing", specifying C:\Updates\cygwin_download as
>>>        the local package directory, then selected additional packages and performed the download.
>>>
>>> at this point, C:\Updates\cygwin_download contained setup-x86_64.exe and a
>>> subdirectory for the mirror site. The setup.ini file was in a x64_64 subdirectory
>>> under the mirror site subdirectory.
>>>
>>> 3. Then I ran setup again, "Install from local directory", with C:\cygwin64 as the root directory
>>>        and C:\Updates\cygwin_download as the local package directory.
>>>
>>> Should I have specified something differently for it to detect the additional packages that I
>>> selected for download? I looked in setup.ini and it does list the additional packages that
>>> I had selected.
>>
>> No.  Based on what you said, I don't know what the problem was.  Does 
>> /var/log/setup.log.full give any clues?

> I checked the log file, and it appears to have found the .ini file, and then 
> it ran a solver. Here's a portion of setup.log.full:
> ...
> 2018/03/03 22:13:47 Selected local directory: C:\Updates\cygwin_download
> Found ini file - C:\Updates\cygwin_download/http%3a%2f%2fcygwin.mirror.constant.com%2f/x86_64/setup.ini
> .ini setup_version is 2.889, our setup_version is 2.889
> 2018/03/03 22:13:49 io_stream_cygfile: fopen(/etc/setup/installed.db) failed 2 No such file or directory
> 2018/03/03 22:14:16 solving: 36 tasks, update: yes, use test packages: no
> libsolv: solver started
> ...
> 
> Later it said "libsolv: 69 installed packages:", which appeared just to be the default preselected packages.
> The log mentions nothing about my additionally selected packages.
> 
> I also looked at the logfile on another computer which used the older setup 2.880. In that log,
> after finding the .ini file, it added some dependencies and checked the SHA512 for some files,
> and those files included the extra ones that I had selected. The 2.880 setup file had no messages from
> libsolver.
> 
> One other difference I noticed was right at the beginning of the logfiles:
> 
> 2018/03/03 22:13:12 Starting cygwin install, version 2.889
> 2018/03/03 22:13:12 User has backup/restore rights
> 2018/03/03 22:13:12 Current Directory: C:\Updates\cygwin_download\http%3a%2f%2fcygwin.mirror.constant.com%2f\x86_64
> 
> vs.
> 
> 2017/06/20 18:42:33 Starting cygwin install, version 2.880
> 2017/06/20 18:42:33 User has backup/restore rights
> 2017/06/20 18:42:33 Current Directory: E:\Updates\cygwin_install
> 
> In both cases, I ran the setup executable from C:\Updates\cygwin_download, yet the "Current Directory"
> reported by the logfiles differ. 
> 
> Could the problem be related to the difference in "Current Directory", or perhaps related to the solver 
> or to whatever in the new setup program parses the setup.ini file once it's found?

Could you please provide the complete 2.889 setup.log.full as a text attachment
for inspection? That may allow us to see if it found all your cached packages,
and did not use them, or skipped them.

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

  reply	other threads:[~2018-03-04  5:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03 23:00 Robert Cohen
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 [this message]
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=f43085cc-0b73-41c2-2b1c-fb2b6d548fbb@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).