Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID:	<010f01c2bef1$d9bb6d10$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	<news AT garydjones DOT mailshell DOT com>, <cygwin AT cygwin DOT com>
References:	<E18Zp6M-0006E0-00 AT clustermail DOT minx DOT net DOT uk>
Subject:	Re: setup errors
Date:	Sat, 18 Jan 2003 13:02:26 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

news AT garydjones DOT mailshell DOT com wrote:
> I encountered a couple of problems updating my installation this
> morning. I use the download option, and then run setup again
> with the "Install from Local Directory" option to actually
> update Cygwin. Setup.exe version 2.249.2.5.
>
> While performing the latter stage, I got an error saying "Can't
> open (null) for reading: no such file" (I know, I've seen a
> number of messages in the archives about this, though not a
> clear explanation of what it really means).

Essentially, setup mishandled its own internal datastructures.

Unfortunately, no one has been able to work out how to consistently
reproduce this, which makes debugging a challenge to say the least.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -