From: David Allsopp <David.Allsopp@cl.cam.ac.uk>
To: Lee <ler762@gmail.com>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: setup -g ???
Date: Wed, 14 Mar 2018 19:08:00 -0000 [thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D90189B4A99A@Remus.metastack.local> (raw)
In-Reply-To: <CAD8GWstM+H9_FBFvCF44vv1PMOgndLEgy3GvXon5UDDon9qZ6A@mail.gmail.com>
[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). 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
next prev parent reply other threads:[~2018-03-14 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 15:28 Lee
2018-03-14 19:08 ` David Allsopp [this message]
2018-03-17 22:51 ` Lee
2018-03-18 13:52 ` David Allsopp
2018-03-18 18:23 ` Lee
2018-03-19 13:32 ` David Allsopp
2018-03-22 23:10 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E51C5B015DBD1348A1D85763337FB6D90189B4A99A@Remus.metastack.local \
--to=david.allsopp@cl.cam.ac.uk \
--cc=cygwin@cygwin.com \
--cc=ler762@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).