X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org X-IronPortListener: Outbound_SMTP Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Im having a problem downloading version 1.5.25-15 having something to do with setup.ini.sig Date: Fri, 15 Aug 2008 17:24:14 -0400 Message-ID: <31DDB7BE4BF41D4888D41709C476B6570929B30B@NIHCESMLBX5.nih.gov> In-Reply-To: <00ad01c8feef$bb70a660$9601a8c0@CAM.ARTIMI.COM> References: <19000930 DOT post AT talk DOT nabble DOT com> <00ad01c8feef$bb70a660$9601a8c0 AT CAM DOT ARTIMI DOT COM> From: "Buchbinder, Barry (NIH/NIAID) [E]" To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m7FLPSe5009206 Dave Korn wrote on Friday, August 15, 2008 11:58 AM: > Garret wrote on 15 August 2008 16:45: > >> I am using the cygwin setup.exe ultimately to use GRASS on my windows >> machine. the problem I am getting is with the setup.ini.sig file. I >> have attached an image of the exact error message I am getting. It >> seems to abort the grass packages download. >> http://www.nabble.com/file/p19000930/grass_error.JPG grass_error.JPG >> >> I had downloaded GRASS via cygwin earlier this year and it seemed to >> work just fine. So this is a new problem, and after looking at a few >> mirror sites and seeing that this file setup.ini.sig was updated a >> few >> days ago that has lead me to believe that this file has a problem >> with GRASS. >> >> any clues? > > Yep: setup.exe now (by default) checks for and tries to validate a > GPG signature file to make sure the mirror isn't damaged or > malicious. If you're installing from a non-official mirror site, it > won't have the signature (since it won't have the Cygwin signing > key). There are command-line options that we can use to enable > mirror maintainers to distribute keys to their users for use with > setup.exe, but for now, you want to invoke setup using the "-X" > command-line option, which you can do either by invoking setup.exe > from a cmd shell, or by making a shortcut to it in windows explorer > and adding "-X" to the end of the "Target" field in the properties. This has been on my mind, actually, for a while now. (Note that, with the possible exception of cygports, it will not make any difference to me. So these are suggestions, not requests.) It would seem that when setup encounters the error that Garret encountered, it should ask whether to continue anyway (i.e., invoke -X) or abort. If nothing else, it will avoid some of emails to the list that repeats Garret's report. It would also seem that a checkbox that invokes the -X functionality would offer flexibility to people who know in advance that there is no sig but do not remember the option don't need to use -X often enough to have a shortcut, etc. Related #1: -X (and -K, -S, -u, and -U?) might be added to FAQ entry on setup command-line usage: http://cygwin.com/faq/faq-nochunks.html#faq.setup.cli. A link to http://www.cygwin.com/ml/cygwin-announce/2008-08/msg00001.html might be appropriate. Related #2: It would be useful to update the setup command-line usage link on http://sourceware.org/cygwin-apps/setup.htm to perhaps point to the FAQ entry. And thanks for all the work that's gone into setup. - Barry - Disclaimer: Statements made herein are not made on behalf of NIAID. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/