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=mzFiicw WsNHIXWUXYK9vrhmmv+xHgU40BwU0AaePIAuWfwCX9OlwiHVmvJaoA5fvIhXqJKq d1Dm/bUelFFL1vDqvywMvDypL49hxq2STD7HwDKYDYecy6K3eS8gLUeKLnzw+jZF DXhDL2jM9BzqpTsafb32XtGCTrMrTlM8Hq+4= 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=zJLYZNEWE3sxq 4zyY1kH1hv0qEw=; b=t6Q8HouqGz1Cv0OwBCzTRyXhe5XU+BrDs0zjOEo2vWm4z 7fqd+2ZqbRoIcE/2uL4xBGrA+TVVJN6q+RR7atqAsGi6Xmms4u6/ja+iOihe6pxe shqmzx/7+9IDlzbiUxZRcpYACaQNBZP+hvD6C0YfUrpXtOa95VxqH/xNdx7AVw= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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, our, lucky X-HELO: mail-it0-f52.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=ARAijAVtZKDD652G+nN7BbMiB46MPjS2HAaHdOMVEfY=; b=H7C9pvIOHZVHwgFKvVXy1caR6fwoQAmNI+YMOlhLyyY2k0pRauNcXzVOjxk4cZHC0+ PQZOTpWyUlIUZ9ttJdDbLvzvEfckgjP2HOy2ov8iWVrmaAXs7a9ObptKUq3KEbgbqsaO caoMbB439aWo2rggzyUtSNMT6cBqG8gQO3mooe21q3A71l2QrF+WxNpfG/xhlRGoT9Rx oCSUYHYKLUDf1PzWPAomXZG7HcmDJUJOoyEbOnUKTDSGgy0D8xbHHOVOrc2nK0D7Z0V5 GSnyuLp72XyZUSxPe96gHYk19C14iEzWebX7ZQ/171832PuHLdYoollHNznCrnoflnBP JKLg== X-Gm-Message-State: AElRT7H0PAIp+n2OR6JsxDMTxplqPoceNazJHB1K8RxpN3/LQfzvlVuF OKYikOrtBqvYR8FFlQmkgjfiwzHnk+JLbOlRzlE= X-Google-Smtp-Source: AG47ELugoxSawGTd3g+Sw3P3ZKXxjqJueNjc9OOgT50OVdMS3/CYmlGkZYXH2cbcKKt5G45qB0n9yPB3AkAatCTzHNc= X-Received: by 2002:a24:9285:: with SMTP id l127-v6mr9697208itd.40.1521389944241; Sun, 18 Mar 2018 09:19:04 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Lee Date: Sun, 18 Mar 2018 12:19:03 -0400 Message-ID: Subject: Re: setup -g ??? To: "cygwin AT cygwin DOT com" Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes On 3/18/18, David Allsopp wrote: > Lee wrote: >> 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 >> >> > >> >> > 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? > > No - the original question here was about running setup with a command line > and the --packages argument. If you run setup interactively (with no > arguments), you should be told if any packages need upgrading, just as > before, without needing -g. When I saw the msg about > Perhaps you need to provide the -g (--upgrade-also) flag I tried running setup & got a short list of updates. Applied the updates and ran setup again.. and had no pending updates listed as expected. Then I ran setup -g and a few libXXX things were listed as pending :( Maybe I got lucky & the lib showed up at the mirror I was using just after running setup the second time?? dunno, but unless/until I can duplicate setup not showing any pending updates & setup -g saying there are pending updates, maybe we should just write it off as a one time occurrence. 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