From: Patrick Jane <brentboyer@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Regression with 1.7.20-1
Date: Wed, 24 Jul 2013 00:46:00 -0000 [thread overview]
Message-ID: <loom.20130723T225553-902@post.gmane.org> (raw)
In-Reply-To: <20130711172026.GB7515@ednor.casa.cgf.cx>
Christopher Faylor <cgf-use-the-mailinglist-please <at> 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
next prev parent reply other threads:[~2013-07-23 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 1:06 Steven Penny
2013-06-10 8:06 ` Csaba Raduly
2013-06-10 8:28 ` Steven Penny
2013-06-10 8:58 ` Corinna Vinschen
2013-07-11 17:05 ` Patrick Jane
2013-07-11 18:56 ` Christopher Faylor
2013-07-24 0:46 ` Patrick Jane [this message]
2013-06-10 13:58 ` Christopher Faylor
2013-06-10 14:38 ` Steven Penny
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=loom.20130723T225553-902@post.gmane.org \
--to=brentboyer@gmail.com \
--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).