From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: git repositories for cygwin packaging - please test
Date: Wed, 27 May 2020 23:27:49 +0100 [thread overview]
Message-ID: <181ea3fa-1a50-7db4-0009-47ea9af77cdc@dronecode.org.uk> (raw)
In-Reply-To: <20e2f046-af24-14b8-b6c4-263f859042b8@dronecode.org.uk>
On 04/08/2019 21:08, Jon Turney wrote:
> To remedy this lack, using the same ssh key you use for sftp package
> upload, package maintainers can now also push to git repositories, like so:
Package maintainers may have noticed that the output from pushing to
these git repositories now includes a line like:
"remote: scallywag: build nnn queued"
This is a *prototype* of a system to automatically build the packages,
where the results appear (some time later) at [1] (URL subject to change)
[1] https://cygwin.com/cgi-bin2/jobs.cgi
Currently, many packages will fail to build correctly due to:
(i) missing or insufficient 'BUILD_REQUIRES',
(ii) missing prerequisites implied by an 'inherit' (a bug in this system),
(iii) resource limits imposed by AppVeyor's free service which is used
to perform the actual builds, or
(iv) other bugs in this system.
At this stage, this is only probably useful for verifying that
BUILD_REQUIRES is correct.
(Note that a successful build doesn't always mean that you have
reproduced your build: You'll need to check the configuration step
output and/or dependencies of the produced packages are the same.
Consider explicitly enabling the functionality you are expecting in the
options to the configure script , if it supports that (e.g.
CYGCONF_ARGS, etc.), to avoid it potentially silently turning off in
future, if it's requirements change)
To allow experimentation without messing up the version history
unnecessarily:
- All package repositories allow the maintainer(s) to create, push,
rewind and delete a branch named 'playground'.
- An additional package repository called 'playground' exists, that all
maintainers can do anything to.
next prev parent reply other threads:[~2020-05-27 22:27 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-04 20:08 Jon Turney
2019-08-05 2:03 ` Ken Brown
2019-08-08 13:47 ` Andrew Schulman via cygwin-apps
2019-08-08 14:04 ` Andrew Schulman via cygwin-apps
2019-08-08 17:09 ` Ken Brown
2019-08-09 16:12 ` Jon Turney
2019-08-09 19:12 ` Ken Brown
2019-08-13 11:55 ` Jon Turney
2019-08-09 16:00 ` Jon Turney
2019-08-09 20:58 ` Brian Inglis
2019-08-13 11:55 ` Jon Turney
2019-08-19 18:36 ` Achim Gratz
2020-05-27 22:27 ` Jon Turney [this message]
2020-05-28 11:51 ` szgyg
2020-06-04 16:01 ` Ken Brown
2020-06-04 20:33 ` Brian Inglis
2020-06-09 13:26 ` Jon Turney
2020-06-09 22:44 ` Brian Inglis
2020-08-06 20:20 ` Jon Turney
2020-08-06 21:04 ` Ken Brown
2020-08-07 19:42 ` Achim Gratz
2020-08-07 22:05 ` Ken Brown
2020-08-08 4:26 ` ASSI
2020-08-16 18:05 ` Jon Turney
2020-08-23 21:01 ` Jon Turney
2020-08-26 22:00 ` Ken Brown
2020-08-30 15:00 ` Jon Turney
2020-08-30 15:22 ` Ken Brown
2020-08-30 15:46 ` Jon Turney
2020-08-30 17:25 ` Ken Brown
2020-08-30 20:06 ` Jon Turney
2020-11-12 21:30 ` Jon Turney
2020-08-30 16:44 ` ASSI
2020-08-30 20:08 ` Jon Turney
2020-10-04 10:26 ` Achim Gratz
2020-10-25 18:10 ` Jon Turney
2021-05-09 14:39 ` Jon Turney
2021-06-22 19:52 ` Jon Turney
2021-06-23 4:22 ` Brian Inglis
2022-07-05 13:12 ` Jon Turney
2023-02-18 16:21 ` Jon Turney
2023-02-18 17:43 ` Ken Brown
2023-02-18 18:40 ` Jon Turney
2020-11-16 21:54 ` Brian Inglis
2020-11-16 22:16 ` Jon Turney
2020-11-16 22:54 ` Brian Inglis
2020-11-17 19:21 ` Achim Gratz
2020-05-29 14:40 ` Alexey Sokolov
2020-06-07 15:06 ` Hamish McIntyre-Bhatty
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=181ea3fa-1a50-7db4-0009-47ea9af77cdc@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@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).