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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D90189B4A99A@Remus.metastack.local>
References: <CAD8GWstM+H9_FBFvCF44vv1PMOgndLEgy3GvXon5UDDon9qZ6A@mail.gmail.com> <E51C5B015DBD1348A1D85763337FB6D90189B4A99A@Remus.metastack.local>
From: Lee <ler762@gmail.com>
Date: Sat, 17 Mar 2018 18:31:00 -0400
Message-ID: <CAD8GWssWPUX7k5mwte5EA3EYqpTRNjBrRCH8moeTvBU7gyRGsA@mail.gmail.com>
Subject: Re: setup -g ???
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

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@cygwin.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