X-Recipient: archive-cygwin@delorie.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:subject:to:cc:mime-version
	:content-type:references:in-reply-to:message-id; q=dns; s=
	default; b=cwYYhhQRa4CNUE1w8WOp5F1iKfF3YLBt3+95wysOdDH6/cstP8bij
	QYXXktzOR1lg/7kRxTCayzViKaORCMbLEgqz7ZwEf8toDj+fJhIJLzwi3aje1JAp
	k1BAlwemmBRWPA6LtH87LR66lqO7X53WLc00L19E+Eqxjq2NdwjUf0=
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:subject:to:cc:mime-version
	:content-type:references:in-reply-to:message-id; s=default; bh=N
	HBF5FFri2CJcj1B8dxyWMA7Plw=; b=BNP+D/kqBO01xaN86dFtIBe8fowQzVddR
	P9F/jMNvAh/k21mVQxh1jxzTX0k1xpdhJKruYtDDKRifADOHIul/9HF7yIdn+d6Z
	lFFDNxi3jmY0p32eBOsCkjML+rsLjiDq7t2g6NTqukFk28Szx8gZcM5GtLTcNVEe
	zARskKrgnM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=Our, H*x:Windows, H*c:HHHHHH, our
X-HELO: smtp.tt-solutions.com
Date: Fri, 3 Nov 2017 17:32:12 +0100
From: Vadim Zeitlin <vadim@zeitlins.org>
Subject: Re[2]: Problem running the latest python2-2.7.14-1 under AppVeyor
To: The Cygwin Mailing List <cygwin@cygwin.com>
cc: Jon Turney <jon.turney@dronecode.org.uk>
MIME-Version: 1.0
Content-Type: MULTIPART/SIGNED; protocol="application/pgp-signature"; micalg=pgp-sha1; BOUNDARY="601656873-41-1509726732=:156960"
References: <E1eAdDq-0000EC-96@smtp.tt-solutions.com> <f9354afc-57f6-7ba4-85b6-da5c85532d6b@dronecode.org.uk>
In-Reply-To: <f9354afc-57f6-7ba4-85b6-da5c85532d6b@dronecode.org.uk>
Message-Id: <E1eAetA-0003k9-SP@smtp.tt-solutions.com>

--601656873-41-1509726732=:156960
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Disposition: INLINE

On Fri, 3 Nov 2017 15:26:27 +0000 Jon Turney <jon.turney@dronecode.org.uk> wrote:

JT> On 03/11/2017 14:45, Vadim Zeitlin wrote:
JT> > Our build has started on AppVeyor, a continuous integration provider,
JT> > started failing since a couple of days as a makefile command running a
JT> > Python script started failing with exit code 127 without any more
JT> > information. This is a strange situation as I can't reproduce the problem
JT> > locally, but something definitely seems to be wrong with this package on
JT> > the AppVeyor machine as Python just doesn't seem to be executable, e.g. the
JT> > output of these commands in our batch file driving the build:
JT> 
JT> Perhaps you need to provide the -g (--upgrade-also) flag to cygwin's setup.

 Thank you! This has indeed fixed it and Python runs now, after having
updated a whole lot of other packages[*]. And it also explains why I failed
to reproduce it locally: it must have installed all the right versions of
the packages for me, as I hadn't had them before.

 Thanks again for helping with resolving this issue!
VZ

[*] https://ci.appveyor.com/project/wxWidgets/wxwidgets/build/2248

--601656873-41-1509726732=:156960
Content-Type: APPLICATION/PGP-SIGNATURE

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)

iEYEABECAAYFAln8mgwACgkQBupB3k9sHoYptACdGdg+wapY+k7uwjjRWHvCW6vV
cIQAnRpGG6mn/S/tVaX69xKcd4h/zgFr
=zkK0
-----END PGP SIGNATURE-----

--601656873-41-1509726732=:156960--
