X-Recipient: archive-cygwin@delorie.com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=Muc0wGLwXRHt1YAwwOHppoNx7rICNm3pCAwS7TzUymkDSEluChr68 FWiYoaYR8ajeZkg4osKAMJcAf+Npc3xY6GxsliZFLdVQHGk/Lmgy0PK5yjWGbyTU xv7qS3YK4WEyEA2Iq7pHISCVQT4JpEhYAP0zfreC5JPzker6xqBBvc= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type:content-transfer-encoding; s=default; bh=ncOFALXCqdwJ70Yhp4CulE+h1Q4=; b=h6d8fg7eolVqkxqDCU7Y38YursXV 8+pBZVDx3EC6/mdgZVetEqKCac4goPUec/JA/VgzYnJAT1bUTMvPJN6iVd2fTGCW KINNIaYbXAbBiv32ziUZmX9XpqWXM2vt048XVcF4kyYbkovi4q7ZwI+ykObqAiln b5GlaSVnrnRbIu8= Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RDNS_NONE,SPF_HELO_PASS,SPF_PASS,TW_CG autolearn=no version=3.3.1 To: cygwin@cygwin.com From: Patrick Jane Subject: Re: Regression with 1.7.20-1 Date: Tue, 23 Jul 2013 21:33:05 +0000 (UTC) Lines: 44 Message-ID: References:

<20130610085849.GC28431@calimero.vinschen.de> <20130711172026.GB7515@ednor.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) Christopher Faylor cygwin.com> writes: > There is no reason to be nervous about installing snapshots if you think > a new release will solve a problem. A snapshot potentially always > equals a new release. Snapshots never break things so severely that you > can't recover by just reinstalling cygwin. I checked out the FAQ on snapshot installation http://www.cygwin.com/faq.html#faq.setup.snapshots and it looks to be enough pain that I want to stick with setup.exe, if at all possible. (I custom install several extra packages beyond the base installation, but don't want to install all, and I really like how setup.exe has memory of that.) > And, yes, you should follow cygwin or cygwin-announce for update announcements. 1.7.21 came out last week http://cygwin.com/ml/cygwin-announce/2013-07/msg00017.html but I do not see a ctrl-c fix in it. Even better, 1.7.22 just came out yesterday http://cygwin.com/ml/cygwin-announce/2013-07/msg00030.html and I see this tantalizing bug fix: - Fix issue with raise() not causing the process to exit with a signal status. Also only set "dumped core" flag when it's a "kernel" signal. See: http://cygwin.com/ml/cygwin-apps/2013-07/msg00251.html That sounds a lot like a fix for the Ctrl-C bug discussed here. I will gladly install 1.7.22 (heck, I will likely deinstall everything and try the 64 bit version) to check out if it fixes the bug if there is an easy way that I can go back to 1.7.18 using setup.exe. I am having a bit of a hard time, however, finding a mirror that has 1.7.18 and which works with setup.exe. Some candidate I tried: http://mirrors.xmission.com/cygwin/release/cygwin/ http://mirror.isoc.org.il/pub/cygwin/release/cygwin/ http://www.fruitbat.org/Cygwin/index.html#cygwinmirror Unfortunately, every time I try to run setup.exe and add one of the above mirrors I get an error message saying something about "Unable to get setup.ini". If anyone else has seen 1.7.22 fix their Ctrl-C bug, I will take your word for it and try 1.7.22 myself. -- 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