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 18:30:00 -0000 [thread overview]
Message-ID: <562293A3.5040503@cornell.edu> (raw)
In-Reply-To: <87zizhe86j.fsf@Rainer.invalid>
On 10/17/2015 1:06 PM, Achim Gratz wrote:
> Ken Brown writes:
>>> 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.
>
> I install also from a local mirror, not signed ini files (yet) and I
> haven't had any problems. I happen to have installed a new machine just
> this week so I know this also works OK. If there is a setup.xz,
> setup.ini shouldn't even be looked at and consequently no setup.ini.xz
> file should be required.
>
>> And even then, setup doesn't seem to work right on the local mirror.
>> The only choices it gives me on the local packages are "Keep" and
>> "Uninstall".
>
> That would indicate it hasn't actually found any packages in whatever it
> used as setup.ini. What's your directory layout? I can't make any
> sense of what's happening for you. Your local mirror should look like:
>
> mirror
> /x86
> /setup.xz
> /setup.xz.sig
> /x86_64
> /setup.xz
> /setup.xz.sig
>
> and setup should be pointed at "mirror".
OK, doing it that way works. But if I add setup.ini alongside setup.xz and
setup.xz.sig, then setup complains about not finding setup.ini.sig.
Also, having to point setup at "mirror" is a major change from the way local
installs used to work. I have the following structure:
download directory
http%3a%2f%2fmirrors.kernel.org%2fsourceware%2fcygwin%2f/
http...
http...
mirror
and I have always pointed setup at "download directory" for a local install. In
the past, this would then pick up the packages from all the http directories as
well as from "mirror". Was it a deliberate change that this no longer works?
This change is probably what's behind the problem the others in this thread have
reported.
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 18:30 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 [this message]
2015-10-17 19:09 ` Achim Gratz
2015-10-17 21:14 ` David Stacey
2015-10-17 22:20 ` Ken Brown
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=562293A3.5040503@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).