From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: CI configuration update
Date: Thu, 29 Apr 2021 21:09:40 +0200 [thread overview]
Message-ID: <YIsEdHJR1W0a+HYU@calimero.vinschen.de> (raw)
In-Reply-To: <20210429185324.17357-1-jon.turney@dronecode.org.uk>
On Apr 29 19:53, Jon Turney wrote:
> Install autoconf and automake, and run winsup/autogen.sh, and don't have
> it silently ignore failures.
>
> On AppVeyor:
> - use latest VM image, to reduce time spent installing updates.
> - run the testsuite, but ignore the result, as some tests don't work
> correctly.
> - hardcode the python-lxml and python-ply packages to install, so we get
> ones for the right python.
> - install texlive collections now needed to build documentation.
>
> On github:
> - Use a copr for cocom, since RPMSphere's package updates don't track
> fedora:latest very efficently.
> ---
> .appveyor.yml | 13 +++++++++++--
> .github/workflows/cygwin.yml | 11 +++++++----
> winsup/autogen.sh | 1 +
> 3 files changed, 19 insertions(+), 6 deletions(-)
LGTM, please push.
Thanks,
Corinna
prev parent reply other threads:[~2021-04-29 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 18:53 Jon Turney
2021-04-29 19:09 ` Corinna Vinschen [this message]
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=YIsEdHJR1W0a+HYU@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@cygwin.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).