X-Recipient:	archive-cygwin AT delorie DOT 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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type:content-transfer-encoding;
	q=dns; s=default; b=kYkAIPctKsQn7J7FwvcS0iHdmCWguiXa9H3x6VLjvpZ
	LdgairwIZsy74AgcGPUIyMv26ggQ4OGX+Up0frwAqG3QEXZs3dsULpOIjxXvGnIs
	vXdqqGTieRF/yPkdTD2Gan7rQxEXpZIFUyrsbLeVKo49DwF/plalC88Sze6VLR3M
	=
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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type:content-transfer-encoding;
	s=default; bh=nyp51MIyAydRXWkRuSrfZ2LALWg=; b=iuaEd7+wS+S7hA+0/
	+Qcl/WsyFVBYqlz+LxpzG39/zoB0ERmjbrnLeN9oguMEJQJrEPwt8hh7pIGRmzWV
	0CJ5XPcPDFpuDLAIGh55GJzAKfpK7fqdtyGuym40PybYiY6KkoI+Hg65fwFpyz1T
	zTMGDnjE4H2nS8Os6qVIDeBX4o=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=0.3 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW,SPF_PASS,UNSUBSCRIBE_BODY autolearn=no version=3.3.2 spammy=msg00136html, UD:msg00136.html, msg00136.html, stages
X-HELO:	mail-in-16.arcor-online.net
X-DKIM:	Sendmail DKIM Filter v2.8.2 mail-in-05.arcor-online.net 3rkCgG5WT2zVyH
From:	Achim Gratz <Stromeko AT nexgo DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Re: Autorebase hangs on install
References:	<CALAhKMyJgwZ+=7m9RDNP+eGoDTkbKi7xV6uCHhg4c4KLcns+Mg AT mail DOT gmail DOT com>
Date:	Tue, 05 Jul 2016 07:51:18 +0200
In-Reply-To:	<CALAhKMyJgwZ+=7m9RDNP+eGoDTkbKi7xV6uCHhg4c4KLcns+Mg@mail.gmail.com> (Jack Bartley's message of "Mon, 4 Jul 2016 22:05:58 +0100")
Message-ID:	<87r3b87hux.fsf@Rainer.invalid>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)
MIME-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id u655pnuo032757

Jack Bartley writes:
> For the first time, I tried installing the 64-bit Cygwin on my Windows
> 7 machine using the setup-x86_64.exe. Once I reach
> '/etc/postinstall/0p_000_autorebase.dash' the installation gets stuck.
> I haven't waited at this stage for more than a few hours but I have
> not got past it.

The longest I have personally witnessed was a little over one hour, so
that would indicate you have some BLODA interfering with the rebasing.
More specifically I suspect some real-time virus scanner in which case
you should create an exception for the Cygwin installation directory or
temporarily disable that function.

> The other entry I found to be similar is entitled "setup -
> 0p_000_autorebase.dash hangs" found
> athttps://cygwin.com/ml/cygwin/2015-06/msg00136.html. Following a
> mention of this in this conversation I ended bash processes whilst
> running the setup and found that this enabled me to pass the
> Autorebase stage.

There isn't any bash process running when autorebase is happening.  I'm
going to assume you meant dash for the moment.

> However, the setup then would just hang at a later
> stages.

Yes, just randomly killing postinstall steps isn't going to help you any
further.

[…]
> I should note, that I ran step one in the Cygwin64 terminal.

That was correct.

> It's worth also pointing out that when I've tried to install new
> packages the same problem recurs. I did not save the log file the very
> first time I try to install Cygwin, but I have the log file for a more
> recent attempt. I'm happy to attach this to a future email if this
> would help. Alternatively, I could just include important parts of it
> in an email. How do I go about opening these files (those beginning
> setup.log.run, found in var/log.

The *run* files are only left there if the setup process gets aborted
somehow.  Since you say you aborted every single one, that should have
left that many of these files.  setup.log.full has the abridged logging
for all installs and setup.log is the complete log for the last
install.  They are all simple text files.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
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

- Raw text -