From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Cygwin command line download issue
Date: Wed, 23 Oct 2019 12:34:00 -0000 [thread overview]
Message-ID: <95a752cf-dd90-0b7b-3bc0-e1ae45f97e5d@cornell.edu> (raw)
In-Reply-To: <857c6c30-9e8c-5142-43dd-d71e63a68fb6@cornell.edu>
On 10/22/2019 8:33 PM, Ken Brown wrote:
> [Please don't top-post on this list.]
>
> On 10/22/2019 3:42 PM, Jim Rather wrote:
>> I only get two lines in setup.log.full with regards to crypto-policies
>>
>> Found category Base in package crypto-policies
>> Added manual package crypto-policies
>
> setup.log.full contains information only about the most recent run of setup.
> That's why I suggested looking in both setup.log and setup.log.full.
>
>> I am confused, this script has worked faithfully for at least a year. I just emptied by %cyg_dir% and re-ran it. Afterwards, I am missing many basic packages like alternatives, bash, etc. so I am not sure what has changed and welcome any suggestions.
>
> Once again, setup.log and setup.log.full should provide some clues.
One other thing: I notice that your setup command line doesn't set the
installation root directory. By default, setup will use whatever root it used
on its last run. So if you previously used setup to install Cygwin, setup will
look at /etc/setup/installed.db to see what you have installed. It won't
re-download the installed packages.
If you want to force download, I think you need to use --root to specify a
directory in which Cygwin is not already installed.
Ken
--
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
next prev parent reply other threads:[~2019-10-23 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 17:12 Jim Rather
2019-10-22 18:52 ` Ken Brown
2019-10-22 19:42 ` Jim Rather
2019-10-23 0:33 ` Ken Brown
2019-10-23 12:34 ` Ken Brown [this message]
2019-10-23 15:33 ` Jim Rather
2019-10-23 16:49 ` Ken Brown
2019-10-23 17:13 ` Jim Rather
2019-10-23 18:12 ` 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=95a752cf-dd90-0b7b-3bc0-e1ae45f97e5d@cornell.edu \
--to=kbrown@cornell.edu \
--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).