From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Preremove/postinstall scripts fail with snapshot installed
Date: Sat, 12 Feb 2011 12:09:00 -0000 [thread overview]
Message-ID: <87fwrtbgkt.fsf@Rainer.invalid> (raw)
In-Reply-To: <4D55A88E.3090301@cornell.edu>
Ken Brown <kbrown@cornell.edu> writes:
> If I run setup.exe with a cygwin snapshot installed, bash crashes
> while running all preremove and postinstall scripts. Here's a typical
> error message in /var/log/setup.log.full:
I'm getting similar crashes running Git fetch on a snapshot installation
on Win7 I did a few weeks ago while trying to figure out my problem with
named pipes. I did not change the Cygwin installation since then (which
went fine at the time) and Git was running OK (cloned a few repos, the
ones that now have a problem updating). If I run the fetch a few times
it will eventually complete, though. There was a patchday inbetween,
however... also it wouldn't be the first time that some Cygwin program
was deemed "malicious" by behavioral virus scanners.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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:[~2011-02-12 12:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 21:22 Ken Brown
2011-02-12 0:26 ` Ken Brown
2011-02-12 12:09 ` Achim Gratz [this message]
2011-02-12 14:26 ` Corinna Vinschen
2011-02-12 14:58 ` Ken Brown
2011-02-12 15:31 ` Ken Brown
2011-02-12 16:44 ` Corinna Vinschen
2011-02-12 18:12 ` Corinna Vinschen
2011-02-12 22:05 ` Christopher Faylor
2011-02-13 16:25 ` Corinna Vinschen
2011-02-13 17:20 ` Ken Brown
2011-02-13 23:07 ` Ken Brown
2011-02-14 9:21 ` Corinna Vinschen
2011-02-14 16:41 ` Corinna Vinschen
2011-02-15 17:09 ` Corinna Vinschen
2011-02-15 17:29 ` Ken Brown
2011-02-13 17:43 ` Andy Koppe
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=87fwrtbgkt.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).