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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=O31WS0UgvFz8HsqQ8PR6/jNkCAwoe
	MHge2jEYiyN4Lk3OJIeh6borqn8Ss5I5CTdPR5E1KQVt0cD36YE/+AVOYvBCG+Bw
	2NM0Ed1qmiHMKhDqtTH/JBN8Ee1TxoScrYnyCNGLY7Mu2GlvntPJ1fjOU4symH46
	bCGCF1kB9Qthlc=
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:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=d8dx0NcwE46Dk7hKlYKYH5PZrL8=; b=FIy
	SvVVeIV1X3y5+mZS/F9bNqFv1sB9hPGElsHRybpvF6rHDwg1Gib7/9Biph8pkA3C
	xXmSiKfZ9yZiuC0lMTf0PdBfjrpmBpEerVzVI5DFpmvh06iejL+KSCI0gY+ODWkC
	lsN0zgrabmGP6bsYSpTVkCmOf8vb3Vjqsjs3LYx8=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-6.6 required=5.0 tests=BAYES_00,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=nuisance, Our, our
X-HELO: outmail149101.authsmtp.com
From: David Allsopp <David DOT Allsopp AT cl DOT cam DOT ac DOT uk>
To: Lee <ler762 AT gmail DOT com>, "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: setup -g ???
Date: Wed, 14 Mar 2018 15:26:40 +0000
Message-ID: <E51C5B015DBD1348A1D85763337FB6D90189B4A99A@Remus.metastack.local>
References: <CAD8GWstM+H9_FBFvCF44vv1PMOgndLEgy3GvXon5UDDon9qZ6A AT mail DOT gmail DOT com>
In-Reply-To: <CAD8GWstM+H9_FBFvCF44vv1PMOgndLEgy3GvXon5UDDon9qZ6A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-Server-Quench: 176d5453-279c-11e8-9f3c-9cb654bb2504
X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse
X-AuthRoute: OCd1ZAARAlZ5RRob BmUtCCtbTh09DhZI RxQKKE1TKxwUVhJU L0JGL0JXPR1GBEcA B3l2ChZLUl1wUXN0 bgBTaw9eawRMXgZ0 UUhMXFBTFhtpABge BBsBU1c1dXAwGS0x B0ZrW3ZYXgp9d0d7 DE9TEzkDYWJjdWIY WRNFdgIBeB5DKBwW d1ksBnUIZTdVZH9g QxkJEmJ5JjhDNTwd Bw5FegVFKQUI
X-Authentic-SMTP: 61633634383431.1039:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 213.105.212.114/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system.
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id w2EFQs3Y026748

[reformatted for top-posting]

Lee wrote:
> > ---------- Forwarded message ----------
> > From: Jon Turney
> > Date: Fri, 3 Nov 2017 15:26:27 +0000
> > Subject: Re: Problem running the latest python2-2.7.14-1 under AppVeyor
> > To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
> > 
> > On 03/11/2017 14:45, Vadim Zeitlin wrote:
> > > Our build has started on AppVeyor, a continuous integration provider,
> > > started failing since a couple of days as a makefile command running a
> > > Python script started failing with exit code 127 without any more
> > > information. This is a strange situation as I can't reproduce the
> > > problem locally, but something definitely seems to be wrong with this
> > > package on the AppVeyor machine as Python just doesn't seem to be
> > > executable, e.g. the output of these commands in our batch file
> > driving the build:
> > 
> > Perhaps you need to provide the -g (--upgrade-also) flag to cygwin's
> > setup.
> > 
> > Due to setup terribleness, without this flag, it will install the
> > requested packages, and any missing dependencies of them, but not
> > upgrade any of the dependencies which are already installed to the
> > current (and perhaps needed) version...
> > 
> > See also [1].
> > 
> > [1] https://sourceware.org/ml/cygwin/2017-03/msg00365.html
>
> Should we still be using the -g (--upgrade-also) flag on setup?

I believe so (or at least hope so). I think it's the case that setup should now know to upgrade a dependency if you install a new package which requires a newer version of it, but I hope that's not become the same as setup effectively acting with --upgrade-also every time you run it (that would be a real nuisance, unless the entire Cygwin package universe is going to be recompiled on every new Cygwin release).


David

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