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:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=J/bo
	Y6dkqoXCADX7O2c1iAiIK0pE1Lsqd8QCl+EdrDNjjrDsr3qUFUSEV9nsVSgdWJc1
	YMRekzA8olYYu0YkTFjLtZDmq8SA0rB8uX7UpG7mSPWtg7qBplxjlZ57rdpueofI
	M+5UlIfdShiGkxdfBuw6kK+Mr41AbzzooRaaB/c=
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:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=ghBA21v+Du
	njd4sdR99pzAmDOz4=; b=AQYuZWSqFcujqkXz8SJJ3R2keixWNw25sLw+4vFOcE
	Z6mU5jB3K5F0M5jknJ6ORTrFEAXz0diQdHNQej7M9nIlozKtv4D+NwDrb9RZsrA3
	sO/7A3WBl09NLutJSsA3nWjhNIRZ+RsYVnsPv5geRrS7SyX1I0nYw2gd4npug8bM
	o=
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
X-Spam-SWARE-Status:	No, score=0.0 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_PASS autolearn=no version=3.3.1
Date:	Thu, 1 Aug 2013 15:41:04 -0700
From:	Gary Johnson <garyjohn AT spocom DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: pango1.0.sh exit code 1
Message-ID:	<20130801224104.GA5083@phoenix>
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<51FAD807 DOT 3070403 AT alice DOT it>
MIME-Version:	1.0
In-Reply-To:	<51FAD807.3070403@alice.it>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On 2013-08-01, Angelo Graziosi wrote:
> Martin Baute wrote:
> >The libpango1.0 postinstall script fails with exit code 1
> 
> Same here on a W7 box (cygwin32). Same workaround.
> 
> Strangely, on XP it worked fine some time ago (probably in the 2009)..

As I reported in an earlier thread ("Recent Cygwin problems", June
21, 2013), I didn't see this message on XP until sometime in May or
June of this year.

Regards,
Gary


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