X-Spam-Check-By: sourceware.org
Message-ID: <4578DD2D.4080109@byu.net>
Date: Thu, 07 Dec 2006 20:34:05 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061025 Thunderbird/1.5.0.8 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Alexei Alexandrov <alexei DOT alexandrov AT gmail DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: Latest Cygwin: rl_getenv_hook problem
References: <98a8c95d0612062318k6d33e444i45adbd01d0aa757a AT mail DOT gmail DOT com>	 <4578169A DOT 5030705 AT byu DOT net>	 <98a8c95d0612070534w29fe312em8a96512322a1f03b AT mail DOT gmail DOT com>	 <457821BF DOT 8070301 AT byu DOT net> <98a8c95d0612070832x774f6e2bj9b1c5cbd58475302 AT mail DOT gmail DOT com>
In-Reply-To: <98a8c95d0612070832x774f6e2bj9b1c5cbd58475302@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Alexei Alexandrov on 12/7/2006 9:32 AM:
>>
>> Also, could you send the output of:
>>
>> $ grep -C5 00bash.sh /var/log/setup.log/full
>>
>> to see if it captured any error messages from the attempted cp?
>>
> 
> The grepped setup log is attached (it is from setup.log, by the way -
> setup.log.full is surprisingly small).

Actually, it was setup.log.full that I wanted, since that is the file
where the postinstall script redirects the output from 'cp -v' - really,
what I'm looking for from someone who has a failed /bin/sh upgrade, is the
reason for the failure (for example, whether it was because sh.exe was in
use, or because of permissions issues, etc.).  Until I know why it failed,
I can't work around it, since I haven't been able to reproduce a failure
in my tests so far.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFeN0s84KuGfSFAYARAiLJAJ908CzEjWOq4yvYwkhJ/0mmVJwZawCePtL0
JODdl6NkxGaLIN7BSuyLLHA=
=OzzO
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/