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:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=vKZkmDm
	KEViu185hiOqvZ7Ra9/zZ4CcTfdg7PQRzRKFXEzcRxOOmmIW0EdNp/eJA7piZkjE
	dr3qfDa8oJ/0m3ObNnbBYCnw0hp5YCciLIVBSnTxl1+8ARBpNWSxy+r+XDahsl8+
	BkzjzYRq9Li9kuwlTEdrehN8j/DoQxUqGxgg=
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:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:content-type; s=default; bh=kMKC/HlGkmwF5
	0bSUWYrEWkKPTY=; b=Zp4vn9B8ii3AZun1saXzHeJ2vwLKteOfQWX/OQLxlRCLE
	CBgNdtTQoAz1UDh2VACdaCUH1n+TXfU7Um0tkPVrdvXN7qCGhchEmqgHfwchc2Tg
	gf//liiw8EMyj3aZOcSokh8/GWjB4VJzxrCPvPTha+JlENrHiStUsvStlhTBOY=
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.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,GIT_PATCH_2,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Our, Hx-languages-length:1721, our
X-HELO: mail-it0-f45.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to;        bh=a8bsc/iV/LtzVEwxStblxKUeS6XG+/f43/u0dpmvoo0=;        b=CSN4cH0Q7CyGRNnfCSsJcuPE6dIVwbtKuYb9Vpu1I9I8+YyBXGzM2UCvhjpfwIzQ89         ezrLFsmhEO9uVDsvAaiY0PaZjcRwma+B7vYhWLqzGhkYWKy1I4EAQyBHYmW3MRxYpCLL         QKRFuralCcM3utzVTkC69qDL2i7fZgSc+Di1c3cX/NvJafcVIYylj1DuvC7KViaLFgBy         HY4czlmxwC5FoTn46eKBehKXJHo0IHaMQzE2hunCoUNuTJF3plokekBhfxnTMUQdBIcv         rzaPGlJgcRHlED/we8zfAkvBCFcngkGRJnGOi2NowcDva4m2xcDQM2Bds5bTV6E3LrC1         aKOw==
X-Gm-Message-State: AElRT7E2g2UuldU3kra4dkRp+ahIkvHegcOLmKIhqxGWMsR+i6drGR72	FxIzL8rSqH7iPvB4o7+km9zpFPa0BUus+bpDWks=
X-Google-Smtp-Source: AG47ELtnwQvM9RcVZtFFyjGIrbc/mtJW6P1OCxP7LNqZwuZ1FRTdjgIulK4vD4FGF3sVGzFJxgRAacxXuUBk2siVCrs=
X-Received: by 2002:a24:17d1:: with SMTP id 200-v6mr7377604ith.15.1521325860733; Sat, 17 Mar 2018 15:31:00 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D90189B4A99A@Remus.metastack.local>
References: <CAD8GWstM+H9_FBFvCF44vv1PMOgndLEgy3GvXon5UDDon9qZ6A AT mail DOT gmail DOT com> <E51C5B015DBD1348A1D85763337FB6D90189B4A99A AT Remus DOT metastack DOT local>
From: Lee <ler762 AT gmail DOT com>
Date: Sat, 17 Mar 2018 18:31:00 -0400
Message-ID: <CAD8GWssWPUX7k5mwte5EA3EYqpTRNjBrRCH8moeTvBU7gyRGsA@mail.gmail.com>
Subject: Re: setup -g ???
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes

On 3/14/18, David Allsopp wrote:
> [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).

So if I run setup and it says there are no pending updates it might be
lying to me?

I need to run setup -g and only then if there are no pending updates
do I know that my cygwin installation is up to date?

Thanks,
Lee

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