X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-0.6 required=5.0 tests=AWL,BAYES_20,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
X-IronPortListener:	Outbound_SMTP
From:	"Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder AT niaid DOT nih DOT gov>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
CC:	"'Milos Puchta'" <puchtmil AT fel DOT cvut DOT cz>
Date:	Mon, 23 Aug 2010 17:48:35 -0400
Subject:	RE: Postinstall error (partly solved)
Message-ID:	<0105D5C1E0353146B1B222348B0411A20946F38B2C@NIHMLBX02.nih.gov>
References:	<000001cb42f0$13818270$3a848750$@cvut.cz>
In-Reply-To:	<000001cb42f0$13818270$3a848750$@cvut.cz>
MIME-Version:	1.0
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

Milos Puchta sent the following at Monday, August 23, 2010 2:22 PM
>Hello
>	boxes.sh exit code 2
>	libglade2.0.sh exit code 3
>	exim.sh exit code 1
>	mined.sh exit code 1
>	boxes.sh exit code 2
>	exim.sh exit code 1
>	libglade2.0.sh exit code 3
>	mined.sh exit code 1
>
>I had created by mc new directory \etx\xml and postinstall has not
>announce any error concerning xml documents. However some error
>persists: Package: boxes Package: libglade2.0_0 Package: exim Package:
>mined Package: No package
>
>Has anyone a hint how to cure boxes, libglade2, exim and mined?

My suggestion:

Open a terminal (bash or your shell of preference).

Go to /etc/postinstall

Edit each of the scripts, adding "-x" to the end of the "shebang" line.

Run the script.

That should show you what command is giving the error.  The error message
may also indicate why it is giving the error.

For what it's worth (probably not much), my experience was related to
permissions.  However, you may have an unrelated cause, so consider other
possibilities.

If an application seems to be working OK, or you figure out the problem and
correct it manually (without the script) you might consider renaming
script.sh to script.sh.done to get setup to stop trying to run the script.

Good luck,

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.


--
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 -