X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW
X-Spam-Check-By:	sourceware.org
Message-ID:	<4CE3DD91.30504@dronecode.org.uk>
Date:	Wed, 17 Nov 2010 13:50:09 +0000
From:	Jon TURNEY <jon DOT turney AT dronecode DOT org DOT uk>
Reply-To:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
CC:	wilson AT ds DOT net
Subject:	Re: "No Package" base-passwd, passwd-grp.sh error messages
References:	<20101117132035 DOT M49506 AT ds DOT net>
In-Reply-To:	<20101117132035.M49506@ds.net>
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

On 17/11/2010 13:35, Brian Wilson wrote:
> I recently tried to correct an issue with passwd-grp.sh giving errora and another kind hearted 
> soul (Marco Atzeri) pointed out that I needed to reinstall base-passwd. 
>  
> I've done the base-passwd reinstall, however the following errors were displayed by setup.
> 
> Package: base-passwd
> 	passwd-grp.sh exit code 1
> Package: No package
> 	passwd-grp.sh exit code 1
> 
> I'm not sure what these "No package" errors mean; and the numeric exit codes are not helpful to 
> me.  Should I try running the passwd-grp.sh script in my own bash shell or could that have nasty 
> side effects?

Yes, look in /var/log/setup.log.full (as that setup page suggests) or try
running the script manually to discover why it failed.

'No package' simply means that a post-install script was found in
/etc/postinstall, but setup doesn't know which package it belongs to (I guess
'Unknown package' would be clearer).  It's a bug in the current version of
setup that this occurs for all failing postinstall scripts at the moment, see [1]

[1] http://cygwin.com/ml/cygwin-apps/2010-08/msg00203.html

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