From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Error Installing Cygwin (setup-x86_64.exe & setup-x86) - No setup.ini.sig found.
Date: Sat, 17 Oct 2015 22:20:00 -0000 [thread overview]
Message-ID: <5622C9C6.40200@cornell.edu> (raw)
In-Reply-To: <5622BA2F.7040205@tiscali.co.uk>
On 10/17/2015 5:14 PM, David Stacey wrote:
> On 17/10/15 13:13, Ken Brown wrote:
>> On 10/17/2015 3:28 AM, Achim Gratz wrote:
>>> Ken Brown writes:
>>>>> Could you check if the setup.ini.sig file is just not stored to disk and
>>>>> that setup would commence installing if you downloaded it manually and
>>>>> put alongside the setup.ini file?
>>>>
>>>> Is there a new requirement that a local repository has to have a
>>>> signature file? And does it have to be setup.ini.sig (rather than,
>>>> for example, setup.bz2.sig)?
>>>
>>> You can always tell it to not check the signature (--no-verify / -X),
>>> but if the directory you set it upon looks like a mirror and has a setup
>>> file, then it will by default want to check the signature (belonging to
>>> the actual suffix used: .xz, .bz2 and lastly .ini).
>>
>> I maintain my own small repository at a remote site and mirror it on my local
>> machine. It contains, for each architecture, setup.ini, setup.xz, and
>> setup.xz.sig. Installation from the remote site works fine. If I try to
>> install from my local mirror, setup complains that it can't find
>> setup.ini.sig. I can install from the local mirror only if I add setup.ini.sig.
>
> Same here. I maintain a local mirror and use my own setup.ini files (created
> with genini); these do not have 'sig' files. Directory structure is as follows:
>
> cygwin-2015-10-16
> /cygwin
> /x86
> /x86_64
> /cygwinports
> /noarch
> /x86
> /x86_64
>
> The 'setup.ini' files are located in the 'x86' and 'x86_64' directories; setup
> is pointed at the 'cygwin-2015-10-16' directory. Eventually managed to install
> using an older version of setup that I had downloaded previously.
Thanks for the confirmation, Dave. Since Achim can't reproduce the problem,
maybe we should temporarily forget about local mirrors and go back to the
simpler situation reported by the OP. I just reproduced that problem in a
simpler form as follows:
1. Download setup-x86.exe from the Cygwin website, and put it in an empty
directory c:/download-test.
2. Run setup-x86.exe. Choose "Install from Internet". Choose the nonexistent
c:\cygwin-test as root directory. Choose c:/download-test as local package
directory. Choose http://mirrors.kernel.org as the only download site.
Repeatedly click "Next" while setup does a base install.
At this point, the download directory looks like this:
download-test
setup-x86.exe
http%3a%2f%2fmirrors.kernel.org%2fsourceware%2fcygwin%2f
x86
setup.ini
release
_autorebase
...
3. Run setup-x86.exe again, this time choosing "Install from Local Directory".
setup complains that it can't get
c:/download-test/http%3a%2f%2fmirrors.kernel.org%2fsourceware%2fcygwin%2f//x86/setup.ini.sig
from <localdir>. [This is the first bug; if setup expects to find signature
files in local directories, it should save the ones it downloads.]
4. Retry, this time using setup-x86.exe -X. The "Select Packages" screen lists
all the installed packages, but for each package the only options are "Keep" and
"Uninstall". [This is the second bug; setup has apparently failed to descend
into http%3a%2f%2fmirrors.kernel.org%2fsourceware%2fcygwin%2f.]
5. Repeat, but this time change the local package directory from the default
c:/download-test to
c:/download-test/http%3a%2f%2fmirrors.kernel.org%2fsourceware%2fcygwin%2f. Now
each package has the additional option "Reinstall" (which works).
Achim, can you reproduce this? Please use the official setup-x86.exe rather
than the one you built, in case your local setup repo is somehow different from
the upstream repo.
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:[~2015-10-17 22:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 14:21 Robert Pace
2015-10-16 16:20 ` Andrey Repin
2015-10-16 20:53 ` Achim Gratz
2015-10-16 21:18 ` Robert Pace
2015-10-17 7:20 ` Achim Gratz
2015-10-16 21:29 ` Ken Brown
2015-10-17 7:28 ` Achim Gratz
2015-10-17 11:15 ` Nicolas Roche
2015-10-17 12:13 ` Ken Brown
2015-10-17 14:19 ` Ken Brown
2015-10-17 17:06 ` Achim Gratz
2015-10-17 18:30 ` Ken Brown
2015-10-17 19:09 ` Achim Gratz
2015-10-17 21:14 ` David Stacey
2015-10-17 22:20 ` Ken Brown [this message]
2015-10-18 2:35 ` Andrey Repin
2015-10-18 2:48 ` Ken Brown
2015-10-18 11:48 ` Achim Gratz
2015-10-18 13:20 ` Ken Brown
2015-10-18 13:31 ` Achim Gratz
2015-10-18 13:47 ` Ken Brown
2015-10-18 15:38 ` Ken Brown
2015-10-18 16:49 ` Achim Gratz
2015-10-18 15:09 ` David Stacey
2015-10-18 17:48 ` Achim Gratz
2015-10-18 23:42 ` Ken Brown
2015-10-19 6:05 ` 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=5622C9C6.40200@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).