delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2018/03/19/09:28:11

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=EJAJ59mdaapRvAAWkQnVq9RUwrEIs
5ekgCARV9qjw3yvDWTMSfzgfuO6CxIStHLc57oP/vOWuajjl5oLGpqMfZR4jPaJN
RvoPoS8sn9eRSbzHl0ogcP1G2z7AoIN9HjZUH2oDdyZk9eMR9gBXKMUHUg6pWiFK
/wWS99pAB0e/Gk=
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=yKUB1rynwMVtIlfcpNtz8dz2YLA=; b=gA0
07oYTnC57ebMNcqjc56eTA4/VogMQqpuklAsd1V9Sj7v4vmWCJpE6EXx82ZQoVzr
5rLe7b6dXJo1GDvWOetGDzRCYkjV1U5UE9aKu11oDfPiPGCDWa7Q7sHg7NayKHjP
HyEkCv98xpFcia+ioex69RlL8fEAN2AFHrkxqA3s=
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=Our
X-HELO: outmail148109.authsmtp.co.uk
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: Mon, 19 Mar 2018 13:27:49 +0000
Message-ID: <E51C5B015DBD1348A1D85763337FB6D90189B7FC24@Remus.metastack.local>
References: <CAD8GWstM+H9_FBFvCF44vv1PMOgndLEgy3GvXon5UDDon9qZ6A AT mail DOT gmail DOT com> <E51C5B015DBD1348A1D85763337FB6D90189B4A99A AT Remus DOT metastack DOT local> <CAD8GWssWPUX7k5mwte5EA3EYqpTRNjBrRCH8moeTvBU7gyRGsA AT mail DOT gmail DOT com> <E51C5B015DBD1348A1D85763337FB6D90189B72D75 AT Remus DOT metastack DOT local> <CAD8GWssfJfFW+_PEU2guvqQE59VQ4=UQ1tBco7UKTNWw1mZruw AT mail DOT gmail DOT com>
In-Reply-To: <CAD8GWssfJfFW+_PEU2guvqQE59VQ4=UQ1tBco7UKTNWw1mZruw@mail.gmail.com>
MIME-Version: 1.0
X-Server-Quench: 53f469bb-2b79-11e8-8106-0015176ca198
X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse
X-AuthRoute: OCd1ZAARAlZ5RRob BmUtCCtbTh09DhZI RxQKKE1TKxwUVhJU L0JGL0JXPR1GBEcA Cnl2ChZLUl1wUXN0 aABTag9YYQRMXgZ0 UUhMXFBTFhtpABge BBsBU1c1dX8yGj4B OUZkWHNSVAp7d099 QgBRFjsCY24yOn0d AkdRagJVJQtXdh5F bE1/VHIIYGIBNSth Tl8lBR1jdS5SNDlN CkQCZQVFFi4I
X-Authentic-SMTP: 61633634383431.1038: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
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id w2JDSAdw010646

Lee wrote:
> 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 <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?
> >
> > 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<whatevers> 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.

It's possible that it was simply a mirror update - there are two ways to tell, if you see it again (or if you can remember what the actual packages were and the date you did it). One is to look in the history of this mailing list and see if there was an announce of a package update on or around the time you did the update. The other is to browse a mirror directly (e.g. https://mirrorservice.org/sites/sourceware.org/pub/cygwin/) and look at the timestamps of the files for the new package which appeared.

The third way, if it really worries you, is to use a private mirror (either via rsync or using Cygwin setup's "Download" option - though over the years I've found the latter remarkably unreliable) which allows completely repeatable installations.

HTH,


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


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019